Skip to content

MAINNET_READINESS.md

Latest commit

 

History

History
57 lines (42 loc) · 3.59 KB

MAINNET_READINESS.md

File metadata and controls

57 lines (42 loc) · 3.59 KB
Raw

Mainnet Readiness Gate

Dark Null must not be launched on mainnet until deployment and audit evidence are published. This page defines the release gate that must pass before mainnet language or deployment claims are allowed.

Run:

npm run check:mainnet
npm run check:mainnet:evidence
npm run check:mainnet:beta
npm run check:claims

Those commands are expected to fail until every blocker below is cleared.

Required Evidence

Gate Required evidence
Rust validation cargo test --offline passes on the release commit
Payout-bound proof v2 circuit, zkey, wasm, vk, Rust verifier, IDL, manifest, SDK, and tests all bind [commitment, nullifier, root, amount, receiver_token_part_0, receiver_token_part_1, mint_part_0, mint_part_1]
Trusted setup final public ceremony transcript or explicit third-party audit acceptance of the setup path, with report path and SHA-256 hash in MAINNET_EVIDENCE.json
Public payout v2 proof verifies amount, receiver token account, and mint before transfer; legacy proof-unbound path stays closed
Mainnet manifest mainnet program id, deployment transaction, artifact hashes, cluster, and upgrade-authority policy are published
Mainnet evidence MAINNET_EVIDENCE.json binds the audited commit, program id, deployment transaction, upgrade policy, v2 artifact label, payout enablement, and audit report hash
Third-party audit external audit report with scope, commit hash, findings, fixes, residual risk, and auditor identity
Runtime security strict npm audit is clean for runtime and dev dependencies
Release integrity checksums, SBOM, and GitHub artifact attestations produced for release artifacts
Public claims docs/CLAIMS_LEDGER.md reflects delivered, blocked, and roadmap claims, and npm run check:claims passes
Operations relayer/direct fallback, rate limits, health checks, key custody, pause/upgrade policy, and incident response are documented
End-to-end flow deposit, root update, proof generation, v2 withdraw, replay rejection, malformed proof rejection, and packaging all pass together

Open Beta Lane

An unaudited mainnet beta is a separate evidence lane, not a production release shortcut. It uses MAINNET_BETA_EVIDENCE.example.json, MAINNET_OPEN_BETA.md, and npm run check:mainnet:beta.

The production gate above remains blocked until the production evidence exists.

Architecture Ideas Worth Evaluating

The strongest adjacent ideas to evaluate before mainnet are:

  • split claim and withdraw so the proof-bearing transaction does not move value if future audits prefer delayed payout
  • use credit-note style commitments for delayed payout
  • add preimage-verified revoke or recovery only if the privacy tradeoff is explicit
  • increase root-history usability or publish snapshot-staleness warnings
  • test wrong recipient, fake note, wrong opening, wrong public payout input, replay, stale root, and malformed proof paths as first-class regression cases
  • make relayer trust boundaries explicit: censorship only, direct fallback always available

These are design directions, not current Dark Null claims.

Promotion Files