Proof of Audits

Learn How Proof
Actually Works

76 short explainers, grouped by the exact ideas behind the platform — from why static audit PDFs fail, to live bytecode matching, auditor tiers, fix verification, and wallet-time trust. Pick a topic and watch.

Open full playlist
The problem

Why Static Audits Fail

A signed PDF is not proof. These explainers show why a static audit report drifts away from the code people actually touch — and why a logo is not evidence.

Current-code proof

Live Code & Deployment Match

How Proof of Audits binds an audit to a commit, matches deployed bytecode against the reviewed source, and catches proxy drift, silent upgrades, and code that no longer matches its report.

Locking the scope

Pre-Audit: Baseline & Invariants

Before a review starts, the source snapshot is locked and expected rules are recorded. These videos cover baseline locking, invariant registries, and chain-of-custody intake.

Who reviews the code

Auditor Tiers, Scoring & Matching

The reputation engine behind the score: tiered reviewers (T0–T4), reviewer scoring, evidence-based matching, and why auditor reputation is kept separate from protocol trust.

After the findings

Post-Audit: Fix Verification

A finding is not fixed until it is retested. These explainers cover fix verification, regression risk, replay evidence, retest scope, and the appeals process.

At the moment you sign

Wallet-Time Trust & Authority

The signal where it matters — in your wallet, before you sign. Function-action trust, wallet-time evidence, and mapping the control keys that can undo an audit.