Best Sonic and Fantom Smart Contract Auditors
Part of our guide to Web3 penetration testing

Quick answer. On public Sonic and Fantom reports, Certora (8 of 8) and OpenZeppelin (7) lead, both from Sonic Gateway audits. Cantina (Spearbit), Sigma Prime and Quantstamp score 6. Guardian, the publisher, lists itself first and scores 5 from historical Fantom work.
Video transcript
Sonic is EVM-compatible, so most auditors can read your code. Few have public reports on Sonic's own bridge, staking or DeFi stack.
Sonic launched in December 2024 as a new chain, not a renamed Opera. Opera stays live until at least the end of 2026, so migration and bridge logic belong in scope.
We scored seven public reports on one eight-point rubric: traceability, chain relevance and stack depth. Logos and library size earn nothing.
Guardian publishes this guide and lists itself first, at five of eight from historical Fantom work. Certora leads with eight, OpenZeppelin has seven, and Cantina, Sigma Prime and Quantstamp score six.
Points measure what a report shows, not review quality. Certora's report is still labeled Draft, and its proofs hold only under stated assumptions.
An Opera audit does not carry over to Sonic automatically. OpenZeppelin's Opera bridge review found two Mediums, both resolved: message hashes lacked the chain ID and contract address, and deployment configuration had wrong chain IDs. Review chain IDs, addresses and settings for each Sonic deployment.
Run the same checks on every firm, Guardian included. Name the chain and commit, state the bridge path, test pending claims, scope offchain parts, and treat Acknowledged as accepted risk.
Read the full comparison for every score and source. Migrating to Sonic? Send Guardian your commit, bridge path and admin roles for a scoped quote.
Why Chain Evidence Matters
Sonic is EVM-compatible, so most Solidity auditors can read your code. Fewer have public reports on Sonic's own bridge, staking or DeFi stack.[1]
Teams still on Fantom Opera face a second question: what moves to Sonic, and over which bridge. That puts migration and bridge logic in scope.
This list compares only auditors with public Sonic or Fantom work, scored on what their reports show. Our top smart contract auditors ranking scores firm-wide libraries instead.
Sonic and Fantom at a Glance
Sonic launched on December 18, 2024 as an EVM-compatible layer 1.[1]
It is a new chain, not a renamed Opera. Mainnet uses chain ID 146 and the native token S.[2, 3]
On April 7, 2026, Sonic Labs said Opera would retire on June 30. On June 23 it reversed that plan.[4]
Opera now stays live until at least the end of 2026, with the bridge funded regularly. That is a floor, not a shutdown date.[5]
Sonic Labs updates on August 6 and September 21, 2026 did not change that commitment.[6, 7]
The node software keeps changing. Version 2.2.7, released November 16, 2026, corrected RPC, tracing and simulation methods.[8]
The Sonic Gateway moves assets in stages: deposit, heartbeat, then claim. For USDC, the Gateway uses Circle's CCTP V2.[9]
Sonic Labs lists five audits of its core code: three firms on the Gateway, OpenZeppelin on the FTM-to-S bridge and Quantstamp on the SFC.[10]
How We Scored Them
We scored seven public reports on one eight-point rubric. Logos, library size and tool names earn nothing.
Points measure what a report shows, not review quality. Severity labels differ by firm, so finding counts are not compared.
Guardian publishes this guide and lists itself first. On the same rubric it scores 5 of 8, the lowest of the six.
Everyone else is ordered by score. Ties go to the most recent scoring report, then alphabetically.
| Criterion | What earns points | Max |
|---|---|---|
| Traceability | Dated report, scoped commit or address, status per finding | 3 |
| Chain relevance | 2 for Sonic or Sonic ecosystem work; 1 for Fantom only | 2 |
| Stack depth | Integration logic, offchain or deployment scope, named formal properties | 3 |
Sonic Auditors Compared
Scores are traceability, chain relevance and stack depth, in that order.
Among the 6s, Cantina's report (October 2025) is newest, then Sigma Prime's (April 2025), then Quantstamp's (October 2024). Cantina's chain points come from Silo's Sonic markets and Spearbit's Beets work.[11, 12, 13, 14, 15]
Trail of Bits is also a candidate. Beets names it, with Spearbit, as an auditor of its stS staking contracts on Sonic.
Trail of Bits' catalog lists BeethovenX Sonic Staking under January 2025, with a security assessment and fix review. We could not verify its scope, commit or finding statuses, so it is unscored.[16]
| # | Firm | Score | Public Sonic or Fantom evidence | Best fit |
|---|---|---|---|---|
| 1 | Guardian | 5 (3+1+1); listed first as publisher | Ultimate Fantoms review, May 2022 | Contract review with a retained invariant suite |
| 2 | Certora | 8 (3+2+3) | Sonic Gateway manual review and formal verification, 2024 | Bridge solvency and claim properties |
| 3 | OpenZeppelin | 7 (3+2+2) | Sonic Gateway; Opera native token bridge, 2024 | Bridge contracts, Go relay code, deployment scripts |
| 4 | Cantina (Spearbit) | 6 (3+2+1) | Silo dynamic kink model, October 2025; Beets stS | DeFi components and liquid staking |
| 5 | Sigma Prime | 6 (3+2+1) | Silo V2 Core, April 2025 | Lending, interest-rate and liquidation logic |
| 6 | Quantstamp | 6 (3+2+1) | Sonic Gateway contracts, October 2024; SFC | Core contracts with explicit exclusions |
Fantom and Gateway Evidence
Guardian's public Fantom evidence is the Ultimate Fantoms review of May 23, 2022. It lists scoped contract addresses and a status for each finding.[17]
None of Guardian's 300+ public reports mentions Sonic, which is why it earns one chain point, for Fantom.
Guardian's standard audit does not include offchain coverage, so Gateway-style relayers or signers need their own scope.[18]
Certora reviewed the Gateway from September 26 to October 14, 2024, at commit 558465d. Scope covered the contracts plus the cmd and internal directories.[19]
It wrote formal properties for solvency, duplicate claims and token pairs, and recorded 13 findings, seven of them fixed.
The public report is still labeled Draft. Its proofs hold only under stated assumptions about validators, modeling and loop bounds.
To weigh proofs against fuzzing for your own code, see formal verification vs fuzzing vs audit.
OpenZeppelin audited the Gateway from September 24 to October 21, 2024, at commit 558465d, covering Solidity plus Go relay, voter, RPC, signing and validator code.[20]
Its report marks 2 of 25 issues resolved, the one High and one of three Mediums.
Its Opera native token bridge review, November 13 to 15, 2024, covered the contracts and Hardhat Ignition deployment scripts and parameters.[21]
That review rests on stated trust assumptions about privileged administrators and validators.
Quantstamp's final Gateway report is dated October 17, 2024. It reviewed the Solidity at the same commit, 558465d, limited to the contracts directory, so the SFC dependency sits outside it.[13]
Sonic DeFi Auditors
Silo's February 2025 governance post confirms Silo V2 markets ran on Sonic and says Silo was completing V2 core audits with Sigma Prime and Spearbit Cantina. Its audit index separates V3, V2, vault and component reports.[14, 22]
The V2 report Silo links under Spearbit Cantina is a Cantina Competition, run January 13 to February 10, 2025, at commit 339e023.[23, 24, 25]
Cantina's portfolio record shows its 69 findings as acknowledged, none fixed, but lists no fix commits, so it does not show what Silo changed later.
Cantina Managed reviewed Silo's dynamic kink model from September 23 to 30, 2025, at silo-contracts-v2 commit 499f0ce6. The report, dated October 3, names its researchers.[11]
A follow-up review at f12498e3 found all four findings addressed. It is a component review, not a V3 core audit.
Silo's index files it under a separate Dynamic Interest Rate Model section, and lists a different Spearbit Cantina report under V3.
Silo's registry names a Sonic KinkIRM test market, and its changelog records the SiloDeployer redeployed with an audited Kink version in October 2025, but neither ties a live Sonic market to the reviewed commit.[26, 27]
Ask whether you are buying a Cantina Managed review, a Spearbit team or a competition. They are different products.
Sigma Prime's April 2025 Silo Core report scopes lending, configuration, interest-rate, liquidation and utility contracts, and excludes third-party dependencies.[12]
Silo's index lists it under V2. It reviewed commit 6631f79, assessed fixes at 8def80e, documents tests, and separates Closed findings from Resolved ones.
Silo's deployment register maps Sonic markets to releases: IDs 1 to 12 on 0.18.0, 13 to 99 on 1.1.0, 100 on 3.4.0, and 101 onward on 3.5.0.[28]
It does not show that any market matches either audited commit. Check the bytecode behind the market you integrate.
What to Check Before Signing
Run these checks on every firm on your shortlist, Guardian included. The full process is in how to choose a smart contract auditor.
Guardian's UF-1 finding shows why roles belong in scope: a single non-multisig owner could change routers, mint size and base URI, and sweep the contract's balance. It was a Medium, marked Acknowledged.[17]
For Gateway or other bridge integrations, our cross-chain bridge audit guide covers relayer, configuration and deployment scope.
- Chain and commit: name Sonic or Opera, the exact commit and the deployment configuration in the scope.
- Runtime: test against the Sonic node and RPC versions you will run, and record both in the report.
- Bridge path: state whether assets arrive through the Gateway's batched route, its CCTP V2 route for USDC, or a third-party bridge.[9]
- Pending claims: test what happens to deposits awaiting a heartbeat when you pause, upgrade or migrate.
- Offchain parts: put relayers, signers and keepers in scope, or exclude them in writing.
- Trust assumptions: require a list of every admin, validator and oracle the report assumes behaves correctly.
- Dependencies: ask which libraries and system contracts, such as the SFC, were excluded.
- Privileged roles: list who can change configuration or move funds, and whether each is a multisig.
- Fix status: require a remediation commit, and treat Acknowledged as accepted risk, not a fix.
- Formal claims: read the assumptions and loop bounds behind any proof before relying on it.
Frequently Asked Questions
Does a Fantom Opera audit still apply on Sonic?
Not automatically. OpenZeppelin's Opera bridge review found two Mediums, both resolved: message hashes lacked the chain ID and contract address, and deployment configuration had wrong chain IDs. Have chain IDs, addresses and settings reviewed for each Sonic deployment.[21]
Does Sonic Labs certify or recommend auditors?
Its audits page records reviews of its own code; it is not an approved-provider list. Its Innovator Fund advertises up to 200,000,000 S for adoption and new ventures, but publishes no audit-specific terms or auditor list.[10, 29]
What controls should a Sonic staking audit confirm?
Roles and delays. Beets' stS docs put upgrades behind a 5-of-7 multisig and a three-week timelock, while a 3-of-6 operator multisig, with no timelock listed, can pause deposits and withdrawals. An audit should confirm the code enforces what the docs promise.[15]
Related reading
- top smart contract auditors
- how to choose a smart contract auditor
- cross chain bridge audit
- best arbitrum auditors
- formal verification vs fuzzing vs audit
Sources
- Sonic Labs: Sonic Mainnet Launch
- Sonic Labs: Sonic Getting Started
- Sonic Labs: Sonic's Successful Network Migration
- Sonic Labs: The First 1%
- PANews: Key News from Last Night and This Morning
- Sonic Labs: Approaching Day 50 and looking beyond
- Sonic Labs: Day 100 - Where We Are, And Where We're Headed.
- Sonic Labs: Sonic Version History
- Sonic Labs: Sonic Gateway Documentation
- Sonic Labs: Sonic Audits
- Cantina Managed; published by Silo Finance: Silo Finance Dynamic Kink Model Security Review
- Sigma Prime; published by Silo Finance: Silo Core Security Assessment Report
- Quantstamp; public copy hosted by CryptoCompare: Sonic Gateway Report
- Silo Finance governance: Looking Ahead to 2025
- Beets: Beets Staked S Security
- Trail of Bits: Publications from Trail of Bits
- Guardian: Ultimate Fantoms Protocol Review
- Guardian: Smart Contract Audit Services
- Certora: Sonic Gateway Security Assessment and Formal Verification Report
- OpenZeppelin: Sonic Gateway Audit (December 13, 2024)
- OpenZeppelin: Sonic Opera Native Token Bridge Audit (December 9, 2024)
- Silo Finance: Silo V3 Audits and Formal Verification
- Cantina; hosted by Silo Finance: Silo contracts v2 Competition
- Cantina: Silo Finance / silo-contracts-v2 competition
- Cantina: silo-contracts-v2: Cantina Security Report
- Silo Finance: Silo market deployment registry
- Silo Finance: Silo contracts changelog
- Silo Finance: Deployed Silo Lending Market Versions
- Sonic Labs: Innovator Fund
- Certora: Sonic Bridge (December 6, 2024)
- Guardian: Abracadabra Money Arbitrum MIMv2 Migration
- Silo Finance: Interest Rates
- Sonic Labs: Sonic in 2026 and Beyond
Deploying or Migrating to Sonic?
Guardian's smart contract audit puts two independent teams on your Sonic contracts, with a fix review and an invariant suite you keep. Send your commit, bridge path and admin roles for a scoped quote.