Skip to content
PINNED AT BLOCK 26,392,435 · SNAPSHOT 0xb91f33be…222a54 · 10 PROTOCOLS · 656 FUNCTIONS · 26,403,76626,403,76526,403,724

See who audited the code before you sign.

Proof of Audits checks every contract your transaction touches and shows which calls were audited, by whom, and what changed since.

  • Recorded data
  • 10protocols
  • 656callable functions
  • 20reports with cited scope
  • 12signed checks recorded
  • pinned block26,392,435

A real check

One supply on Aave, 14 contract calls.

This is the signed check we recorded for Aave V3 · supply 100 USDC, rendered with its real data. Open any row to see the report, page and quote behind it.

FIG 1Recorded signed check · Aave V3 · supply 100 USDCblock 26,404,833 · 13 Nov 2026

Before you sign

Aave V3 · supply 100 USDC

EthereumBlock 26,404,833

14calls checked

12
In audit scope
2
No audit found

14 calls checked · 12 in audit scope · 2 no audit found

Reviewers

  • Trail of Bits
  • MixBytes
  • ABDK Consulting
  • Blackthorn
  • Certora

Call breakdown

In execution order. Open a row to see its sources.

In audit scope: file named in the report's scope; code match not yet checked.

Who can change this

  • A single wallet (0xfcb1…ae3a) is the owner of FiatTokenProxy and FiatTokenV2_2. No timelock is recorded.

Not established for 7 other contracts: InitializableImmutableAdminUpgradeabilityProxy, PoolInstance, SupplyLogic, VariableDebtTokenInstance, ATokenInstance, DefaultReserveInterestRateStrategyV2, RewardsController.

12 of 14 calls run code named in a public audit report, but none has been matched byte for byte to the reviewed code yet.

View details

Signed response (JSON) · Signature verified: a signed observation, not an assured proof

Proof of Audits release: not yet — needs 2 independent reviewers

What you're looking at

  1. 01

    The transaction. What you are about to sign, the network and the block we checked it at.

  2. 02

    Calls checked. Every contract call the transaction makes, counted by status.

  3. 03

    Reviewers. The firms whose public reports name the code those calls run.

  4. 04

    Call breakdown. Each call in execution order. A row opens to its report, page and cited quote.

  5. 05

    Who can change this. Owners and upgrade admins recorded for the contracts, and any timelock.

The four statuses

Byte-for-byte match
Deployed code is the build of the reviewed commit.
In audit scope
A public audit report names the file this code comes from.
No audit found
The report we hold for this protocol lists its files and does not name this one.
Not checked
Our evidence cannot say either way.

File named in the report's scope; code match not yet checked.

02Catalog

Ten protocols, every callable function. Open any.

Pinned at block 26,392,435. Each function is checked against the public audit reports we hold for its protocol, with the cited file list.

Rebuilt byte for byte from the reviewed commit

Two deployed contracts outside the catalog, compiled from the commit their audit report names. The bytes match.

  • Byte-for-byte matchChainSecurity

    Aave V4 SpokeInstance

    0xabd0…d8b5 · commit cdacec509e · 0 reviewer approvals

    Open the record
  • Byte-for-byte matchdapp.org

    Uniswap V2 USDC/WETH Pair (UniswapV2Pair)

    0xb4e1…c9dc · commit 816075049f · 0 reviewer approvals

03How it works

From the report to your call, one link at a time.

Aave V4 Spoke on mainnet, rebuilt from the audited commit. The build matches byte for byte. It is still not a released audit.

FIG 2.0Aave V4 Spoke · exact build matchEthereum mainnet
  1. 01

    Report

    ChainSecurity
    Aave V4 · 23 March 2026
    sha256
    2caa833f0b…4e8330

    reviewed at

  2. 02

    Commit

    repo
    aave/aave-v4
    commit
    cdacec509e4f…3b79

    compiles to

  3. 03

    Bytecode

    runtime
    0x41b906d9…b42eb6
    linked
    LiquidationLogic
    pinned at block
    26,399,480

    runs behind

  4. 04

    Proxy

    proxy
    0x94e7a5…c485
    implementation
    0xabd0e2…d8b5

    receives

  5. 05

    Your call

    Supply 1.0 WETH
    supply(uint256,uint256,address)
    recorded at block
    26,403,765

Release state: 0 of 2 reviewers signed. Not released.

Still open

  • Only one RPC provider was used. A second, independent provider still has to agree on the creation trace.
  • Release still needs a submitter, two independent human evidence reviewers and an operator signature.

04Products

Read the evidence. Fill the gaps. Stand behind the scope.

  • FIG 3.1Proof Before Sign

    Proof Before Sign

    Availability: Preview

    The panel above, inside your MetaMask confirmation.

    12 signed checks recorded

    Learn about Proof Before Sign
  • FIG 3.2Audit Contests

    Audit Contests

    Availability: Intake open

    Get the code no audit covers reviewed next.

    72 catalog functions with no audit found

    Explore audit contests
  • FIG 3.3Bonded Campaigns

    Bonded Campaigns

    Availability: In development

    Reviews backed by a reviewer bond. Financial terms are not final.

    Stake to Audit: 258 forge tests passed, 0 failed

    Read about bonded campaigns

Try it in MetaMask.

Proof Before Sign runs in MetaMask Flask today. Public install in ordinary MetaMask is waiting on MetaMask.

Checking install status

Proof Before Sign is built by Proof of Audits. It is not a MetaMask product.

Not using MetaMask? Waiting list: Join the waiting list

Honest status

Proof Before Sign
Preview
Published for MetaMask Flask. Public install in ordinary MetaMask is pending MetaMask approval.
Bonded Campaigns
In development
Running on a test network. Financial terms are not final.
Proof of Audits release
Not yet
Proof of Audits release: not yet — needs 2 independent reviewers. What is known today is above: cited report scope for 584 catalog functions and 2 byte-for-byte matches.

Questions

Is this another wallet?

No. Proof Before Sign adds a panel to the MetaMask confirmation you already use. It cannot move funds, and you still decide whether to sign.

Does it replace an audit?

No. It shows evidence from audits firms have released and checks it against the live code. To get code reviewed, a protocol can start an audit contest.

What happens when code changes?

If a contract is upgraded or its live code no longer matches the audited build, that part reads “Changed since audit” until a new audit is released.

What if no audit evidence exists?

The call reads “Not audited”, and you still see the facts: the proxy, its implementation and who can upgrade it. Missing evidence never reads as safe.

Can Proof of Audits guarantee a transaction is safe?

No. An audited contract can still contain vulnerabilities. A match only says the live code is the code that was audited.

How do protocols, firms and auditors take part?

Protocols add their contracts and can start an audit contest. Audit firms register and push audits by API. Auditors publish rates on Audit Rental.