The single most common question we get on a first call is some version of "how much does a smart contract audit cost?". The honest answer is from $5,000 for a small, well-scoped engagement up to $80,000 or more for larger or novel protocols, and the variance inside that range is mostly explainable. This piece walks through how serious audit firms price, why the cheap quote is rarely cheap, and how to scope your own engagement so the number you get back is the number you pay.
The pricing axes that matter
A senior auditor who quotes you in five minutes is either running on intuition or selling you a templated number. The real scoping looks at five axes:
- Lines of in-scope Solidity / Vyper / Cairo. Not total lines, in-scope lines. A 4,000-LOC repo where you only ship 800 lines of new code re-prices accordingly.
- Novelty of the design. A vault that wraps a known yield strategy is faster to audit than a custom AMM with a novel curve. Novelty means the auditor can't lean on prior pattern-matching.
- External integration count. Every external contract your code calls into is a new threat surface. Oracles, bridges, lending markets, governance: each adds review time.
- Upgrade and access-control complexity. Proxies, timelocks, governance modules, and privileged roles compound review effort. A single owner-only function is trivial; a 12-role permissioned protocol with conditional access is not.
- Re-audit scope. Most audits include one re-audit after fixes. Multiple rounds, or fixes that touch wide surfaces, can extend the engagement.
When we send a fixed-fee proposal, those five inputs are visible in the math. There are no hourly surprises later.
Where the price lives
Rough 2026 ranges we see in the market for credible firms:
- $5k–$15k: Low end. Almost always a small scope (single contract, well-understood pattern), or a junior-led tool-driven review marketed as an audit. Useful as a sanity check, not as the audit you stake mainnet on.
- $15k–$40k: The typical mid-market range. Senior-led, 2–3 weeks, full report, re-audit. Most DeFi vaults, NFT mints, and small protocols sit here.
- $40k–$80k: Larger or more novel protocols. Multiple auditors, longer engagement, deeper threat modeling.
- $80k+: Lending markets, perpetuals, large governance systems, novel cryptography. Multi-week, multi-auditor, often paired with a public competition (Code4rena, Sherlock) and a bug bounty.
Numbers below the floor of those ranges should make you pause. The cost of a missed reentrancy, oracle manipulation, or access control bug is the protocol's TVL, not the price difference between two auditors.
Why the cheap quote is rarely cheap
Three patterns we see in cut-rate quotes:
- Tool-driven "audits". A Slither + Mythril run is a starting point, not a deliverable. Senior auditors use the same tools, but the value they add is reading every in-scope line manually with the protocol's economic logic in mind. If the report you receive looks like a tool dump, you bought a tool dump.
- Junior-only staffing. Audit reports have author lines. If the people listed are all junior, the firm priced for junior throughput. Senior eyes catch the patterns that pattern-matching tools cannot.
- No re-audit. The audit you ship is the post-fix audit, not the initial-finding audit. If the engagement doesn't include re-auditing the changed code, you are publishing findings against a state that no longer exists, and shipping a delta that nobody reviewed.
The smart contract audit checklist we wrote walks through what a credible scope statement looks like, useful to compare against any incoming proposal.
What to ask before you sign
Three concrete questions to put to any auditing firm:
- Show me a recent report you wrote on a similar protocol. The report is the deliverable. Read the writing quality, the depth of finding descriptions, and the post-fix re-audit section.
- Who specifically will work on this engagement? Senior auditors are the value. Junior staff plus tooling is not what you are paying for.
- What is included beyond the initial review? Re-audit scope, public summary you can publish, communication during the engagement, post-engagement support: confirm in writing.
Compliance pentest is priced differently
If you need a Web3 penetration test for MiCA, DORA, or PSAN compliance, the pricing logic shifts. The deliverable is not just findings: it is a documented methodology, an attestation letter your supervisor (AMF, ACPR, or local NCA) can rely on, and a defensible re-test cadence. That bumps the engagement scope by 20–40% over a standard pentest of the same surface, but it replaces a separate compliance workstream that would otherwise cost you weeks of internal effort.
Scoping your own engagement
When you reach out, the information that lets us send a fixed-fee proposal in 24–48 hours is:
- A commit hash and a list of in-scope contracts.
- The chain(s) and a brief design doc or whitepaper.
- A list of external dependencies (oracles, bridges, other protocols).
- Your target launch date and any regulatory deadline.
If you have those, book a scoping call and we can give you a number, in writing, the same week.
What this isn't
This is a guide, not a price list. Every protocol is different, and the cheapest credible audit for your protocol may be at the high end of the typical range or below it depending on the five axes above. The point of writing this piece is to show that the number is not arbitrary, and that any auditor who refuses to walk through the math with you should not be running adversarial review on your code.