← All posts
Audit ProcessBuying Guide

Choosing a Smart Contract Audit Firm: 10 Questions to Ask Before You Sign

Security Wiz team3 min read

ShareTelegramX

Choosing an audit firm is a bit like hiring a home inspector: from the outside they all look alike. Each has a logo, a list of past clients, and a sample report. The differences that matter are in how the work is done. Here are ten questions that bring them out. We note how we answer each, so you can compare.

1. Who will actually review my code?

Ask for the name and background of the person doing the review, not just the firm's brand. Some firms hand work to less experienced reviewers. You want to know who is reading your code and how much they've seen.

2. How is each finding confirmed?

"Our scanning tool flagged it" isn't confirmation. Ask what it takes for a suspicion to become a finding. Our answer: a person confirms every lead, either with a test or by following the exact route through the code. On our Fork tier, we confirm it with a working attack.

3. Will I get a proof I can run myself?

If a finding comes with a test you can run, your team can watch the problem happen, understand it, and check that the fix works. If it comes with only a written description, you're taking it on faith. Ours: on the Fork tier, each finding ships with a working attack you can run. On Core, a finding ships with a test wherever one can be written, and otherwise with the exact route through the code.

4. How is severity decided, and can I check it?

A label like "High" with no reasoning invites argument. A score you can recalculate yourself settles it. Ours: findings in the contract code are scored with OVSS, an open system, and the report shows the inputs behind each score.

5. Do you test on a copy of the live network?

Reading the code is valuable, but some attacks only show up against the real money and the real apps your product connects to. A "fork" is a private copy of the live blockchain where those attacks can be tried safely. Ask whether fork testing is available and what it adds. Ours: it's a tier. See Core vs Fork.

6. What does the report cover, including what wasn't found?

Ask for a sample. A good report is more than a list of bugs. It shows exactly what was reviewed, what an attacker would be after, and how the code was tested against a known standard such as the OWASP Smart Contract Top 10. See what a good report contains.

7. Is a recheck of my fixes included?

Fixes are new code, and new code has new bugs. Some firms charge separately for retesting, or skip it. Ours: one round is included in every audit.

8. Can I publish the report?

Your users can't read your code. They can read a report. Ask whether you can share it, and whether it's written for a non-technical reader. Ours: it's written to be publishable, and you decide whether it goes public.

9. How do you handle my code, and do you use AI on it?

You're sending unreleased code to an outside company. Ask where it's stored, who sees it, and when it's deleted. Ask whether any AI service touches it, and with what protections. Ours: only with your written consent, with secrets and personal data stripped first. Read how we use AI.

10. What happens after the audit?

Your code will change. An audit report covers one exact version of it. Ask how upgrades are handled, whether the firm offers repeat scans or a review of your design, and how long the audit stays meaningful. Ours: we review the changes in each upgrade, and offer design reviews and repeat automated scans. See why one audit isn't enough.

Two more things to ask yourself

  • Does the quote make sense? A fixed price tied to the size and complexity of your code is easier to plan around than an open-ended hourly rate.
  • Do you get timely answers? How a firm treats you during the sales process is a hint about how they'll treat you during the audit.

None of these questions is a trap, and the right firm will be glad to answer them. If you'd like to put ours to the test, request an audit and ask us all ten.

ShareTelegramX

Shipping something onchain?

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

Request an Audit