Smart Contract Audit for Teams Launching or Upgrading Contracts
Protofire reviews contracts that another team wrote, at named commits. We also prepare code for an outside firm's audit and check each fix against its finding. Each finding has a severity, a commit and a status. We maintain Solhint, a Solidity linter the Ethereum Foundation funded in three allocations.

Reviewed by Luis Medeiros, Field CTO at ProtofireLast reviewed: November 2026
On this page
Work shipped for 60+ networks and 95+ protocols, including
Who has read your code, and at which commit
A smart contract audit answers the question of who read your code only when the report names the files and the commit it covers. For example, the contracts are frozen and the launch date is fixed. Then an investor, a listing venue or your own board asks who has read this code, and at which commit.
Protofire does three jobs under the name smart contract audit. We review code another team wrote. We prepare code ahead of an outside firm's audit. We check each fix against its finding. Your team decides on each finding and on the launch.
Who handles each step from a frozen commit to deployment
Your team holds the code, the decision on each finding and each role once the contracts deploy. Protofire prepares code and reviews it, and an outside firm audits code Protofire wrote.
Repository, commit and role map
Decision on each finding
Pre-audit preparation
Review and report
Fix review
Independent audit of code Protofire wrote
Deployment and roles
What a smart contract audit report covers and leaves out
An audit report speaks for the files in scope at the commits it lists, and a launch can move past both.The report does not speak for code merged later, a privileged role left on one key, or an oracle or bridge outside the file list. The report also does not speak for findings your team chose to acknowledge.
The 2026 edition of the OWASP top ten for smart contracts ranks access control first, business logic second and price oracle manipulation third. A reviewer can judge access control and business logic only against your own documents and role map. If the documents and the role map are not written, the review is thinner. If the launch moves after the review, nobody can say whether the report describes what is deployed.
Who may review your code independently
The team that wrote the contracts can review them, but that review is not independent.So Protofire reviews code other teams wrote, and code we wrote is handed to a firm outside Protofire. Protofire writes contracts as its smart contract development service. For that code, we prepare the commit and fix what the outside firm finds.
Some buyers' rules ask for more. DORA applies from 17 January 2025 to EU financial entities, among them crypto-asset service providers and issuers of asset-referenced tokens. Financial entities other than microenterprises must have tests "undertaken by independent parties, whether internal or external" (Article 24(4)). Delegated Regulation (EU) 2024/1774 also asks for source code reviews "covering both static and dynamic testing" (Article 16(3)). Protofire's DORA guide covers third-party risk for onchain providers.
Before a licensed virtual asset trading platform in Hong Kong admits a token, the SFC's guidelines ask the platform to appoint an independent assessor. The assessor audits the token's contracts (paragraph 7.10 of the SFC's guidelines). Your counsel judges whether DORA or the SFC's guidelines bind your firm.
What Protofire delivers before your launch or upgrade
A review of code another team wrote, with a written report
Your launch rests on a report that names the repository, the commits and the files in scope. The report lists each finding with its severity and status. Protofire reviews code another team wrote against your documents and role map. Where the written scope names them, we add fuzzing, invariant testing or formal verification.
Pre-audit preparation for an outside audit firm
An outside audit firm gets a frozen commit, a role map and documents, so the firm spends its hours on your logic. Protofire writes the role map and its trust assumptions and adds NatSpec. We run linting and static analysis in CI, and each warning is fixed or explained. We prepare code another team wrote and code we wrote.
A fix and a fix review for each finding
A finding ends with a status linked to a fix commit. Your report or the outside firm's report can cite that status and its commit. On code Protofire wrote, or code your team asks us to change, we commit one fix per finding with a test that reproduces it. When your engineers write the fixes, we read each fix commit against its finding.
A separate review for each proxy upgrade
An upgrade of a deployed proxy is a new commit, so an earlier report does not apply to the upgrade. Protofire reads the diff against the deployed implementation. We also read the storage layout, the initializer calls and the upgrade transaction your team will sign.
Audit firms, audit competitions and bug bounties compared
Protofire's 2024 reports recommend several independent audits and a public bug bounty program.Each option leaves something different open.
A Protofire review
What it is for: Protofire reads contracts another team wrote at named commits, against your documents and role map. We check each fix against its finding.
What it leaves open: The review does not cover commits after the last one listed, or files outside scope.
A dedicated audit firm
What it is for: Staff who did not work on the code give an independent review. A regulator, listing venue or investor may ask for that kind of review.
What it leaves open: The firm's own report states the same limits of scope and commit.
An audit competition
What it is for: Many researchers read one frozen codebase in the same window and are rewarded for valid findings.
What it leaves open: Coverage depends on who takes part. The findings still need triage, fixes and fix review.
A bug bounty
What it is for: Researchers test code over time, mostly after launch. They are paid under the program's terms for valid reports.
What it leaves open: Researchers are paid per report, so nobody is bound to read the whole codebase.
Our record: Solhint, a Certora audit and our review reports
Two outside records show how Protofire treats contract code.Our own review reports are collected on one page.
- SolhintProtofire created Solhint, a Solidity linter, and we still maintain it. The Solidity documentation lists Solhint. Its first release came in 2017, and npm has served it 25M+ times. The Ethereum Foundation's Ecosystem Support Program funded our work on Solhint in Q4 2022, Q4 2023 and Q1 2025. The Q1 2025 funding was for ongoing maintenance and support.
- An outside audit of code we wroteProtofire built the ve8020 Launchpad alongside Balancer's core team, as the Balancer case study describes. Certora audited the Solidity contracts of the Launchpad and published its report in March 2024. The Certora audit shows the practice Protofire follows for its own code: people who did not write the code read it.
- Our reviews of other teams' codeProtofire's audit reports page lists the reports we have published, and the earliest is dated November 2024. Each report lists the repository, the commits reviewed and a status per finding.
Together, these records show the tooling Protofire maintains and our habit of having outsiders read our own code.
How a Protofire review runs, from frozen commit to deployment
You send read access to the repository at the frozen commit, with your documents and the role map.You also send a test account for each role on a testnet or fork. The review touches no deployed contract. The first written proposal fixes the scope, the commit and the methods.
- Step 1
Your team freezes the commit
You name the repository, the commit and the files in scope. The report opens with the review dates and the repository. It also lists the full commit hashes and the contracts in scope. - Step 2
The reviewer logs each finding
Each finding names the file, a recommendation and the commit where it was found. Severity follows the OWASP Risk Rating Methodology, which combines likelihood and impact into Critical, High, Medium or Low. Where needed, Protofire deploys to a private testnet or writes a proof of concept. - Step 3
Your team chooses the response
Your team chooses to fix, mitigate or acknowledge each finding. An acknowledged finding is still listed in the report. - Step 4
Protofire reads the fix commit
The status then changes to "Fixed at" with the new commit hash, or to Mitigated. - Step 5
The report ends at the last reviewed commit
The final version lists each review date and commit. Code merged after the last reviewed commit has not been reviewed. - Step 6
Your wallet or Safe deploys the last reviewed commit
Your team builds the last reviewed commit with the reviewed compiler settings, deploys it and compares the deployed bytecode with that build. At this step, constructor arguments, initial parameters and the addresses each contract trusts are set. So is the choice of which key or Safe holds each role.
No amount of security review can guarantee that a smart contract is secure against all possible vulnerabilities [...]
Who holds the code, the decisions and the roles after a review
Your team keeps the code and the decision on each finding.Your team also keeps the deployment and each owner, pause and upgrade role. Protofire holds no owner, pause or upgrade role on the contracts it reviews, and it signs nothing at deployment. If a review needs deploy logs or other production data, that data comes under NDA, with user addresses stripped out.
- Proposal
- In writing, one business day after the discovery call: findings, a plan in phases and the first step we recommend.
- Price
- Fixed per phase when you commission it, against written acceptance criteria. Overruns inside them are ours to absorb, invoices follow delivered milestones, and you can stop at any phase boundary. Anything we operate after launch is priced in the proposal as its own recurring line, with the notice to end it.
- Ownership
- Code we write for you, contracts, the keys and credentials this work creates and the accounts your infrastructure runs in are yours by contract, within the license of any third-party software involved. Keys that a custody platform or a staking provider holds under its own key model stay with it under your contract; every other custody key stays with you or the custodian you appoint. Where the scope places something on servers we rent, it says what moves to you and when. An NDA is available from your first message, and we sign a data processing agreement (DPA) together with it.
- After launch
- Delivery closes with a hypercare window and a defect warranty, with their terms written into the proposal. A service we operate continues under its written scope until that scope ends.
- Access
- Read-only by default. A role that can start requests only if your written scope names one; never a signer, approver, administrator, key holder or recovery role on your contracts, wallets or custody platform. Services we build call each platform on credentials your staff issue and keep in your vault. Anything that approves or moves funds runs in your environment, and a scope under which we operate a service lists every write call it makes. Where the scope has us operate nodes, validators, monitors, explorers or indexers, it names the role and any key we hold on those servers, and in your own cloud account you can remove it.
- Licenses
- Protofire is an engineering firm and holds no financial or crypto-asset license; licensed activity stays with you and your providers.
How we work shows a worked proposal.
When a Protofire review does not fit
A Protofire review reads a fixed commit of code another team wrote, ahead of a launch or an upgrade.Other jobs call for a different service or firm.
- An independent audit of code Protofire wrote goes to an outside firm that had no hand in the code.
- Protofire's protocol rescue service starts from an exploit that is under way.
- An automated pause on a live contract belongs to Protofire's Hypernative integration service. That service builds the role or module your team grants Hypernative's keeper, and the path to revoke it.
- Protofire's QA and testing service tests the product around the contracts: front ends, APIs and user flows.
Book a review when another team wrote the code and the commit is fixed. The launch or upgrade date also needs to leave room to fix what the review finds.
FAQ
What is a smart contract audit?
Who can audit our smart contracts before launch, and how does Protofire differ from a dedicated audit firm?
Does a smart contract audit guarantee that the contracts are secure?
Can you fix the findings?
Which tools should run in CI before an audit?
What sets the scope of a review?
Get a proposal
Tell us what you are building. An engineer reads it, we have a short call, and the written proposal follows within one business day.
