Ten protocols. Every callable function.
Open a protocol, then any function. You see which public audit report names its file, who wrote it, where the call lands and who can call it. Read from block 26,392,435.
- Recorded data
- 10protocols
- 656callable functions
- 584in a cited audit scope
- 72no audit found
- 0not checked
- block26,392,435
The ten protocols
Pick a protocol.
One row per protocol build at block 26,392,435. One mark per callable function, coloured by what our evidence says about its file.
656 functions · 584 in audit scope · 72 no audit found · 0 not checked
- In audit scope
- No audit found
- Not checked
- AaveV3 · Pool revision 127573 of 75 in audit scopeReports by MixBytes, ABDK Consulting, Blackthorn, Certora, Trail of Bits
- UniswapV4 · PoolManager3331 of 33 in audit scopeReports by OpenZeppelin
- CompoundIII · USDC Comet9292 of 92 in audit scopeReports by OpenZeppelin
- MorphoBlue · core2828 of 28 in audit scopeReports by OpenZeppelin
- LidostETH core · revision 49393 of 93 in audit scopeReports by Certora, ConsenSys Diligence
- SafeSmart Account 1.4.13232 of 32 in audit scopeReports by Ackee Blockchain, Certora
- PendleV2 · RouterV4 + 7 facets580 of 58 in audit scopeChainSecurity: file list does not name these files
- SkysUSDS · pinned implementation5151 of 51 in audit scopeReports by ChainSecurity, OpenZeppelin
- EulerV2 · EVC + EVault implementation141141 of 141 in audit scopeReports by ChainSecurity
- EigenLayer1.13.0 · StrategyManager5343 of 53 in audit scopeReports by Certora, ConsenSys Diligence
Byte-for-byte matches
Two contracts rebuilt byte for byte.
For these two contracts, outside the ten catalog builds, the deployed bytecode was rebuilt from the commit an audit names and compared byte for byte.
- Byte-for-byte matchChainSecurity
Aave V4 SpokeInstance
Exact build match, not yet a released POA audit.
0 reviewer approvals · Proof of Audits release: not yet. Needs 2 independent reviewers.
FIG 5.1Deployed runtime bytecode, one dot per byte Reading
FIG 5.1 — 24,291 bytes read with eth_getCode at block 24,720,899; keccak256 0x41b906d9…b42eb6. Blue dots are PUSH4 operands, mostly function selectors.
- Deployed contract
- 0xabd0e26fe17bde4f1f1187ed8aa80c274e03d8b5 (opens in a new tab)
- LiquidationLogic
- 0x88df535473c5adf1f57789734a05e555f7deb8db (opens in a new tab)
- Runtime hash (keccak256)
- 0x41b906d9…b42eb6
- Rebuilt from commit
- cdacec509e…ee3b79Commit on GitHub (opens in a new tab)
- Audit report
- ChainSecurity, Aave V4, 23 March 2026Original report (opens in a new tab)
- Report document SHA-256
- 2caa833f0b…4e8330
- Compared at block
- 26,399,480
- Evidence files
docs/grants/thedao/submission/evidence-2026-11-12/aave-v4/Repository path in the Proof of Audits repository.- Still open
- Only one RPC provider was used. A second, independent provider still has to agree on the creation trace.
- Release still needs a submitter, two independent human evidence reviewers and an operator signature.
- Byte-for-byte matchdapp.org
Uniswap V2 USDC/WETH Pair (UniswapV2Pair)
Exact build match, not yet a released POA audit.
0 reviewer approvals · Proof of Audits release: not yet. Needs 2 independent reviewers.
FIG 5.2Deployed runtime bytecode, one dot per byte Reading
FIG 5.2 — 11,293 bytes read with eth_getCode at block 26,378,312; keccak256 0x5b83bdbc…9e9ce5. Blue dots are PUSH4 operands, mostly function selectors.
- Deployed contract
- 0xb4e16d0168e52d35cacd2c6185b44281ec28c9dc (opens in a new tab)
- Runtime hash (keccak256)
- 0x5b83bdbc…9e9ce5
- Rebuilt from commit
- 816075049f…4c07ebCommit on GitHub (opens in a new tab)
- Audit report
- dapp.org, Uniswap V2 audit report (report.org source)Original report (opens in a new tab)
- Report document SHA-256
- 3a7e01b533…ddd392
- Compared at block
- 26,399,669
- Evidence files
docs/grants/thedao/submission/evidence-2026-11-12/uniswap-v2/Repository path in the Proof of Audits repository.- Still open
- Release needs a submitter, two independent human evidence reviewers and an operator signature.
- Whether the review covers the contract or individual functions is a reviewer decision. Scope is not confirmed.
How to read it
Four words, one per function.
Each status says what our evidence holds for the file a function lives in. None of them is a Proof of Audits release.
- Byte-for-byte match
- Deployed code is the build of the reviewed commit.
- In audit scope
- A public audit report names the file this code comes from.
- No audit found
- The report we hold for this protocol lists its files and does not name this one.
- Not checked
- Our evidence cannot say either way.
Proof of Audits release: not yet for any build here. A release needs 2 independent reviewers.
Check it yourself
Block hash 0xb91f33be3eab6abc885f2ef8adfb404f72a328fb053c4a68180b635415222a54
Re-check the catalog
node scripts/verify-function-catalog.mjsRun from products/proofofaudits/frontend in the Proof of Audits repository.