← All posts
Audit ProcessChecklist

Smart Contract Audit Checklist: What to Prepare Before You Hire an Auditor

Security Wiz team3 min read

ShareTelegramX

The fastest way to get more from an audit is to show up prepared, the way you'd gather your paperwork before meeting an accountant. Auditors can only test what they can run, read, and understand. Most of the delay on a typical audit comes from missing basics, not from hard problems. Here's what we ask every team for, and why each item matters.

Code and build

  • Access to your code, and one exact version of it. The audit covers a single version, identified by its commit hash, the ID your code-hosting tool gives each saved version. Any change after that is a change to what's being audited. So freeze the code first, then book.
  • A list of what's included and what isn't. Name the contracts or parts to be reviewed, and say what's left out, so nobody assumes something was covered when it wasn't.
  • Code that builds on a fresh computer. Tell us which versions of your tools to use (solc, Foundry or Hardhat, Sui CLI, Anchor), include the files that pin your dependencies, and give us one command that builds everything. If it only builds on one person's laptop, the first day goes to fixing your setup.
  • Your existing tests, and a report of how much of the code they cover, runnable with one command. Tests show what you already believe about the code. The gaps show where to look.
  • Your launch scripts and the settings you'll launch with: starting values, addresses, fees, limits. Many real problems live in the settings and not in the code.

How it's supposed to work

This is the part teams most often skip, and it's the part that leads to the most serious findings.

  • A plain-English description of what your product does, who it's for, and how money moves through it. A whitepaper works. So does a one-page note.
  • The rules you believe must never break, for example "the shares handed out always match the money deposited." Auditors turn these into tests and try to break them.
  • Who has special powers. Every administrator, owner, upgrade key, and pause key, and who holds each one. Tell us whether each is a multisig (a wallet that needs several people to approve an action) or sits behind a timelock (a built-in waiting period).
  • What you rely on from outside, and what you assume about each: price feeds, connections to other blockchains, other apps, the tokens you accept. "We assume the price feed is up to date" is exactly the kind of sentence an auditor wants to test.

If you're live or upgrading

  • Which blockchain you're on, and the addresses where your code lives.
  • For an upgrade: the version that's live now, exactly what's changing, and your plan for moving over.
  • How much money you expect it to hold, and in which tokens, so each finding can be sized by its real impact.

If your website and servers are included

  • The website's code and how it's hosted: where the domain is registered, the delivery network in front of it, the automated system that builds and releases it, and who can publish changes.
  • Your servers, APIs, and any automated bots that act on the product's behalf, and where their private keys are kept.
  • A test copy of the site and test accounts that the auditor is allowed to attack.

Background that speeds things up

  • Earlier audits and how each finding was dealt with
  • Known problems and risks you've chosen to accept, so they aren't reported as new
  • The areas your team is most worried about
  • One technical contact who answers questions within 24 hours

Permissions

  • Written consent for how your code is handled, including whether any AI service sees it.
  • Ground rules for anything that's live: which systems may be tested, how hard, and no transactions on the real network.

A quick self-check

Before you ask for a quote, ask yourself: could someone I've never met download this code, build it, and explain in plain English what it does and who is allowed to do what? If the answer to any of those three is "no," that's your first task.

If you'd like a second pair of eyes on your readiness, or want to start with a design review before your code is frozen, get in touch. We return quotes within 24 hours, and you can read more about how our audits work.

ShareTelegramX

Shipping something onchain?

Send us your repo and we’ll return a quote within 24 hours.

Request an Audit