Preparing the live product surface
PrivateDAO is loading wallet-ready controls, Devnet context, and proof-linked routes so the app lands with real content instead of an empty frame.
PrivateDAO is loading wallet-ready controls, Devnet context, and proof-linked routes so the app lands with real content instead of an empty frame.
The live state route is loading proposal cards, treasury status, and execution history.
This route is for checking what happened after a wallet action. Open it when you want to confirm a proposal, inspect treasury posture, or follow execution and logs in one readable place.
Proposal actions stay close to the signer flow instead of hiding behind docs or settings pages.
Execution posture and readiness stay visible beside governance state, not on a disconnected route.
Diagnostics, evidence, and operational signals remain one click away from the governance board.
Execution visibility is stronger when custody evidence is visible before reviewers or buyers inspect the board.
These metrics are shown here so commit, reveal, finalize, and execute stay tied to the live Devnet proof boundary.
7/7 governance proof steps are finalized. 0 proposal is already executed on devnet, 0 proposal is still in commit mode, and 5 proposal is still waiting on settlement evidence.
Open govern flowRuntime evidence 1d old, Devnet canary 6d old, and frontier integrations 5d old remain published together. This is the freshness boundary the user and reviewer see before commit, reveal, finalize, and execute.
Open proof pathPrimary Devnet blockhash latency is 242 ms with no unexpected canary failures.
Open diagnostics5 real-device wallet targets remain pending in the runtime capture set.
Review wallet evidence27 more attempts than successful tracked transactions are currently recorded; adversarial unexpected success count is 0.
Open incident runbookDevnet operation is not isolated from the commercial surface. The same execution evidence that helps reviewers also supports pilot, hosted API, and enterprise governance conversations.
Open engageExecutes the treasury action only after pass state, timelock expiry, and recipient validation succeed.
Dashboard is part of the public product surface. It is responsible for execution visibility, logs, and diagnostics, while repo-only tools remain outside the buyer-facing runtime.
Start with Solflare, Phantom, or Backpack and activate the live governance flow.
Use the guided start workspace to move into the DAO creation rail instead of repo setup.
Stay in the same govern flow and submit the first proposal after the DAO is ready.
Commit voting stays inside the same live wallet-connected govern surface.
Reveal remains a first-class product action rather than a hidden protocol-only step.
Finalize stays explicit in the govern flow so the product matches the real on-chain phase boundary before execution.
Execution only becomes visible when the real readiness boundary says it is ready.
Follow proposals, vote timeline, treasury state, and execution results in the activity view.
Runtime evidence, proof freshness, and operational health stay in the product diagnostics route.
These stay outside the buyer-facing flow. They remain accessible through the repo for maintainers, audits, migrations, incident handling, and deep protocol operations.
Solana Devnet
Create DAO, treasury, policy companions, and migration-safe governance defaults.
Commit-reveal with quorum snapshots, reveal rebate vault, and ZK review overlay when needed.
REFHE and MagicBlock runtime checks gate treasury execution without changing the legacy path.
Execution log, Devnet proof packets, and reviewer bundles update together.
Treasury Committee
Cross-proposal isolation lane C The governance lifecycle is complete enough that the treasury path is ready to execute once the operator reviews the final packet.
This motion is close to execution, so the AI layer focuses on beneficiary clarity, treasury magnitude, and proof visibility.
Treasury conditions are serviceable, and the route should keep operational notes and reviewer links visible.
Gaming DAO
Devnet test: confidential token bonus bound to a real AES-GCM encrypted manifest artifact, REFHE hashes, and MagicBlock private payment route. The governance phase is complete, but settlement evidence still gates the commercial trust surface.
This motion is still active, so the AI layer focuses on signing clarity, treasury context, and the proof surfaces the reviewer should inspect next.
Treasury conditions are serviceable, and the route should keep operational notes and reviewer links visible.
Gaming DAO
End-to-end confidential token payout with REFHE and MagicBlock settlement evidence. The governance phase is complete, but settlement evidence still gates the commercial trust surface.
This motion is still active, so the AI layer focuses on signing clarity, treasury context, and the proof surfaces the reviewer should inspect next.
Treasury conditions are serviceable, and the route should keep operational notes and reviewer links visible.
Enterprise DAO
Execute a confidential payout only after REFHE settlement and strict settlement evidence. The governance phase is complete, but settlement evidence still gates the commercial trust surface.
This motion is still active, so the AI layer focuses on signing clarity, treasury context, and the proof surfaces the reviewer should inspect next.
Treasury conditions are serviceable, and the route should keep operational notes and reviewer links visible.
Enterprise DAO
Confidential token payout with MagicBlock and REFHE settlement The governance phase is complete, but settlement evidence still gates the commercial trust surface.
This motion is still active, so the AI layer focuses on signing clarity, treasury context, and the proof surfaces the reviewer should inspect next.
Treasury conditions are serviceable, and the route should keep operational notes and reviewer links visible.
Enterprise DAO
Confidential token payout with MagicBlock and REFHE settlement The governance phase is complete, but settlement evidence still gates the commercial trust surface.
This motion is still active, so the AI layer focuses on signing clarity, treasury context, and the proof surfaces the reviewer should inspect next.
Treasury conditions are serviceable, and the route should keep operational notes and reviewer links visible.
| Asset rail | Allocation | Value | Policy | Runtime state |
|---|---|---|---|---|
| SOL treasury | 42% | $1.18M | Timelocked execution / onchain treasury PDA | Live |
| Confidential payroll reserve | 23% | $648k | REFHE envelope + execution snapshot | Gated |
| Gaming rewards corridor | 19% | $533k | MagicBlock settlement evidence | Pending evidence |
| Strategic grants | 16% | $451k | Governance V3 + live proof bundle | Live |