Skip to content

Latest commit

 

History

History
122 lines (70 loc) · 7.04 KB

File metadata and controls

122 lines (70 loc) · 7.04 KB

PrivateDAO Excellence Closure Matrix - 2026-05-06

PrivateDAO is not treating launch gaps as hidden caveats. Every serious gate is converted into a visible operating lane with a product route, evidence schema, verification command, and reviewer-readable boundary.

The result is a stronger product posture: users see what works now, operators know exactly what to close next, and reviewers can distinguish live Testnet execution from mainnet-real-funds gates without reading terminal logs.

Closed Product Surface

  • Anchor program: Anchor 1.0.1 Testnet program and IDL posture are documented, with web and Android constants aligned to EP9xE8MJZ6FfyEwLqns6HDdUZBknEa7WGYs1Jzsecuva.
  • Governance OS narrative: the public product now leads with Private. Verified. Informed.: ZK + commit/reveal privacy, REFHE confidential execution, MagicBlock speed, and GoldRush/QVAC intelligence.
  • QVAC intelligence: the QVAC route uses qvac/fabric-llm-finetune through a browser-local inference path for proposal briefs, risk notes, privacy mode, and counterparty context.
  • theMiracle growth track: the wallet-placement benefit design is published as a public route and paste-ready submission packet.
  • Product routes: Payroll, Gaming, Compliance, Developers, RPC Services, Command Center, Custody, Android, and service lanes are visible from the public sitemap.
  • Proof and review: reviewer routes expose proof matrix, runtime packets, Testnet lifecycle rehearsal, and explicit custody/mainnet boundaries.
  • Supabase/Eitherway posture: receipt timeline surfaces are wired as first-class product evidence lanes instead of a hidden backend dependency.

No-Gap Operating Design

Custody and multisig

Current truth: mainnet custody ceremony is not claimed until real multisig addresses, signer roster, authority-transfer signatures, and readouts are recorded.

Productized closure: /custody/ turns the ceremony into a strict intake packet and reviewer matrix.

Evidence route: /custody/, /documents/canonical-custody-proof/, and docs/custody-evidence-intake.template.json.

Next operator action: create the Squads or equivalent multisig, populate the intake, then run npm run apply:custody-evidence-intake.

Real-device wallets

Current truth: real-device evidence must come from signed wallet flows; it is never synthesized.

Productized closure: wallet coverage is tracked as a capture program with templates for Phantom, Solflare, Backpack, Glow, and Android.

Evidence route: /documents/real-device-runtime/ and docs/real-device-runtime-templates/.

Next operator action: record each wallet flow with explorer signatures and import with npm run record:real-device-runtime -- <capture.json>.

Umbra and Cloak

Current truth: relayer health and private-settlement intent are live evidence. Full claim submission requires SDK-generated ZK proof data and UTXO slot data.

Productized closure: settlement lanes expose intent creation, relayer checks, receipt capture, and the exact proof boundary.

Evidence route: /services/umbra-confidential-payout/, /services/cloak-private-settlement/, and /documents/umbra-devnet-relayer-receipt-2026-05-06/.

Next operator action: run a real SDK claim only when valid UTXO slot data and proof account data are available; attach returned signatures to the receipt packet.

AWS read node

Current truth: api.privatedao.org is the hosted read-node lane; root product remains static for resilience.

Productized closure: backend health, relayer, QVAC, GoldRush, Torque, and Zerion checks are surfaced as service evidence.

Evidence route: /rpc-services/, /documents/reviewer-fast-path-2026-05-06/, and docs/read-node/.

Next operator action: keep the hosted read-node environment aligned with the current Testnet program ID and verify /healthz plus /api/v1 after each cutover.

Jupiter quote path

Current truth: Jupiter routing is a no-key API lane and must show concrete input/output values when the quote parameters are valid.

Productized closure: treasury route pages keep quote review user-facing instead of hiding it in scripts.

Evidence route: /services/jupiter-treasury-route/, /documents/jupiter-treasury-route/, and DX-REPORT-JUPITER.md.

Next operator action: use canonical SOL and USDC mints, integer lamports, and a bounded slippage value before presenting the quote.

GoldRush intelligence

Current truth: GoldRush value depends on a configured environment key and a valid wallet query.

Productized closure: Intelligence is placed before signing so users understand treasury health and counterparty risk before committing.

Evidence route: /intelligence/ and /treasury/.

Next operator action: keep the API key server-side or environment-backed and show graceful degraded explanations when the key is absent.

QVAC local AI

Current truth: native QVAC SDK packages are installed, while browser execution uses the QVAC Hugging Face model path that works in static web delivery.

Productized closure: the product treats QVAC as sovereign pre-sign intelligence, not as a decorative chatbot.

Evidence route: /services/qvac-sovereign-ai/, /assistant/, and /intelligence/.

Next operator action: preserve zero-cloud behavior for sensitive proposal briefs and document any future native runtime expansion separately.

Mainnet release

Current truth: PrivateDAO is Testnet-live, not mainnet-real-funds-live.

Productized closure: mainnet is a disciplined release gate: audit, custody, monitoring, and cutover readouts must close before public real-funds claims.

Evidence route: /documents/mainnet-blockers/, /documents/mainnet-readiness/, and /trust/.

Next operator action: close the ceremony, external review, monitoring destinations, and final cutover packet before changing release language.

Why This Is Stronger Than Hiding Gaps

PrivateDAO's users are not asked to trust a black box. They can operate from the interface, learn the concepts in plain language, and verify the evidence route for each critical layer.

This is the product advantage:

  • Private operations are guided through UI flows instead of scripts.
  • Verification is attached to every major action instead of buried in a spreadsheet.
  • Intelligence runs before signing so governance decisions are informed, not blind.
  • External gates become exact operating lanes with schemas, routes, and commands.
  • Mainnet language stays conservative until the custody and audit facts exist.

The project can therefore improve aggressively without overclaiming. Each remaining blocker has a conversion path into evidence, and each evidence path is already represented in the product surface.

Reviewer Fast Path

  1. Product home: https://privatedao.org/
  2. Governance: https://privatedao.org/govern/
  3. Intelligence: https://privatedao.org/intelligence/
  4. QVAC local AI: https://privatedao.org/services/qvac-sovereign-ai/
  5. Private settlement: https://privatedao.org/services/cloak-private-settlement/
  6. Proof matrix: https://privatedao.org/proof/?judge=1
  7. Custody lane: https://privatedao.org/custody/
  8. theMiracle benefit: https://privatedao.org/documents/themiracle-benefit-proposal/