Deployed/Live code match and reproducible builds
What you get · Deterministic evidence
Live code match and reproducible builds
See whether the bytecode users touch still matches audited commits — and what changed if it does not.
AAVE V4 · PUBLIC BLOCK SNAPSHOT
chain 1 · block 25,596,250
8 contract addresses · 8 runtime hashes
Core Hub 0x6fe3bd0c490eec49…
Main Spoke 0xd5a0f33aeed2fcb3…
audit-to-commit mapping remains open
independent public evidence, not a safety conclusion
What you get
Deployment registry
Chain ID, target address, purpose, production vs deprecated labels.
Proxy and implementation graph
Proxy, implementation, beacon, and facets resolved at a reference block.
Isolated rebuilds
Audited commits rebuilt with compiler, optimizer, libraries, and constructor inputs.
Match status
Exact match, changed, legacy deployment, or unknown — never inferred from the protocol name.
Diff surfaces
Bytecode, storage layout, and configuration deltas when the match fails.
How it works
01
Freeze reference
Pick a finalized block per chain and freeze intake inputs.
02
Scan live code
Bytecode and proxy resolution from dual RPC providers.
03
Rebuild audits
Isolated container builds; network off by default.
04
Compare and label
Status chips plus an evidence class on every claim.