Treasury | PrivateDAO

This route centralizes treasury posture: asset allocation, risk interpretation, read-node health, and AI-assisted proposal context for safer execution.

Open govern Open execute Open curated docs

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.

Start flow Proof hub Matrix JSON

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

Try Verify

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

Try Verify

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

Try Verify

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

Try Verify

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

Try Verify

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

Try Verify

Treasury explainer

Treasury work should be private before execution and verifiable after it.

The treasury route explains budget risk, route quality, stablecoin movement, and governed execution before a signer approves anything from the wallet.

Pain

Public wallets expose strategy before action

Path

Review risk -> Select route -> Execute -> Audit

Rails

Jupiter, PUSD, read-node proof, Testnet receipts

Start from treasury context, then continue to execution only after reviewing risk and route quality.

Open intelligence Open treasury route Open proof

Treasury table

Asset rail	Allocation	Value	Policy	Runtime state
SOL treasury	0.02 SOL	Testnet rehearsal funded	Timelocked execution / onchain treasury PDA · display uses Testnet evidence, not USD AUM	Live
Confidential payroll reserve	USDC/PUSD/AUDD	Intent receipts ready	Umbra/Cloak intent receipts + scoped viewing-key audit posture	Testnet-ready lane
Gaming rewards corridor	Proposal-bound	Governed payout route	MagicBlock settlement evidence with proposal-bound distribution review	Routed
Strategic grants	16%	$451k	Governance V3 + live proof bundle	Live

Treasury Review AI

Treasury execution review

Route notes attached

Treasury conditions are serviceable, and the route should keep operational notes and reviewer links visible.

Treasury destination

Execution target pending index evidence

Baseline motion

Pending exact baseline in current evidence packet

Current motion

Pending exact amount from the indexed proposal record

Execution target

Execution target remains governed by the indexed proposal account and current DAO phase.

Recipient has limited treasury history, so destination context should stay visible before execution.

Execution delay is compact, so timing and signer context should stay explicit through execution.

Treasury magnitude is not yet present in the structured proposal payload, so payout risk should stay conservative.

Recipient disclosure is not yet present, so beneficiary validation cannot be completed from the current packet alone.

Backend-indexed proposal record: Confidential payroll batch / April (Executable). Structured execution context reads timelock-hours, execution-target directly instead of inferring them from card prose.

Read-node activation

Hosted-read activation

Buyer-facing infrastructure value starts here: indexed governance reads, reviewer telemetry, and the exact backend deployment target stay in one commercial path instead of being split across docs and GitHub blobs.

Activation state

Indexed reads and same-domain backend serving are live for Testnet reviewer checks

Public product routes consume indexed read evidence and the hosted `api.privatedao.org` lane now serves health, relayer, QVAC, Covalent GoldRush, Torque, Zerion, and SNS checks.

Read path

backend-indexer

Indexed coverage

20 proposals / 19 DAOs

Confidential

3 confidential payouts

Operator checks

6 operator checks

Integration coverage

2/3 REFHE settled · 1/2 MagicBlock settled

Open buyer infrastructure route Open telemetry packet Open read-node snapshot Open read-node ops Open deploy target Open cutover packet

Host readiness

Hosted-read host readiness

Show buyers the real deployment lane: target host, public proof endpoints, route binding, and the static fallback policy stay visible from the commercial surface.

Readiness state

Host-ready lane defined; same-domain public serving is in final security hardening before release cutover

Use https://api.privatedao.org/api/v1 as the live read-node boundary. Same-domain `/api/v1` on the static frontend remains a future reverse-proxy consolidation step, not the current production-candidate API host.

Deploy target

https://privatedao.org/ → https://api.privatedao.org/api/v1

Health

https://api.privatedao.org/healthz

Metrics

https://api.privatedao.org/api/v1/metrics

Public checks

6 public checks

Indexed proof

17 proposals / 16 DAOs

Settlement proof

3 confidential payouts · 2 REFHE settled · 1 MagicBlock settled

Telemetry freshness

2026-05-26T03:09:35.774Z

Route binding

Serve read-node traffic from `https://api.privatedao.org/api/v1` until a same-domain reverse proxy is intentionally cut over.

UI fallback policy

If the API host is unreachable, keep read-node evidence available through in-app packets and snapshots.

Open cutover packet Open deploy guide Open runtime snapshot Open telemetry packet

Analyst-grade data corridor

Export-ready summaries and hosted-read proof for reviewer-grade telemetry

Telemetry posture

Runtime evidence, diagnostics, and analytics now behave like one reviewer-safe telemetry corridor rather than three disconnected surfaces.

Hosted-read proof

Core integrations, read-node snapshot, and services packaging keep hosted reads visible as buyer and reviewer value.

Operational trust

Launch trust, custody truth, and runtime evidence remain close enough that data reviewers can inspect proof without leaving the product shell.

Export-ready route

The telemetry export packet now gives a compact path into diagnostics, analytics, runtime evidence, and the hosted-read proof chain.

Open telemetry export packet Open telemetry packet Open read-node snapshot Open diagnostics Open read-node ops Open integrations