Skip to content
Get protected

For audit firms

Put your name where users sign.

Your audit report ends in a PDF. With Proof of Audits, your firm, report and commit appear in the wallet panel when someone uses the audited contract.

Register your firmRead the API and MCP docs

Attribution shows what your firm reviewed and whether it matches deployed code. It is evidence for diligence, not a safety promise.

MetaMaskConfirm transaction

Ethereum Mainnet · Contract interaction

Proof Before Sign

Illustration with example data. Panel text comes from the Snap's own code.

The credit dies in a PDF

A firm's reputation is built one report at a time, then scattered across PDFs and links that nobody can verify at the moment it matters.

All that is left is a badge and a filename

You ship a thorough report. Months later an investor sees a static badge and a filename. They cannot tell which firm reviewed which module, or whether the review still applies to the code that is live now.

Your name outlives the commit

The commit you audited and the deployed contract drift apart. Without a hash bound to your review, your firm gets associated with code it never saw.

Individual work never rolls up

Your auditors build track records across contests and engagements, but none of it accrues to the firm. There is no single place that says this team did this work.

From registration to Audited by in the wallet.

  1. Register and get verified

    Create the firm profile. It starts pending and moves to verified after an admin review.

  2. Create a key on the firm dashboard

    Pick the scopes and an expiry for the key.

  3. Push audits by REST or MCP

    Send the report, commit and findings from your own tooling or an AI agent.

  4. Users see Audited by in the wallet

    Your firm, report and commit appear in the panel for the audited contract.
Submit an audit (REST)
curl -s -X POST https://proofofaudits.com/api/firm/v1/audits \
  -H "Authorization: Bearer $POA_FIRM_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: acme-2027-01-vault-v2" \
  --data-binary @submission.json
MCP endpoint
https://proofofaudits.com/mcp

A submission is stored as a candidate and shown to users once the evidence is released.

What your firm gets

A record of your work that investors and protocols can read in context, matched to the code it reviewed.

Attribution bound to a codebase hash

Every audit your firm submits is recorded against the exact commit hash reviewed. Investors see whether that hash still matches the deployed contract, so your review is read in the right context.

One roster, one reputation

Add the auditors on your team and assign roles. Their reviews are credited to the firm, and the firm profile carries the combined record.

Scope stated in the open

Covered and excluded modules are published alongside each audit. No implied coverage, no argument later about what was in scope.

A verified firm identity

Register your firm, links, and specialties. Once an admin verifies the identity, your profile is marked verified wherever it appears.

Credit on the Trust Passport

Your firm is listed under Who audited this on every protocol you review, with the reviewed codebase hash, scope, and a live match indicator against the deployed contract.

See a live investor view