Proof of Audits
Proof of Audits
Start
Native lifecycle
Prepare · Pre-audit

Contest for Discovery, Proof for Protection

Make the submitted review boundary testable before auditor time begins.

Pre-audit is the prepare phase of contest → proof: lock the snapshot, map risks and invariants, run quality gates, and hand core auditors a real brief so discovery starts from evidence, not a cold repo.

Price pre-audit reviewers View full native pricing Full lifecycle map
Who performs it
Protocol contributors, Proof of Audits gate tooling, and up to three approved pre-audit reviewers: function, contract, and economic/system.
When it starts
After repository and scope submission, before core-audit recruitment and funding approval.
Pricing basis
10%, 15%, or 20% of coreOne reviewer adds 10% of core, two add 15%, and three add 20%. Every option contains 5% Proof of Audits operations; the reviewer pool receives 5%, 10%, or 15% respectively.

How the work moves

Each step creates or validates evidence needed by the next step. Missing proof stops the handoff.

  1. 01
    Lock the snapshot

    Record the submitted source state and verify that pre-audit tooling does not mutate protocol code.

  2. 02
    Index facts and flows

    Build contract, dependency, call-flow, risk-surface, summary, and evidence records from the scoped repository.

  3. 03
    Prepare invariants

    Link English reasoning, exact source evidence, tests, formal status, monitorability, and admin-action state.

  4. 04
    Run the gates

    Compilation, quality, source-integrity, final merge, and release gates decide whether the core brief can be released.

What the protocol receives

Compact output records first. Methodology detail remains one click away.

Evidence areaOutputWhat it means
Facts and graphRepository evidence index

Contracts, dependencies, functions, flows, summaries, and source-bounded facts.

Invariant registryTestable protocol properties

English why, stateless/stateful links, compile and quality state, formal status, and monitorability.

Reviewer workFunction, contract, system

Three separate review roles check different preparation surfaces before core audit.

Formal preparationHalmos checks and Certora-ready stubs

The pipeline can prepare starting artifacts. A live Certora run still needs approved access and execution scope.

Core handoffcore_audit_brief.md

The approved scope, risks, invariants, blockers, and evidence trail handed to core auditors.

Failure stateAdmin action required

Missing evidence or failed gates stop release and identify the exact action needed.

What blocks completion

  • Source snapshot changes during analysis
  • Repository cannot compile in the isolated workspace
  • Loaded protocol patterns remain unresolved
  • Invariant evidence or quality fields are incomplete
  • Release gate does not pass
Repository-backed sources

Inspect the rules behind this page.

Public copy summarizes current implementation and skill contracts. It does not replace repository evidence or approval.

Put pre-audit into the funding plan.

Build the lifecycle cart, then submit repository identity so the approved quote can replace every public estimate.

Price pre-audit reviewers