Question 1

What is Proof of Audits?

Accepted Answer

Proof of Audits is a proof-based Web3 auditing and protocol trust platform. It turns audits, live bytecode (deployed-code) checks, authority evidence, and VTI scores into a Trust Passport that shows what was reviewed, what still matches on-chain, who can change the system, and what gaps remain — not a safety guarantee or certificate that a protocol is unhackable.

Question 2

What is Web3 auditing?

Accepted Answer

Web3 auditing is security review of smart contracts and protocols — finding logic bugs, access-control flaws, and economic risks before and after launch. Proof of Audits adds live code match and Trust Passports so audit evidence stays useful after the PDF is written.

Question 3

What is a Trust Passport?

Accepted Answer

A Trust Passport is a live, inspectable proof page for a protocol. It packages reviewed scope, deployed-code match status, authority and control evidence, audit history, and open gaps into one record investors, users, and wallets can check before relying on the protocol.

Question 4

How is Proof of Audits different from a traditional smart contract audit?

Accepted Answer

A traditional audit is usually a point-in-time report (often a PDF). Proof of Audits keeps evidence current by linking audits to commits, checking whether live bytecode still matches, mapping who holds upgrade/pause/oracle power, and publishing gaps when proof is missing or stale.

Question 5

What is deployed-code match or bytecode verification?

Accepted Answer

Deployed-code match verifies that the contract users interact with on-chain still matches the audited source or commit. Proxy upgrades, new implementations, and redeployments can make old audit reports irrelevant; Proof of Audits flags match, partial match, or drift instead of treating a logo as current proof.

Question 6

What is a pre-audit in Proof of Audits?

Accepted Answer

A pre-audit is structured readiness work before a core contest or firm engagement: locking a source snapshot, mapping complexity and invariants, producing review bundles, and recording evidence gaps so teams spend audit budget on cleaner, better-scoped work.

Question 7

How is this different from a bug bounty?

Accepted Answer

Bug bounties optimize for open-ended volume of reports after or during production. Proof of Audits optimizes for segmented review, validation chains, deployed-code proof, and measurable coverage of the audit lifecycle — complementary to bounties, not a replacement for continuous disclosure programs.

Question 8

Does Proof of Audits replace Sherlock, Code4rena, or Cantina?

Accepted Answer

No. Proof of Audits sits before and after contest/firm work: cleaner scope and readiness going in, fix verification and deployed-code match coming out, plus a public Trust Passport so markets can inspect evidence instead of only audit logos.

Question 9

How are auditors matched to protocols?

Accepted Answer

Auditors are routed by skill tags, public contest/history evidence, reputation signals, tier eligibility, protocol category, and conflict-of-interest checks. The goal is specialist coverage of the actual risk surface rather than random assignment by brand name alone.

Question 10

Is Proof of Audits a security guarantee?

Accepted Answer

No. Proof of Audits shows evidence, gaps, and risk signals. It does not certify that code is safe, that exploits are impossible, or that past reviews still apply after unreviewed upgrades. Users and investors still decide; the product makes the proof trail inspectable.

Question 11

Is pricing public?

Accepted Answer

The commercial model is public. Ten qualified founding protocols can receive one sponsored first deployed baseline. Every later upgrade, redeployment, new version, or material production change receives one complete scope and one fixed quote. Code matching, mismatch investigation, coverage work, authority review, and exit verification are included when the accepted scope requires them; they are not separate products. ITS results never set the price. Machine-readable details: /pricing.md and /deployed/pricing.

Question 12

Can already-deployed protocols use Proof of Audits?

Accepted Answer

Yes. Live protocols submit contract addresses, audit reports, source/GitHub links, known changes, and protection evidence for a private External Deployed ITS v2 /900 review. Results stay private until the owner approves Trust Passport publication.

Question 13

What does the wallet or browser extension show?

Accepted Answer

The extension surface is designed to show trust status at signing time: deployed-code match, known auditors, missing proof, mismatch, or high-risk labels linked to the public passport — so users see evidence before approving a transaction, not only after a loss.

Contest.Then proof.

Contest for discovery. Living proof for protection.

Contest phase

Proof transformation

Pre to passport.One living trail.

Pre-audit

Core cascade · T4 → T0

Protocols / founders

Auditors

Investors & users

Start with proof that lasts