Wallet-first
Testnet
User-first flow
Govern
Run private on-chain governance from the browser

This is the core product path. Connect a Solana Testnet wallet, create or review a DAO, prepare a proposal, commit, reveal, execute treasury intent, inspect PDAO governance-token context, and verify the result without terminal work or developer-only steps.

ConnectReviewSignVerify
Wallet-orchestrated UXReview first · Sign second · Verify third
Connect
Choose wallet, confirm account, and stay on Solana Testnet.
Review
Read the action, policy, risk, privacy mode, and execution lane first.
Sign
Approve the exact wallet request only after the operation is clear.
Verify
Open the receipt, explorer hash, and proof continuity from the same flow.
PrivateDAO Stack

Most DAOs expose everything. Votes. Payroll. Treasury activity. Internal operations.

We think that is broken. PrivateDAO enables organizations to operate privately while remaining cryptographically verifiable on Solana. Each layer below has a live route, a proof route, and when available a one-click API exercise.

route proof

1. Private Governance

Confidential decisions for Solana-native organizations.

Create or review DAO state, prepare proposals, commit/reveal private votes, inspect PDAO context, then verify the Testnet action.

SolanaAnchorcommit-revealZK proof anchorsreviewer proofs
one-click API

2. Encrypted Treasury Coordination

Private budget and execution coordination before funds move.

Review treasury risk, preview Jupiter routing, keep encrypted payment metadata bounded, and route approved actions to proof.

JupiterstablecoinsSquads-style authorityencrypted metadataread-node telemetry
TryVerify
one-click API

3. Private Payments

Confidential payouts from organizations to contributors, operators, and task executors.

Generate a private settlement intent, preserve a receipt reference, and route the visitor to the matching proof lane.

CloakUmbraIkaencrypted receiptsSolana memo/hash anchoring
TryVerify
route proof

4. Confidential Payroll

Payroll integrity without exposing every contributor detail.

Use REFHE payroll proof, encrypted manifests, stablecoin payout context, and proof continuity for auditor-safe payroll review.

REFHEencrypted metadatastablecoin payoutsproof receiptsselective disclosure
route proof

5. Intelligence Layer

Decision support before governance or treasury authorization.

Summarize proposals, score risk, inspect wallet and treasury context, and detect abnormal governance or payment posture before signing.

QVACGoldRushCovalentZerionQuickNodeSupabase receipts
one-click API

6. Agent / MCP Layer

Execution lineage for intent -> approval -> execution -> outcome.

Forward an approved operational event to the agent/growth rail while keeping the approval and outcome tied to verifiable receipts.

Torque MCPMagicBlock skillscustom MCP toolsexecution lineageread-node APIs
TryVerify
Governance runtime

This route keeps the full DAO lifecycle in one wallet-first surface instead of scattering it across separate tools

Govern is where a normal user proves the product is real. Create the DAO, submit the proposal, commit the vote, reveal it, finalize, and execute from one route. Then open live state, proof, or security only when you want to inspect what the blockchain and the cryptographic rails just recorded.

Create and execute from one route with the same connected wallet.
Use proof and security after the action, not before the first click.
Treat the chain hash and logs as the final explanation layer for the user and the reviewer.
Visitor fast pathClick → Sign → Verify
Need test funds?
Use the official Solana faucet to fund your connected Testnet wallet before creating a DAO, voting, or executing a proposal.
Policy Control Room

Proposal packs produce machine-readable operating policy

Select a pack, inspect the policy contract, then run create proposal from the same govern shell. This keeps approval logic, execution rail, audit scope, and proof requirement aligned before any signing step.

Machine-readable policy
{
  "pack": "payroll-pack",
  "operationType": "payroll",
  "spendingScope": "proposal-bound",
  "assetScope": "PUSD",
  "executionRail": "cloak",
  "proofScope": "enhanced",
  "auditScope": "auditor",
  "incentiveScope": "operator_retention",
  "requiresPrivateSettlement": true,
  "requiresIntelligenceGate": true,
  "generatedAt": "2026-05-30T16:58:53.720Z"
}
Apply pack now
1. Keep `DAO` and `proposal` in the same signer lane.
2. Route through `Intelligence` before execution if required.
3. Execute from `Execute` with selected asset and rail.
4. Validate receipts from `Proof` and `Judge` mode.
Normal user pathBrowser only

The product flow is meant to be clicked, signed, executed, and verified by a normal visitor

This route turns the technical stack into a simple operating loop: connect a Testnet wallet, review the decision, sign the exact action, then verify the hash and proof continuity from the same product shell.

Operating map

Governance is the first executable lane in the PrivateDAO Stack

Every other corridor exists to make organizational governance useful: intelligence explains the decision before authorization, treasury routes turn approved policy into action, encrypted payments and payroll protect sensitive intent, GamingDAO rewards use the same primitives, and proof lets the visitor verify what happened on Testnet.

How intelligence feeds every lane
Governance receives proposal review, risk framing, and policy context before a signer approves.
Payments receive counterparty review, settlement lane selection, and private rail clarity before funds move.
Payroll receives encrypted operational preparation so payout metadata stays out of shared review surfaces.
Treasury receives wallet history, stablecoin visibility, and route comparison before rebalance or disbursement.
Wallet-first flows receive simpler user context so normal operators can act safely without losing technical truth.
Governance runtime

Every governance action stays attached to the chain evidence

Create DAO, proposal, commit, reveal, finalize, and execute all sit on the same Testnet execution spine so the UI, review gate, signer, program, and proof packet remain aligned.

Wallet-first governance controls are mounted in the browser for safe signing. The page content above is already reviewable while the wallet adapter hydrates.