Mainnet Proof Package

mainnet-proof-package.generated.md

Boundary

This route preserves legacy markdown access inside the Next.js surface. The raw repository file remains authoritative.

Open raw file

Mainnet Proof Package

Overview

project: PrivateDAO
generated at: 2026-05-26T03:10:16.035Z
package decision: repository-strong-but-external-blockers-remain
program id: EP9xE8MJZ6FfyEwLqns6HDdUZBknEa7WGYs1Jzsecuva
verification wallet: 4Mm5YTRbJuyA8NcWM85wTnx6ZQMXNph2DSnzCCKLhsMD
accepted in repo: 9
pending external: 3
not in repo: 1

Core Artifacts

docs/mainnet-readiness.generated.md
docs/mainnet-acceptance-matrix.generated.md
docs/test-wallet-live-proof-v3.generated.md
docs/governance-hardening-v3.md
docs/settlement-hardening-v3.md
docs/release-ceremony-attestation.generated.md
docs/release-drill.generated.md
docs/operational-evidence.generated.md
docs/runtime-evidence.generated.md
docs/runtime/real-device.generated.md
docs/deployment-attestation.generated.json
docs/go-live-attestation.generated.json
docs/external-readiness-intake.md

Canonical Commands

npm run build:mainnet-readiness-report
npm run build:mainnet-acceptance-matrix
npm run build:mainnet-proof-package
npm run verify:mainnet-readiness-report
npm run verify:mainnet-acceptance-matrix
npm run verify:mainnet-proof-package
npm run verify:all
bash scripts/check-mainnet-readiness.sh

Purpose

This package is the shortest reviewer-facing path for mainnet readiness discussions. It binds the readiness report, acceptance matrix, baseline and additive V3 proof surfaces, runtime package, release discipline, and honest external-intake boundary into one compact surface.