reth EIP-7928 report: see how a Hackerbane report is structured. Open the report → (opens in a new tab)

· Oscar Chambers

Smart contract audit cost in 2026

The figure Hackerbane publishes for a smart contract audit is From $18,000, and the quote is fixed once the scope is read. Code size, language, bridges and oracles, timeline, and the retest are what move that quote.

The description published for the smart contract audit page is a smart contract audit for Solidity, Rust, and Move, with two reviewers, exploit proofs, and a retest before you deploy. The price in that line is From $18,000, with a fixed quote after scope. High and Critical issues ship with a proof your team can run.

On the page, the price depends on scope, code complexity, integrations such as bridges and oracles, and the timeline. Share the repository and we confirm a fixed quote and a schedule before work starts.

Code size

Duration on the same page tracks the size of the code, and how quickly questions get answered during the review. A first audit is usually scoped at about two person-weeks. A single contract can take days. A protocol with upgradeable contracts, oracles, or bridges takes several weeks. The timeline is fixed when the scope is. A larger repository is more code for both reviewers to read, and that is what moves the quote.

Language

The page names Solidity, Rust, and Move. Language is part of the scope we read before the quote is fixed. A repository in more than one of those languages is a larger scope.

Bridges and oracles

The price depends on integrations such as bridges and oracles. The same page puts a protocol with oracles or bridges at several weeks. The quote follows that scope.

Timeline

The price depends on the timeline. The timeline is fixed when the scope is. The usual first audit on the page is about two person-weeks. A single contract can take days. Upgradeable contracts, oracles, or bridges take several weeks. The quote and the schedule are both confirmed before work starts.

Retest

The published line includes a retest before you deploy, and the page lists a retest of every in-scope fix. After the findings, your team fixes them and we retest. In-scope fixes come back inside an agreed window. We recheck that each fix resolves the issue and adds no new risk, and the final report records each issue as resolved, mitigated, or acknowledged. How much retest work that window contains is part of the scope the quote is fixed against.

What you send

Share the repository. The page also asks that the code you want reviewed is frozen, that it builds and its tests pass, that the architecture and the permissions are documented, and that the scope is defined down to the commit. What comes back is a fixed quote and a schedule, then a report with the scope and commit, findings ranked from Critical to Informational, a proof for High and Critical issues, and the retest status of each in-scope fix.

The page is Smart contract audit. To have the scope read, request an audit.