Mainnet Cryptographic Readiness Ladder - 2026-05-25

PrivateDAO is a Solana Testnet production-candidate system. This ladder is the cutover map from the current Testnet cryptographic system to a mainnet-ready launch posture. It does not claim mainnet real-funds release. It shows the exact rails that already exist, the public proof attached to them, and the remaining gates that must close before mainnet funds or customer payroll can be enabled.

Current operating scope:

• Cluster: Solana Testnet
• Anchor program version: 1.0.1
• Current program ID: EP9xE8MJZ6FfyEwLqns6HDdUZBknEa7WGYs1Jzsecuva
• ProgramData: FKyt5DcmRQcCF8kzMGjCvfGb3ZPHMQnH1SqiG9Mi8xEc
• Squads vault authority: CALHrBqx6jbzcPn2NVcinqSAHeod65v9LcDuTxsdPqBv
• Current binary proposal: Squads proposal index 3
• Current timelock release: 2026-05-27T02:25:39Z

What This Changes

The old readiness question was "do not overstate operational truth." That is still enforced. The new engineering question is stronger: every cryptographic claim must have a path to production-grade operation. For each rail below, PrivateDAO tracks four layers:

1. Core instruction or backend route
2. Testnet proof or repository artifact
3. User-facing route
4. Mainnet cutover gate

The same ladder is exposed as backend-readable JSON at:

• https://api.privatedao.org/api/v1/cryptographic-readiness

That endpoint is intentionally secret-free. It lets reviewers, operators, and future monitoring jobs inspect the live rail map without scraping the website.

Ladder

Mainnet Cutover Sequence

1. Execute Squads proposal index 3 after 2026-05-27T02:25:39Z.
2. Record DAO authority handoff signature and account readout.
3. Record treasury-operator authority handoff signature and account readout.
4. Run the integrated ZK proposal flow and record verifier-program boundary evidence.
5. Repeat REFHE + MagicBlock settlement with production endpoint policy and monitoring owners.
6. Close Umbra claim proof account data and Ika funded dWallet proof only when those artifacts exist.
7. Enable production RPC and stream alert delivery with transcript evidence.
8. Freeze a release candidate, run npm run verify:all, npm run check:mainnet, and publish the mainnet proof package.

Verification Commands

npm run verify:mainnet-cryptographic-readiness
npm run verify:cryptographic-onchain-matrix
npm run verify:frontier-track-closure
npm run verify:mainnet-proof-package
npm run check:mainnet

Public Language Boundary

Safe public wording:

• "PrivateDAO is a Solana Testnet production-candidate for private governance, encrypted payroll, confidential payouts, and wallet-first operations."
• "REFHE and MagicBlock settlement gates have finalized Testnet receipts."
• "ZK has local proof discipline plus a standalone Solana Testnet verifier receipt; integrated governance execution is staged behind Squads timelock."
• "Ika and Umbra lanes are productized with explicit proof boundaries; final dWallet signing and full claim settlement are not claimed until recorded."

Forbidden until recorded:

• "Mainnet funds are live."
• "Final Ika 2PC-MPC signing is complete."
• "Umbra full claim settlement is complete."
• "External audit is complete."
• "Monitoring is production-delivering incidents to named owners" unless delivery evidence is attached.

Reviewer Shortcut

Open these in order:

1. /documents/mainnet-cryptographic-readiness-ladder-2026-05-25
2. https://api.privatedao.org/api/v1/cryptographic-readiness
3. /documents/cryptographic-onchain-matrix-2026-05-25
4. /judge
5. /security
6. /services/encrypt-ika-operations
7. /services/magicblock-private-payments

The intended reading is simple: PrivateDAO has real Testnet encrypted execution, real custody controls, real proof surfaces, and a precise cutover ladder to mainnet without overstating unfinished external rails.