Coverage
Which recorded deployments were reviewed?
A review says nothing about code that was deployed after it. This table joins the public deployment records with the review log, contract by contract.
Deployment records synced 3 Oct 2026 from deployments/8453/versions.json. The implementation addresses are a manifest snapshot, not live chain queries. Later upgrades can make them stale. Check the verified production reference and each address on Base’s block explorer before inferring current coverage.
On-chain versions were read through version() at Base block 52,128,806 on 3 Oct 2026. “Reviewed version” is the version recorded by the referenced review.
Per-contract coverage may be published before a review’s findings. This confirms only what code was examined and whether its runtime matched; it reveals no result and does not imply that no findings exist.
Proxies
Core contracts
Linked code
Libraries and helpers
Legend
What each status means
- Reviewed · live bytecode matched
- The recorded implementation is the one that was reviewed, and its bytecode matched a build of the reviewed source.
- Reviewed at source only
- The recorded implementation is the one that was reviewed, but its bytecode could not be matched to the reviewed build.
- Upgraded for a disclosed fix
- The live implementation differs from the reviewed one, but its version and deployment date match a disclosed fixed finding. This does not mean its bytecode was matched to a reviewed build.
- Other upgrade since review
- The live implementation differs from the reviewed one and is not linked to a disclosed fixed finding. This is a coverage gap, not evidence of a defect; a differential review is due.
- No published deployment check
- No published review records a check of this contract’s recorded bytecode.