Before Commissioning a Web3 dApp Security Audit: Scope and Terms to Align in Your Quote
Yuta Matsuyama
Security Researcher, TECHFUND Inc.
Updated:
Who this is for: EVM or Solana dApp development teams
The practical answer
When you want to understand the cost of auditing a Web3 dApp, the quickest starting point is to clarify what you want to protect and how far you want the assessment to go. An audit limited to smart contracts and an assessment that also includes the frontend, APIs, and administrative key operations have different scopes, even for the same dApp. Rather than comparing quoted amounts alone, check the revision being assessed, expert review, reporting, and verification after fixes. This article helps development teams building dApps on EVM or Solana prepare to request quotes from audit providers. Actual prices and supported chains vary by project and need to be confirmed with each provider.
A Smart Contract Audit Alone Does Not Assess the Entire dApp
Contracts carry application-specific risks involving asset transfers, administrator privileges, price references, and interactions with external contracts. Meanwhile, the user interface, wallet connections, APIs, signing servers, and key management are separate attack surfaces.
For example, if only the contract handling deposits is in scope, the audit can examine that contract’s permissions and asset-transfer design. However, that does not mean it has also assessed tampering with the interface that prompts users to connect their wallets, or what happens if a backend private key is leaked. Documenting exclusions in the report is another important audit outcome.
OWASP SCSVS provides criteria that support smart contract assessments, but it is not a standard for assessing an entire conventional web application. When commissioning a Solana program audit, do not assume that EVM-oriented checks can be applied unchanged. Confirm the methodology and the reviewers’ familiarity with the target language and framework.
Actual reports also explicitly state exclusions. Halborn’s audit of 1Win’s Solana program excludes third-party dependencies and economic attacks. Consider whether these need a separate assessment for your own service as well.
This report uses cargo audit to check dependencies against known vulnerabilities. This is separate from including the third-party dependency code itself in the audit scope, so please confirm how far the review extends.
Wallet connection and user authentication are also different things. The Sign-In with Ethereum specification defines the message to be signed, including the domain, nonce, chain ID, and time. The signature is supplied separately and verified against the message. Communicate which conditions are verified on the server and what users are allowed to do after login as part of the audit scope. If you use Anchor on Solana, one topic to address is how signers, owners, and relationships between accounts are checked using account constraints.
| Area | Scope to communicate when requesting a quote | What to check |
|---|---|---|
| Smart contracts | Chain, target files, commit, dependencies | Permissions, asset transfers, external calls, upgrades |
| dApp interface and APIs | URLs, repositories, authentication methods, test environment | Wallet connections, authorization, inputs, API configuration |
| Keys and operations | Administrator privileges, signing flow, external services | Who can perform which operations, and how keys are stored and changed |
| Integrations | Oracles, bridges, external protocols | Assumed trust relationships, impact of failures, exclusions |
Prepare the Information Needed for a Quote in Four Parts
First, share the target chain, language, repository, target files, and the commit to be fixed for the audit. In addition to the number of contracts, explain integrations with external protocols, upgrade functionality, administrator privileges, and oracle use. Even with the same line count, different specifications and dependencies change the work needed for the assessment.
Next, explain the intended usage and the assets you want to protect. For example: “Users can deposit tokens, and administrators can update settings,” or “Prices are obtained from an external oracle.” Without a specification, it becomes harder to determine whether the code behaves as intended.
Also decide which deliverables you need. Confirm whether you need a report covering the evidence and reproduction conditions for findings, their impact, proposed fixes, and exclusions, as well as how many rounds of post-fix verification will be provided and what they will cover. Depending on your intended use, discuss whether a public report and a private detailed report can be provided separately.
Finally, communicate your preferred schedule and constraints. Work backward from the release date to allow time for the initial review, fixes, and verification. Before signing a contract, also confirm taxes, additional fees, confidentiality, and source-code handling in writing.
Example Request
The following is a fictional example. Replace the chain and amount of code with the details of your actual project.
We are considering an audit of a deposit dApp running on EVM. The scope covers contracts for deposits, withdrawals, and administrator settings, and we will fix the commit at the start of the audit. The application integrates with an external oracle, and administrators can change settings. Please provide a quote that includes manual smart contract review, the evidence supporting findings, proposed fixes, and post-fix verification. Please also advise whether the frontend and APIs require a separate assessment, and explain the terms with and without them included in the scope.
This request makes differences in scope explicit and allows you to obtain comparable quotes from multiple providers. Before sharing code, it is also important to confirm confidentiality and access arrangements, and to limit permissions to what is necessary.
Compare Expertise and Scope Before Price
The ethereum.org security guide lists testing and security measures during development in addition to audits. An audit is an assessment of a defined scope at a particular point in time; the absence of findings is not proof of security. Decide in advance what should be checked again after changes to code or configuration.
Ask prospective providers about their experience with the target chain, who will perform the review, exclusions, post-fix verification, and previous public reports. As a public example, the Arbitrum audit report list contains multiple third-party reports organized by assessed component. When commissioning your own audit, checking how the scope and assessed version are documented in reports can help align expectations for the deliverables.
When looking for providers to request quotes from, OpenZeppelin advertises audits for Solidity, Cairo, Rust, and other languages, while CertiK advertises smart contract audits across multiple chains, including Ethereum and Solana. For either provider, confirm the scope available for your specific project, pricing, schedule, and verification terms when making your request. These two companies are examples of potential providers, not an exhaustive list or a ranking of recommendations.
In addition, OtterSec lists areas of coverage that include EVM and Solana, while Trail of Bits indicates that its evaluations cover bridges and off-chain infrastructure in addition to contracts. Quantstamp also lists audits for Ethereum, Solana, and others. In all cases, what is included in an individual engagement needs to be confirmed.
Even when prices are published, the code in scope, review method, verification, taxes, and additional fees may not match. Avoid choosing solely on the basis of the average or lowest published price before you have quotes with aligned terms.
Common questions
How should audit costs be compared?
Align the scope, review method, retesting, taxes and extras, then request quotes from providers.
Does code analysis replace an independent audit?
No. Findings assist review but do not replace an independent expert assessment or human judgment.
How Hi AUDIT Agent can help
Hi AUDIT Agent lets you access code analysis for web applications, EVM smart contracts, and Solana programs from an MCP-compatible development environment. It can be used for reviews before submitting a project for audit or as supporting material for checks after fixes. Analysis results alone do not prove security, and the service does not replace an audit by independent experts. Before use, confirm support for your target language and framework, as well as how data is handled.
Create a Hi AUDIT Agent account