Smart contract security case studies from leading web3 protocols

For teams with a lot at stake: how L1s, L2s, zkVMs and DeFi projects found bugs before their users did, and which tool proved each one.

More smart contract and ZK security case studies

Each case names the protocol, what was found, how it was found or proved, and the number that matters.

zkVM

critical bugs caught before external audits
3

Succinct verified the SP1-Hypercube zkVM with Picus

Picus caught 3 critical underconstrained bugs in the DivRem circuit, then verified every RISC-V chip and the SHA-256 and Poseidon2 precompiles. Succinct has since caught another critical bug on a new chip, on its own, through AuditHub.

Layer 2 & ZK Provers

circuits proven deterministic
21/26

Matter Labs verified determinism in ZKsync Airbender

Before the V2 prover, Picus proved 21 of 26 circuits of the STARK-based RISC-V zkVM deterministic. 3 critical soundness bugs were fixed: one found by Picus, two by manual review of the verifier.

Multisig & key management

issues found and fixed before production
6

Mina Multisig hardened its FROST integration

A line-by-line manual review found 1 high, 2 medium and 3 low issues before the first production deployment by Nori. Findings and fixes were tracked in AuditHub.

One mechanic on your code: the agent finds, the tool proves

AI agents review your code and report what they find. Vanguard, OrCa, ZK Vanguard or Picus then checks each finding and returns the evidence your team acts on.

Scout AI - Findings

HighNeeds Review

Line 10

Signal r may be underconstrained

divide.circom:10
agent-findingcircuits/divide.circom

Picus - Evidence

Unsafe

Circuit is nondeterministic

Two distinct witnesses satisfy the constraints.

Witness 1, q2
Witness 2, q1

// COUNTEREXAMPLE FOUND

View both witnesses

Find your bugs before your users do

Run the same security tools on your smart contracts and ZK circuits.