Live Activity
Treasury + proposals
Live Testnet state
Activity view

Review proposals, treasury state, and execution results without leaving the product.

This route is for checking what happened after a real wallet action. Open it after you connect a Testnet wallet, create a DAO, submit a proposal, vote, or execute so you can confirm the result and inspect the runtime trail in one readable place.

How to verify the product here

Wallet-first actions

Proposal actions stay close to the signer flow instead of hiding behind docs or settings pages.

Proof-aware execution

Execution posture and readiness stay visible beside governance state, not on a disconnected route.

Runtime visibility

Diagnostics, evidence, and operational signals remain one click away from the governance board.

Connect a Testnet wallet, run the govern flow, then come back here after each action. This is the fastest way to verify that the privacy rails, cryptographic flow, and runtime speed are working inside one real product cycle.
Payments truth

Payments truth strip

Surface treasury readiness to reviewers and operators directly from the dashboard so payments proof does not depend on a separate documents-first reading path.
Payments readiness
Testnet rails live, production treasury still evidence-gated
Treasury network
Solana Testnet
Public rails
3 public rails
Payments fit
strong
Exact blocker
upgrade-authority-multisig · external ceremony gate
Move production upgrade authority and operational authorities to a documented multisig or governance-owned path and rehearse rotation.
9 ceremony evidence gates
Live infrastructure state

Supabase, Eitherway, and Amazon are connected as separate runtime layers

The static site stays on GitHub Pages, Supabase stores browser-direct operation receipts, Eitherway previews the wallet-first dApp shell, and Amazon EC2 serves the read-node API at api.privatedao.org. Direct Solana Testnet RPC remains the primary chain path so a failing AWS RPC proxy cannot block the product.

PDAO token strategy
Solana Testnet
Token-2022
Mint authority disabled

PDAO token strategy for live governance operations

Keep the token story operational: PDAO governs participation, proposal discipline, and treasury accountability inside the live dashboard instead of reading like detached tokenomics.
Live token truth
Mint
DFYvBdivHCe4bSErgCiKm2RhwGEcZYbBPFQzLNr37Bie
Initial supply
1,000,000 PDAO
Exact boundary
PDAO is preserved Testnet governance-token evidence attached to the current PrivateDAO Testnet path. It is not presented as a public mainnet payment coin or speculative market token.
What PDAO does now
Governance participation
PDAO is the live Token-2022 governance mint for the canonical reviewer-facing Testnet path and anchors proposal participation and voting.
Proposal discipline
It exists as the participation layer behind proposal lifecycle responsibility instead of leaving proposal access completely open-ended.
Treasury accountability
Treasury motions stay tied to a governed participation surface rather than informal wallet choreography or off-chain chat decisions.
Reviewer-visible identity
The token surface, mint attestation, metadata, and disabled mint authority are already reviewer-visible and bound to the proof package.
What it gates
Voting rights
PDAO gates who participates in the proposal lifecycle today, especially voting and reviewer-facing governance flows.
Proposal access
The token strategy supports proposal access and anti-spam governance posture without claiming a new protocol interface beyond the documented token-gated surface.
Treasury action classes
It governs who can shape treasury-sensitive motions such as top-ups, vendor payouts, contributor flows, and confidential payout proposals.
Community membership
PDAO already reads naturally as a membership and governance identity layer for recurring operator and community actions.
What remains future-facing
Gaming governance
Reward policies, clan treasury motions, sponsorship budgets, and tournament allocations are the most natural next gaming-facing uses.
API and operator permissions
Hosted reads, diagnostics, and API-oriented governance services can use PDAO as a permission and accountability layer rather than a billing token.
Commercial service access
Longer term, PDAO can anchor recurring governance identity across enterprise deployments, contributor rails, and governed service permissions.
Confidential settlement governance
Future-facing confidential payout and settlement policies can stay governed by PDAO without claiming that the token itself is the settlement asset.
How it connects to the stack
ZK
ZK remains the proof and reviewer-confidence rail around proposal patterns and governance interpretation, not a separate token thesis.
MagicBlock
MagicBlock is the responsive confidential payout corridor. PDAO governs access and policy around that corridor instead of replacing it.
REFHE
REFHE stays the encrypted settlement gate for confidential payout proposals. PDAO is the governance layer deciding when those proposals move forward.
RPC and API
Indexed proposals, hosted reads, diagnostics, and reviewer telemetry make the token strategy inspectable as infrastructure rather than symbolic branding.
Payments
PDAO should be read as a governance and control token around payments readiness, payout policy, and treasury routing, not as the public payments coin itself.

Custody truth quick actions

Open the exact custody truth surfaces directly from the dashboard: reviewer packet, canonical proof, strict intake shape, and the apply route.
Reviewer packet
Shortest reviewer-facing custody truth packet with proven evidence, ceremony gates, and the ingestion route.
Open
Canonical custody proof
Exact ceremony gates, observed chain readouts, and explorer-linked closure points.
Open
Strict intake shape
Canonical multisig intake schema for signer keys, multisig address, timelock proof, and authority-transfer evidence.
Open
Apply route
Open the strict packet workspace, then apply the operator JSON with `npm run apply:custody-evidence-intake`.
Open
Dashboard readiness
Structured custody evidence is partially recorded: 4/6 gates passed.
Partially evidenced

Execution visibility is stronger when custody evidence is visible before reviewers or buyers inspect the board.

Trust state
Some ceremony evidence is recorded, which improves reviewer confidence and points clearly to the remaining readiness steps.
Evidence completion
4/6
Multisig, threshold, signer roster, transfer signatures, and post-transfer readouts are counted together.
Immediate next move
Reviewer confidence improves once the packet is structured and reproducible, but the launch boundary must remain explicit until every signer, transfer, and readout reference is complete.

Dashboard operating health

These four panels keep live Testnet health, proof recency, wallet readiness, and product-to-market posture visible inside the daily product shell instead of hiding them in reviewer docs alone.
Proposal flow health
50%
0/7 governance proof steps are finalized. 1 proposal is already executed on Testnet, 0 proposal is still in commit mode, and 2 proposal is still waiting on settlement evidence.
Open proof and execution
Wallet-by-wallet readiness
Runtime capture live
Wallet diagnostics, connect/sign/submit evidence, and real-device intake are surfaced as a living runtime program with proof packets attached for each supported wallet path.
Open wallet diagnostics
Proof freshness
2d old
Runtime evidence 2d old and Testnet canary 2d old remain published together. The integration packet remains linked as the reviewer baseline without turning an archived source packet into the freshness score. Latest Testnet rehearsal is 21d old with 9 confirmed lifecycle signatures.
Open trust documents
Product-lane commercial readiness
Core Product Lane · Runtime API And Fast Reads · Privacy Infrastructure Lane
Current top conversion-ready product lanes combine commercial upside, operating readiness, and mainnet distance: Core Product Lane (9.2/10) · Runtime API And Fast Reads (8.3/10) · Privacy Infrastructure Lane (7.9/10).
Open learning path
Operating journey
Live operating journey
Freshness
2d old

Use this as the first answer to: what stage of the real wallet-first product cycle is already verified on Testnet, and where evidence coverage is currently scaling.

Connect
Scaling
Wallet evidence intake is active across desktop and mobile paths
Review
Verified
DAO bootstrap and proposal creation are captured in the governance evidence lane
Sign
Verified
Commit, reveal, finalize, and execute signatures are all captured in the wallet-driven lifecycle
Verify
Scaling
Verification continuity exists, but some evidence lanes are still being expanded
Next step
Expand wallet/device evidence
On-chain lifecycle is captured, and wallet/device evidence is attached through signed capture packets as each path is verified.
Open next route

Live proposal execution health

These metrics are shown here so commit, reveal, finalize, and execute stay tied to the live Testnet proof boundary.

Proposal flow health
50%

0/7 governance proof steps are finalized. 1 proposal is already executed on Testnet, 0 proposal is still in commit mode, and 2 proposal is still waiting on settlement evidence.

Open govern flow
Proof freshness
2d old

Runtime evidence 2d old and Testnet canary 2d old remain published together. The integration packet remains linked as the reviewer baseline without turning an archived source packet into the freshness score. Latest Testnet rehearsal is 21d old with 9 confirmed lifecycle signatures. This is the freshness boundary the user and reviewer see before commit, reveal, finalize, and execute.

Open proof path
Current incident watch
RPC delivery
Healthy

Primary Testnet blockhash latency is 104 ms with no unexpected canary failures.

Open diagnostics
Wallet runtime
Watch

The wallet evidence program is active, with browser and device captures attached as they are signed on Testnet.

Review wallet evidence
Replay and retry pressure
Action

27 more attempts than successful tracked transactions are currently recorded; adversarial unexpected success count is 0.

Open incident runbook
Buyer path stays connected

Testnet 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
Execution parity

Execute Proposal

execute_proposal

Executes the treasury action only after pass state, timelock expiry, and recipient validation succeed.

Field order
No instruction args
Accounts
daoread · non-signer
proposalmutable · non-signer
treasurymutable · non-signer
executorread · signer
treasury_recipientmutable · non-signer
treasury_token_accountmutable · non-signer
recipient_token_accountmutable · non-signer
confidential_payout_planread · non-signer
token_programread · non-signer
system_programread · non-signer
Runtime verification status
Execute proposal is live in the web wallet lane for standard, SendSol, and SendToken proposals. The full Solflare browser cycle is captured; Android capture expansion remains pending and CustomCPI stays outside the current executable release boundary.
Open proof packet
Live lane
Wallet-first live
Repo proof
Captured
Browser wallet proof
Captured
Real-device proof
Pending

Live session carried from start and govern

Session active
DAO
PrivateDAO Frontier Council
Proposal
Confidential payroll batch / April
Create DAO
Pending
Create Proposal
Pending
Commit Vote
Pending
Reveal Vote
Pending
Finalize Proposal
Pending
Execute Proposal
Pending
Latest log
No action has been staged yet in this governance session.
Next route
Use the shortest browser-only path first, then come back for proof and judge once real Testnet actions exist.
Open start guide · Use the browser-only entry route if this session still needs wallet and first-run context.
Open learning guide · Explain the product, privacy model, and proof surfaces in plain language.
Open govern flow · Continue the DAO lifecycle from create proposal into commit and reveal.
DAO Card

PrivateDAO Governance Council

Solana Testnet

Treasury
$2.84M
Timelocked treasury with policy-aware execution rails
Members
164
Governance V3 + Settlement V3
Reviewer State
Live proof and runtime evidence available

Execution log

Create DAO
DAO 8c6N...EvjG deployed with policy snapshotting and treasury rails.
Submit proposal
Proposal 6rSb...KqpG recorded with encrypted manifest binding and service-fit guidance.
Private vote
Commit and reveal completed with generated runtime evidence and reviewer path.
Execute treasury
0.05 SOL Testnet execution completed with explicit proof and settlement packet linkage.

Vote timeline

DAO bootstrap
Completed

Create DAO, treasury, policy companions, and migration-safe governance defaults.

Private vote
Completed

Commit-reveal with quorum snapshots, reveal rebate vault, and ZK review overlay when needed.

Evidence boundary
Live

REFHE and MagicBlock runtime checks gate treasury execution without changing the legacy path.

Execution and review
Live

Execution log, Testnet proof packets, and reviewer bundles update together.

PDAO-000-2MCU

Confidential payroll batch / April

Enterprise DAO

Execution ready

Confidential payroll batch / April submitted from the live web governance surface. The governance lifecycle is complete enough that the treasury path is ready to execute once the operator reviews the final packet.

Proposal Review AI
Proposal execution review
Operational notes attached

This motion is close to execution, so the AI layer focuses on beneficiary clarity, treasury magnitude, and proof visibility.

Recipient
Execution target pending index evidence
Amount / mint
Pending exact amount from the indexed proposal record
Recipient is lightly used, so the route should keep an explicit rationale visible before voting.
Timelock is compact, so timing context should stay explicit before execution.
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
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.
Window
Commit closed · Reveal complete · Timelock cleared
Privacy boundary
Commit-reveal governance path
Treasury path
Treasury action is still pending explicit indexing in the current proposal record
ZK
Fast RPC
51% quorum · governance token requirement 0
PDAO-000-CKDQ

Confidential payroll batch / April255552

Enterprise DAO

Execution ready

Confidential payroll batch / April255552 submitted from the live web governance surface. The governance lifecycle is complete enough that the treasury path is ready to execute once the operator reviews the final packet.

Proposal Review AI
Proposal execution review
Operational notes attached

This motion is close to execution, so the AI layer focuses on beneficiary clarity, treasury magnitude, and proof visibility.

Recipient
Execution target pending index evidence
Amount / mint
Pending exact amount from the indexed proposal record
Recipient is lightly used, so the route should keep an explicit rationale visible before voting.
Timelock is compact, so timing context should stay explicit before execution.
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
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.
Window
Commit closed · Reveal complete · Timelock cleared
Privacy boundary
Commit-reveal governance path
Treasury path
Treasury action is still pending explicit indexing in the current proposal record
ZK
Fast RPC
51% quorum · governance token requirement 0
PDAO-000-EPZM

Confidential payroll batch / April

Enterprise DAO

Execution ready

Confidential payroll batch / April submitted from the live web governance surface. The governance lifecycle is complete enough that the treasury path is ready to execute once the operator reviews the final packet.

Proposal Review AI
Proposal execution review
Operational notes attached

This motion is close to execution, so the AI layer focuses on beneficiary clarity, treasury magnitude, and proof visibility.

Recipient
Execution target pending index evidence
Amount / mint
Pending exact amount from the indexed proposal record
Recipient is lightly used, so the route should keep an explicit rationale visible before voting.
Timelock is compact, so timing context should stay explicit before execution.
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
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.
Window
Commit closed · Reveal complete · Timelock cleared
Privacy boundary
Commit-reveal governance path
Treasury path
Treasury action is still pending explicit indexing in the current proposal record
ZK
Fast RPC
51% quorum · governance token requirement 0
PDAO-000-AUWZ

Settlement Hardening V3 + REFHE + MagicBlock live proof

Gaming DAO

Evidence gated

Execute a token confidential payout only after REFHE settlement, MagicBlock corridor settlement, and strict settlement evidence. The governance phase is complete, but settlement evidence still gates the commercial trust surface.

Proposal Review AI
Proposal execution review
Execution notes attached

This motion is still active, so the AI layer focuses on signing clarity, treasury context, and the proof surfaces the reviewer should inspect next.

Recipient
7snWATmFitXe2TZcw58BsNfBT1bwUUMSTdkEfJJo5R7u
Amount / mint
50,000,000 raw token units · A3rV3NguK3VNiEry34qV6KX1YLC1A2wAq22yUWeB2rPu
Large treasury transfer detected relative to a normal Testnet operating motion.
Recipient is lightly used, so the route should keep an explicit rationale visible before voting.
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
7snWATmFitXe2TZcw58BsNfBT1bwUUMSTdkEfJJo5R7u
Baseline motion
50000000 SPL token
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.
Window
Voting closed · Finalized on Testnet · Settlement evidence still incomplete
Privacy boundary
Commit-reveal + REFHE envelope
Treasury path
Confidential payout still gated for 50,000,000 units to 7snW…5R7u via mint A3rV…2rPu
ZK
REFHE
MagicBlock
Fast RPC
51% quorum · governance token requirement 0
PDAO-001-2GDR

REFHE confidential payroll envelope 2026-05-07

Enterprise DAO

Evidence gated

Testnet confidential payout proposal with proposal-bound REFHE envelope commitment for Encrypt/IKA reviewer evidence. The governance phase is complete, but settlement evidence still gates the commercial trust surface.

Proposal Review AI
Proposal execution review
Execution notes attached

This motion is still active, so the AI layer focuses on signing clarity, treasury context, and the proof surfaces the reviewer should inspect next.

Recipient
4Mm5YTRbJuyA8NcWM85wTnx6ZQMXNph2DSnzCCKLhsMD
Amount / mint
1,000,000 raw token units
Large treasury transfer detected relative to a normal Testnet operating motion.
Recipient is lightly used, so the route should keep an explicit rationale visible before voting.
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
4Mm5YTRbJuyA8NcWM85wTnx6ZQMXNph2DSnzCCKLhsMD
Baseline motion
1000000 SPL token
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.
Window
Voting closed · Finalized on Testnet · Settlement evidence still incomplete
Privacy boundary
Commit-reveal + REFHE envelope
Treasury path
Confidential payout still gated for 1,000,000 units to 4Mm5…hsMD via mint native asset
ZK
REFHE
Fast RPC
51% quorum · governance token requirement 0
PDAO-000-B8KY

Settlement Hardening V3 + REFHE + MagicBlock live proof

Gaming DAO

Executed

Execute a token confidential payout only after REFHE settlement, MagicBlock corridor settlement, and strict settlement evidence. This indexed proposal already executed on Testnet and should be reviewed as proof, not as a pending signature flow.

Proposal Review AI
Proposal execution review
Operational notes attached

This motion is already executed on Testnet, so the AI layer focuses on beneficiary correctness, treasury interpretation, and proof continuity.

Recipient
5vQiGkrsfz3wjeFWcPDFLAZV8Xyp36QRWatkh7Rt2FVj
Amount / mint
50,000,000 raw token units · 7VoozT9PVXieCZoB6KrNUQ8g2PDyBoVrhGy82NKGUudg
Large treasury transfer detected relative to a normal Testnet operating motion.
Recipient is lightly used, so the route should keep an explicit rationale visible before voting.
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
5vQiGkrsfz3wjeFWcPDFLAZV8Xyp36QRWatkh7Rt2FVj
Baseline motion
50000000 SPL token
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.
Window
Commit closed · Reveal complete · Executed on Testnet
Privacy boundary
Commit-reveal + REFHE envelope
Treasury path
Confidential payout executed for 50,000,000 units to 5vQi…2FVj via mint 7Voo…Uudg
ZK
REFHE
MagicBlock
Fast RPC
51% quorum · governance token requirement 0

Treasury table

Asset railAllocationValuePolicyRuntime state
SOL treasury0.02 SOLTestnet rehearsal fundedTimelocked execution / onchain treasury PDA · display uses Testnet evidence, not USD AUMLive
Confidential payroll reserveUSDC/PUSD/AUDDIntent receipts readyUmbra/Cloak intent receipts + scoped viewing-key audit postureTestnet-ready lane
Gaming rewards corridorProposal-boundGoverned payout routeMagicBlock settlement evidence with proposal-bound distribution reviewRouted
Strategic grants16%$451kGovernance V3 + live proof bundleLive
Open servicesOpen learning path