The public checker and API show whether an exact contract has attested deployment proof, what changed, and what evidence is missing. Wallet integrations can use the same result contract before signing.
Public service state
Exact chain + address query. Timestamped verdict. Inspectable reason codes.
A registry miss is reported as insufficient evidence, not converted into a safety claim.
Proof of Audits does not guarantee safety. The proof service reports evidence, gaps, and risk signals for an exact contract target.
Live public proof service
Query the public Proof of Audits registry for an exact chain and address. The result is generated by the live API, not embedded page copy.
This already happened
Frozen withdrawals. Emergency war rooms. Funds gone. Every number here is someone who trusted a badge, a PDF, or a claim — and found out too late that the code, the bridge, or the signer was not what they thought. Proof has to be visible before the signature, not reconstructed after the loss.
Not one bug. Not one protocol. Live code, control keys, bridges, signers — every path where trust breaks down before the user can see it. Bitrue reported that 2026 crypto hack losses had surpassed $1.1B by June 11.
Bitrue, June 2026If nobody can see the deployed code, everyone is trusting a black box. Chainalysis found at least $36.7M stolen in six months from protocol-owned contracts with unverified source code.
Chainalysis, June 2026Cross-chain bridges failed 14 times in 2026, including the roughly $292M KelpDAO/LayerZero incident. One missing verification layer became a liquidity shock across chains.
CoinGabbar / PeckShield, June 2026Real loss: of crypto hack value through April 2026 came from two DPRK-linked attacks, per TRM Labs
Extensions from unknown sources can inject malicious code into wallet interactions. Control-plane compromise is now a major loss path — and 76% of 2026 hack value came from just two state-linked attacks.
The contract checker and public API are available now. They expose the same evidence contract a wallet integration can use, while keeping raw results open for inspection.
Anyone can submit an EVM chain and contract address and inspect the registry result without logging in or connecting a wallet.
The same public endpoint returns a machine-readable verdict, reason codes, deployment context, and an exact check time.
Wallet clients can consume the proof result. Current public access is the web checker and API, with no unverified install file required.
It moves proof from a dashboard into the wallet decision moment, so a user can see the live contract match, key control, missing evidence, and full proof trail before continuing.
Shows whether the contract and proxy implementation still match the reviewed code, or whether the live deployment changed.
Shows who can upgrade, pause, or control critical runtime paths when authority proof exists.
Flags unknown contracts, unpublished code-hash proof, pending deployment review, unresolved findings, and stale evidence.
Links from the wallet moment into the full protocol proof page, so users can inspect the evidence before continuing.
lost across 14 bridge attacks where signing-time dependency context would matter
The wallet popup says 'Confirm Transaction.' Nothing about the bridge dependency, the verifier quorum, the source verification, or the admin powers. By the time users manually research, the decision is already on-chain.
The workflow is simple: detect the target, check the proof registry, compare live deployment state, show evidence, and warn when proof is missing or stale.
A wallet integration reads the chain, target contract, method, and transaction context before the signing decision.
The exact address is checked against finalized protocol proof, deployment records, and known contract state.
Runtime bytecode, proxy implementation, and audited scope must match before a green verdict is shown.
The result returns the evidence state, reason codes, and Trust Passport link when public proof exists.
Changed, mismatched, unknown, or high-risk contracts receive a review signal before the user continues.
The trust evidence was buried in dashboards and audit pages. It never appeared at the moment the wallet asked for a signature — exactly when the user needed it most.
CoinGabbar 14 Bridge Attacks 2026The investor page is for comparison. Contract Shield is for the moment when a wallet request needs a decision.
External Deployed ITS v2 /900 score
Runtime bytecode and proxy implementation match
Changed deployment and UNVERIFIED_UPGRADE warnings
Trust Passport, VTI, and on-chain publication state
Authority-key evidence and pending key changes
Wallet request decision before signing
The wallet showed pass or fail — but not what was verified, what was missing, or what changed since the last audit. A clear verdict system could have flagged the exact gap that got exploited.
CoinGabbar 14 Bridge Attacks 2026This contract matches a finalized audited scope.
Audit evidence exists, but deployed-code verification is not finalized yet.
This protocol is known, but the contract or implementation has changed since the audit.
This contract does not match the audited scope.
No Proof of Audits evidence was found for this contract.
A warning signal was found that should be reviewed before continuing.
Proof of Audits does not guarantee safety. The proof service reports evidence, gaps, and risk signals for an exact contract target.
