Quick route navigation
Choose the right corridor, connect a wallet, and move through a guided governance flow without losing the proof, trust, and operational depth behind the product.
The shortest startup-grade truth layer before the user opens anything else
The core governance, wallet, and devnet posture stays unmistakably Solana-native.
Wallet-first live-dApp UX is surfaced directly in the product shell and command flows.
Capital-governance and treasury-discipline positioning stays strong for partner-facing tracks.
Fast RPC, diagnostics, and hosted-read posture remain visible as real product value.
Privacy track strength stays tied to responsive settlement corridors and proof-backed execution.
Next.js architecture, reusable UI, and shipping discipline remain obvious to developer judges.
What stays inside the product
The public UI is for wallet connection, DAO creation, proposal flow, voting, execution, logs, and diagnostics. Debugging, migrations, batch operations, and recovery stay in the engineering layer.
Shared product session
Start with the exact user journey
The first-run product path should make the eight real operations obvious and keep everything else out of sight until engineering truly needs it.
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.
Open the command center and stage governance actions from the product shell.
Commit voting stays inside the live wallet-connected governance surface.
Reveal remains a first-class product action rather than a hidden protocol-only step.
Finalize stays explicit in the UI so the product matches the real on-chain phase boundary before execution.
Execution only becomes visible when the proof and readiness boundary says it is ready.
Execution logs, vote timeline, and treasury state belong inside the operating dashboard.
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.
Start with the corridor that matches your team, then connect a wallet and move straight into governance.
This workspace removes the need to understand every proof packet up front. It gives a direct path into the right service rail, the right wallet, and the right command surface for the team using PrivateDAO.
Choose the service corridor, connect a wallet, and follow the shortest path to a real governance action.
Start with one hosted overview reel when a normal user or judge needs instant orientation.
Create, vote, reveal, and execute in one operational rail without dropping into raw docs.
Choose your PrivateDAO corridor
Private committee decisions and public treasury accountability
ZK-heavy review rails for sensitive capital allocation
Reward distribution and token-native operations with corridor evidence
Payroll, bonus, and operator trust packaging for real teams
Recommended wallet path
Best first-run choice for live dApp demos, consumer UX, and partner-facing wallet tracks.
Fastest path for mainstream Solana users who want familiar wallet behavior on devnet.
Best for users who want a more advanced signer posture without leaving the product shell.
What the first successful session looks like
Start from grant, fund, gaming, or enterprise rails so the app can bias the governance and treasury experience correctly.
Bootstrap the DAO, treasury, governance settings, and wallet-connected runtime surfaces from one product shell.
Proposal cards keep privacy boundary, treasury path, service fit, and hardening expectations visible before a vote begins.
Commit, reveal, evidence gates, and treasury execution remain connected to proof packets and runtime diagnostics.
Start-path readiness
First-run users should see whether wallet, proposal, and proof surfaces are healthy before entering deeper governance steps.
4/5 wallets are review-ready and 5/5 expose diagnostics. Pending real-device targets remain visible in runtime evidence. Primary wallet runtime should stay visible before every sign request.
Open wallet diagnostics7/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 command centerPrimary 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 engage