Skip to content

Explained · Initiative 1 of 3 · 14 November 2026

Proof Before Sign, explained

Was the code you are about to sign actually reviewed? A plain account of the problem, what we found and what other tools already do.

In short

When you press Confirm in your wallet, you trust code you can't see, usually because the protocol says it was audited. But an audit covers one version of the code, and your transaction runs whatever is deployed today, often through a proxy that can be pointed at new code.

Proof Before Sign answers one question in the wallet, before you sign: for each contract this transaction will call, is there public evidence that this exact code was reviewed?

1. The problem

A DeFi transaction rarely touches one contract. A USDC deposit into Aave V3 goes through the Pool proxy, its current implementation, several libraries, the price oracle and the token contract itself. Each of these can have a different audit history, or none.

Audit reports are PDFs on a protocol's website or GitHub. They name a commit and a list of files. Nothing connects that list to the address your wallet is about to call, so the wallet can't tell you whether they match.

2. What we found

We ran 12 real Ethereum mainnet transactions through our live checker and looked at every contract call they make, 97 in total (see all 12).

Evidence for the 97 calls
EvidenceCallsWhat it means
Byte-for-byte match2The deployed code is identical to a rebuild of the commit an audit report names.
In audit scope74An audit report names the source file. Nobody has yet compared the deployed code with the reviewed commit.
No audit found21We read the protocol's published reports and none names the file. A report we haven't collected may still cover it.

One example: an Aave V3 USDC supply makes 14 calls. 12 run code in files an audit report names. The other 2 are the USDC token itself, whose v2.2 audit by Halborn has not been published (open the breakdown).

Exact rebuilds are possible but rare. The Aave V4 Spoke implementation rebuilt from commit cdacec5, which ChainSecurity's 23 March 2026 report lists as its final reviewed version, matches the deployed code byte for byte (evidence).

Those three levels of evidence are very different. In the wallet today they all look the same: a Confirm button.

3. What other tools already do

Good tools already protect people at signing time. Each answers a different question.

Existing tools and the question each answers
ToolWhat it doesThe question it answers
MetaMask Security Alerts, with BlockaidSimulates the transaction and checks it against threat intelligence for scams, malicious approvals and flagged addresses.Is this a known attack?
MetaMask transaction simulationPredicts the balance changes the transaction will cause.What will move out of my account?
Etherscan contract verificationConfirms that published source code compiles to the deployed bytecode.Is this the source of the deployed code?
Protocol audit pages and DefiLlama audit linksList the reports a protocol has published.Has this protocol ever been audited?

None of them says whether the specific code your transaction runs is the code an auditor reviewed. That is the gap Proof Before Sign works on, and it sits alongside these tools: a wallet can show a scam warning, a balance preview and audit evidence on the same screen.

4. What Proof Before Sign adds

  • For each call in the transaction, the audit evidence that exists: an exact match, a file in an audit's scope, or none found. Each claim links to the report, page and quoted line.
  • Upgrades since the audit: if a proxy now points at different code, the evidence for the old code does not carry over.
  • Signed results, so a wallet or agent can check the answer came from our service and was not altered.
  • Rules for AI agents: an agent that signs for its owner can be set to refuse when the evidence the owner requires is missing.

It runs today as a MetaMask Snap in MetaMask Flask (install status, public source). Ordinary MetaMask needs MetaMask's approval first.

5. What it does not claim

  • Reviewed code can still have bugs. A match only tells you what was checked.
  • "No audit found" means we found no matching public evidence. It does not mean the code is unsafe, or that it was never audited.
  • We are not an auditor and do not give security ratings.

References

  1. 12 recorded transaction checkshttps://proofofaudits.com/demos/proof-before-sign
  2. Ten-protocol function explorerhttps://proofofaudits.com/explorer/functions
  3. Aave V4 exact-rebuild evidencehttps://proofofaudits.com/deployed/evidence/aave-v4
  4. Snap source codehttps://github.com/ProofOfAudits/proof-before-sign-snap
  5. Full whitepaperhttps://proofofaudits.com/whitepapers/proof-before-sign
  6. MetaMask Security Alerts by Blockaidhttps://metamask.io/news/metamask-security-alerts-by-blockaid-the-new-normal-for-a-safer-transaction
  7. MetaMask transaction simulationshttps://support.metamask.io/manage-crypto/transactions/simulations/
  8. Etherscan contract verificationhttps://docs.etherscan.io/contract-verification
  9. Ethereum Foundation, Trillion Dollar Securityhttps://ethereum.org/reports/trillion-dollar-security/