Plain-English definition
What live-code match means
Live-code match checks whether the contract currently executing on-chain corresponds to the source and compiler target covered by an audit.
Proof feature 05 of 10 · verify deployed bytecode matches audited code
Verify Deployed Bytecode Matches Audited Code
Compare live runtime bytecode and proxy implementations with the audited commit using reproducible build evidence and explicit match states.
Questions this page answers
What to verify
- Which implementation address is live now?
- Can the audited source reproduce the runtime bytecode?
- Did an upgrade occur after the reviewed commit?
Evidence checklist
Evidence that makes this useful
Each item must be tied to an inspectable source or remain clearly labeled as pending, unavailable, or unidentified.
01
On-chain target
Chain, address, runtime bytecode, proxy type, and implementation slot.
02
Build provenance
Repository commit, compiler, optimizer, metadata handling, and libraries.
03
Match classification
Exact match, partial match, mismatch, unavailable, or pending review.
Decision use
How to use this proof
Use the result to determine whether an audit is current evidence for the contract users actually touch.
Proof of Audits shows evidence and gaps. It does not guarantee protocol or transaction safety.
Specific answers
Frequently asked questions
Does verified source on an explorer prove an audit applies?
No. Explorer verification links source to bytecode, while audit applicability also requires matching that source and version to the reviewed scope.
How are upgradeable proxies handled?
The proxy and current implementation must be resolved separately, and implementation changes must be compared with the audited target.