Find the flaw before someone else does
DeFi protocols hold user funds in code that anyone can read — including attackers. We read it first, prove what we find with a runnable test, and tell you how to fix it.
Just want to check a token or wallet yourself, right now? Contract Reader is the free tool below — paste an address, see what its owner can actually do.
Proof, not opinion
A finding that can't be demonstrated isn't a finding. Every issue we report comes with a test you can run yourself.
Built for what's coming, not just what's here
The next wave of DeFi is landing on high-throughput, ZK-driven, order-book-native chains — infrastructure that makes verifiable correctness the whole pitch. That only means something if someone actually reads the code and proves what it does. That's the job.
Every audit record we produce is signed with a real, published key and anchored two independent ways — a Bitcoin-based timestamp and a classical timestamp authority — then hash-chained to the one before it and cross-witnessed by four independent parties. Deleting or altering a past record breaks the chain visibly, not just for us.
16/20 · floor criteria: 6/8
See how it works, self-scored against an external standard →How we can help
A full read of your contracts with a written report. Findings are ranked by impact and each one ships with a reproduction.
See what's covered →For teams shipping continuously. New code gets reviewed as it lands, rather than once a year in a fixed audit window.
Discuss a retainer →Paste any verified contract address and see the privileged capabilities written into its code — no invented risk score, no black-box grade, just what the code says, cited to the function.
Use the tool →Where we go deep
Broad tooling finds shallow bugs. The issues that actually drain protocols live in the interaction between components — accounting that drifts, oracles that behave unexpectedly at the edges, invariants that hold in isolation and break under composition.
Transient Storage in the Wild
We measured EIP-1153 misuse across every Uniswap V4 hook on Ethereum and Arbitrum — 1,756 contracts across both chains. The reference implementations get it right, and the one dangerous pattern found in the wild — reappearing on both chains — turned out to be correctly guarded every time. Built with an open-source detector.
Shipping something that holds funds?
Tell us what you're building and where you'd want us to look. If a review isn't the right fit, we'll say so.
Start a conversation