ZK Verifier Audit
Static ZK tooling mostly lints the circuit; the seam it misses is where the deployed verifier's hardcoded points stop matching the audited circuit's verifying key. This page reads the verifier bytecode, extracts every 32-byte VK constant, and tells you whether the commitments you expect are bound or stale.
Embedded 32-byte constants
Every PUSH32 in the verifier. These are the candidates for generator points, IC[] entries, and VK commitments. Use them as ground truth when deriving the expected set from your circuit.
| # | Offset | Hex |
|---|
What the verdict means
- VK bound every expected commitment is embedded as a
PUSH32. Circuit is pinned to this verifier. - VK stale at least one expected commitment is missing. Likely a stale verifier or a circuit edited post-deployment. Treat as an Error-class dual-layer finding.
- VK unknown you didn't provide expected commitments. The embedded set is reported for manual comparison against the circuit's verifying key.
Select Smart Contract
Choose a smart contract from your workspace to open in this view.
Sign in to audit ZK verifiers against your workspace contracts
Use the Sign In button in the navigation bar.