Operational Surface
Quick route navigation
Services
Hosted Read API + Ops
Pilot-ready
Commercial
Service and pilot surfaces presented like a product, not buried in docs
PrivateDAO also needs to sell what it can do: API rails, operator support, pilot onboarding, trust packaging, and pricing language that stays technically honest.
Payments truth
Payments truth strip
Give buyers the treasury truth at first glance: public Devnet rails, reviewer packet, commercial fit, and the exact blocker stay visible before deeper service sections.
Payments readiness
Devnet rails live, production treasury still evidence-gated
Treasury network
Solana Devnet
Public rails
3 public rails
Payments fit
strong
Exact blocker
upgrade-authority-multisig · pending-external
Move production upgrade authority and operational authorities to a documented multisig or governance-owned path and rehearse rotation.
24 pending evidence items
Loading execution workbench…
PDAO token strategy
Solana Devnet
Token-2022
Mint authority disabled
PDAO token strategy for buyers, payments, and infrastructure reviewers
Explain the token as governance coordination and commercial control infrastructure: what it already does now, what it gates, what remains future-facing, and how it stays tied to payments, API, RPC, and confidential execution rails without pretending to be a generic payment coin.
Live token truth
Mint
AZUkprJDfJPgAp7L4z3TpCV3KHqLiA8RjHAVhK9HCvDt
Initial supply
1,000,000 PDAO
Exact boundary
PDAO is a live Devnet governance and coordination token. It is not presented as a public mainnet payment coin or speculative market token.
What PDAO does now
Governance participation
PDAO is the live governance mint for the canonical reviewer-facing Devnet DAO 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.
Telemetry truth
Telemetry truth for infrastructure buyers
Put freshness, hosted-read scale, finalized proof counts, and the telemetry packet above the commercial infrastructure story.
Freshness
3d old
Indexed proposal count
41
Governance finalized
7/7
Confidential finalized
5/5
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 are live in-product; same-domain backend serving is still pending host cutover
The current live site is static on GitHub Pages. `/api/v1` becomes a true product rail only after a separate backend host and reverse proxy are cut over.
Read path
backend-indexer
Indexed coverage
41 proposals / 21 DAOs
Confidential
8 confidential payouts
Operator checks
6 operator checks
Integration coverage
4/6 REFHE settled · 3/4 MagicBlock settled
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; public same-domain serving is still pending real cutover
Do not claim `/api/v1` as live on the current public site until the read node is hosted behind a real domain or subdomain with health, metrics, and reverse-proxy evidence.
Deploy target
https://app.privatedao.xyz/ → /api/v1
Health
/healthz
Metrics
/api/v1/metrics
Public checks
6 public checks
Indexed proof
41 proposals / 21 DAOs
Settlement proof
8 confidential payouts · 4 REFHE settled · 3 MagicBlock settled
Telemetry freshness
2026-04-11T14:20:29.957Z
Route binding
Reverse-proxy `/api/v1/*` to the read-node process while keeping writes wallet-signed on the client.
UI fallback policy
Until backend cutover is live, keep read-node evidence available through in-app packets and snapshots.
Ecosystem fit
Services also close real ecosystem focus areas
Make the payments, DAO tooling, developer tooling, and decentralisation fit explicit from the services surface instead of leaving it buried in grant notes.
Promote decentralisation
PrivateDAO already exposes wallet-connected governance, launch blockers, custody truth, authority hardening, and reviewer-safe trust surfaces instead of hiding operational trust in off-product workflows.
Production multisig closure and authority-transfer evidence still remain the real boundary before stronger decentralisation claims can be made for mainnet funds.
Make Solana more censorship resistant
PrivateDAO already ships commit-reveal governance, execution safety boundaries, hosted reads, runtime diagnostics, and reviewer-facing proof routes that strengthen governance resilience.
The strongest censorship-resistance case still depends on completed custody evidence, monitored runtime ownership, and more externally proven infrastructure closure.
DAO tooling
The core live product already covers DAO creation, proposal lifecycle, private voting, treasury motion handling, trust packets, telemetry, and reviewer-safe surfaces.
The highest-value next step is to keep treasury professionalism and custody continuity extremely tight as the product advances toward mainnet operations.
Education
PrivateDAO already ships a hosted story route, community hub, start workspace, reviewer packets, and documents that onboard judges, users, and operators quickly.
Education will get stronger as video openings, onboarding copy, and public community materials stay perfectly synced with live proof and telemetry.
Developer tooling
PrivateDAO already provides reviewer telemetry, generated packets, hosted-read proof, runtime diagnostics, and a developer route tied to real product infrastructure.
The best uplift is continued strengthening of exported telemetry, runtime evidence summaries, and infrastructure-facing docs for external engineers.
Payments
Treasury request routing, confidential payout framing, payments-oriented intake flows, and reviewer-safe custody truth are already visible in the live product.
The strongest version still requires strict sender discipline, explorer-linked rails, and completed authority-transfer evidence for real-funds credibility.
Cause-driven building
PrivateDAO already supports grant governance, community treasury routing, and privacy-aware payout approval flows that can serve more inclusive coordination models.
This remains a selective fit until a cause-specific pilot, partner, or measurable impact program is actually documented.
Live proofs
2
Baseline proof and dedicated V3 proof packet are both reviewer-facing
ZK anchors
3
On-chain proof anchors exposed in the Devnet evidence path
Wallets
50
Multi-wallet Devnet rehearsal already captured and packaged
Commercial rails
4
Grant, fund, gaming, and enterprise service packs remain part of the UI
Commercial readiness
Custody workflow exists, but no structured ceremony evidence is recorded yet.
Pending external
Buyers and judges should see the custody boundary beside service packaging, not only inside security-only routes.
Trust state
No custody ceremony evidence is recorded yet, so trust and mainnet posture must remain bounded.
Evidence completion
0/6
Multisig, threshold, signer roster, transfer signatures, and post-transfer readouts are counted together.
Immediate next move
The product now exposes a strict custody ingestion path, but the mainnet boundary stays blocked until real multisig details, signer keys, transfer signatures, and readout references are recorded.
Data-side quick links
Buyer-safe path into the telemetry packet, diagnostics, analytics, and hosted-read proof so infrastructure reviewers can inspect the data corridor from the services surface.
Private treasury teams and internal governance operators
PrivateDAO Core
The main governance system for private proposals, treasury execution, reviewer-visible evidence, and additive V3 hardening.
ZKREFHEGovernance V3Settlement V3
Open core governance rail
Teams that need a familiar committee and council posture
Realms Compatibility Rail
A compatibility-facing surface for organizations that still think in Realms-style committees but need stronger privacy, proof, and operational rails.
ZK reviewFast RPCReviewer docs
Open reviewer compatibility rail
Mobile-first operators and signer workflows
Android Native
A mobile and Android-facing runtime path for wallet access, reviewer journeys, and diagnostics without pretending the product is desktop-only.
Wallet UXDiagnosticsFast RPC
Open Android runtime surface
Reward programs, tournaments, and token-native communities
Gaming DAO Corridor
MagicBlock-backed evidence corridors for reward distribution and proposal-scoped settlement logic where responsiveness matters.
MagicBlockSettlement V3Proof
Open gaming corridor
Builders, operators, and hosted governance consumers
Read API + RPC
A commercial and operational surface for hosted reads, diagnostics, API-facing ops, and buyer-friendly product packaging.
Fast RPCHosted Read APIOps
Open API and RPC surface
Loading service metrics…
Hosted-read proof strip
Runtime, integration, and reviewer proof tied to one infrastructure story
This strip keeps the RPC and telemetry story concrete: hosted reads, runtime evidence, integration proof, and trust surfaces remain linked so the infrastructure case reads like product value rather than hidden backend detail.
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
Frontier 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 packet now gives a compact path into diagnostics, analytics, runtime evidence, and the hosted-read proof chain.
Try these services now on Devnet
RPC Infrastructure
PrivateDAO RPC is the infrastructure rail behind reads, writes, diagnostics, and buyer-facing hosted governance access.
Try now on Devnet
Open Services and Diagnostics, inspect hosted read coverage, and route into the command center to see the same infrastructure powering live DAO actions on Devnet.
Hosted read coverage
41
The backend-indexer read path currently exposes 41 indexed proposals across 21 DAOs.
Primary RPC latency
242 ms
Current blockhash latency from the primary Devnet endpoint. Version latency is 1504 ms.
Fallback recovery
100%
Fallback RPC recovery is currently passing in the resilience report.
Buyer motion
Sell shared or dedicated DAO-specific RPC plus hosted reads and operator support as the first paid infrastructure motion.
Mainnet gate
Dedicated endpoint hardening, quota enforcement, alert routing, and production support commitments must be closed before mainnet RPC promises become customer-grade.
Gaming DAO
Gaming DAO turns proposal templates, reward treasury, and tournament or guild operations into a live governance corridor rather than a concept pitch.
Try now on Devnet
Use Products for the gaming corridor, then continue into the command center to model reward, clan, or event decisions through the live proposal flow.
MagicBlock settlement completion
100%
5/5 confidential corridor transactions finalized in the current integration evidence package.
Execute health
100%
2/2 tracked execute operations finalized across simple governance and confidential settlement paths.
Wallet coverage
80%
4/5 wallet classes are review-ready. Selector coverage is 100%.
Buyer motion
Lead game studios with reward governance, guild treasury control, and tournament payout management as a repeatable premium package.
Mainnet gate
Game-specific proposal templates, reward token policy hardening, and studio-grade custody or treasury authority separation must be finalized before production launch.
Payments DAO
Payments DAO extends the treasury model into contributor, vendor, and subscription payouts governed through the same proposal and proof rails.
Try now on Devnet
Open Services, then the command center, and walk through treasury-backed proposal execution as the governed payout path for contributors or vendors.
Confidential payout coverage
8
8 confidential payout proposals are indexed, with 4 REFHE-settled flows.
Execute health
100%
2/2 tracked execute operations finalized across simple governance and confidential settlement paths.
Proof completion
100%
7/7 canonical governance lifecycle transactions are finalized in the live proof package.
Buyer motion
Position governed payouts as the first paid motion for teams that need contributor, vendor, or internal treasury disbursements with reviewable controls.
Mainnet gate
Real payment rails need stricter beneficiary validation, payout policy closure, production custody ceremony, and external audit evidence before mainnet claims.
Security / Encryption
Security is a product layer here: ZK, REFHE, MagicBlock, trust packets, and runtime diagnostics are visible to users, buyers, and reviewers.
Try now on Devnet
Open Security, inspect the ZK matrix and confidence engine, then jump into Proof and Diagnostics to see the encrypted and reviewer-facing path stay connected.
Proof freshness
3d old
Runtime evidence 3d old, Devnet canary 3d old, and frontier integrations 3d old remain published together.
Wallet coverage
80%
4/5 wallet classes are review-ready. Selector coverage is 100%.
Proof completion
100%
7/7 canonical governance lifecycle transactions are finalized in the live proof package.
Buyer motion
Sell confidential operations, proof-backed governance, and trust packaging as a premium layer for privacy-sensitive organizations.
Mainnet gate
Mainnet security promises remain blocked until multisig authority transfer, incident monitoring closure, audit posture, and real-device capture coverage are all complete.
AI-powered features
Operational intelligence is now part of the commercial surface
Proposal Review AI, Treasury Review AI, Voting Summary, RPC Analyzer, and Gaming AI strengthen how buyers understand PrivateDAO. They are part of the product story because they improve real decisions.
Commercial services
Hosted Read API + Ops
Serve governance state, runtime evidence, and diagnostics through a cleaner operational API layer.
Pilot Package
Week-by-week rollout with trust packet, SLA framing, and buyer-friendly onboarding.
Confidential Operations Premium
Add encrypted payout boundaries, V3 hardening, and reviewer-ready execution evidence.
Pilot and trust journey
Pilot Program
Week-by-week rollout packet for teams that want guided adoption rather than a raw protocol integration.
Service Level Agreement
Operational framing for hosted reads, response expectations, and trust boundaries.
Pricing Model
Commercial packaging for API, ops, and confidential governance support without hiding the technical stack.
Trust Package
A buyer-readable path into proof packets, runtime evidence, and launch readiness boundaries.
Pilot Package
Best for teams validating private governance and treasury operations before a longer rollout.
Week-by-week onboarding, trust packet, readiness framing, and guided operating plan.
Open pilot program
Hosted Read API + Ops
Best for apps or teams that need cleaner governance data, evidence reads, and reviewer exports.
Hosted read surfaces, ops guidance, reviewer packet alignment, and product-facing API framing.
Open service catalog
Confidential Operations Premium
Best for payroll, bonus, and private treasury teams that need stronger confidentiality boundaries.
REFHE paths, V3 hardening, evidence-gated treasury flows, and operator trust surfaces.
Open pricing model
Enterprise Governance Retainer
Best for organizations that want longer-term support across launch, controls, and operator workflows.
SLA framing, trust package, launch blockers review, and governance operations guidance.
Open SLA
Open /intelligence to try the live Security + Intelligence layer. It is where proposal analysis, treasury warnings, voting compression, RPC interpretation, and gaming-governance assistance become user-visible.
Loading treasury routes…
Treasury reviewer-grade
Treasury reviewer-grade bundle
Collapse treasury professionalism into one reviewer-grade surface before the receive rails: sender discipline, proof links, rail references, commercial fit, and the exact blocker stay visible together.
Treasury network
Solana Devnet
Exact blocker
upgrade-authority-multisig
pending-external
Payments fit
strong
Reviewer-safe treasury intake and payout framing are already live.
Pending closure
24 items
Move from intake rails to production-safe custody evidence.
Strict sender checklist
1Confirm whether the request is a treasury top-up, pilot-funding packet, vendor payout, or contributor payout before selecting a rail.
2Copy the exact public receive address and explorer link for the selected asset rail. Do not reuse a rail from memory.
3Attach a reference string that includes payer, purpose, amount, and settlement context so the intake packet can be matched later.
4Open reviewer truth surfaces before promising production-safe settlement or custody posture to a sender, buyer, or judge.
5Treat the current rails as Devnet/public treasury intake until authority-transfer evidence closes the production custody blocker.
Reference-linked rails
SOL
Native SOL
AZUroiNeGAjNdD84eEHnAKHHFwqAFmkjr2g1eoF7Ek5c
Use this rail for treasury top-ups, operator funding, and governed SOL transfers on Devnet.
Mint: Configured at deployment / public receive rail only
USDC
USDC
AZUroiNeGAjNdD84eEHnAKHHFwqAFmkjr2g1eoF7Ek5c
Use this rail for governed payouts, vendor settlement, and stable-value treasury requests when USDC is the active stable asset.
Mint: Configured at deployment / public receive rail only
USDG
USDG
AZUroiNeGAjNdD84eEHnAKHHFwqAFmkjr2g1eoF7Ek5c
Use this rail for alternative stable settlement when the team or customer operates with USDG-compatible treasury flows.
Mint: Configured at deployment / public receive rail only
Commercial + payments focus alignment
DAO tooling
strong
The core live product already covers DAO creation, proposal lifecycle, private voting, treasury motion handling, trust packets, telemetry, and reviewer-safe surfaces.
Exact gap: The highest-value next step is to keep treasury professionalism and custody continuity extremely tight as the product advances toward mainnet operations.
Developer tooling
strong
PrivateDAO already provides reviewer telemetry, generated packets, hosted-read proof, runtime diagnostics, and a developer route tied to real product infrastructure.
Exact gap: The best uplift is continued strengthening of exported telemetry, runtime evidence summaries, and infrastructure-facing docs for external engineers.
Payments
strong
Treasury request routing, confidential payout framing, payments-oriented intake flows, and reviewer-safe custody truth are already visible in the live product.
Exact gap: The strongest version still requires strict sender discipline, explorer-linked rails, and completed authority-transfer evidence for real-funds credibility.
Exact blocker visibility
upgrade-authority-multisig
Move production upgrade authority and operational authorities to a documented multisig or governance-owned path and rehearse rotation.
Severity: critical
Status: pending-external
Pending evidence: chosen multisig implementation · multisig public address · multisig creation signature · rehearsal signature
Loading treasury receive surface…
PrivateDAO platform architecture
PrivateDAO should read as governance infrastructure, not as a single DAO toy. These layers keep the product, infrastructure, gaming, payments, proof, and developer story aligned.
Layer 1
Governance Core
The live governance engine already runs the end-to-end DAO lifecycle with treasury execution inside the product shell.
Create DAO
Create Proposal
Commit Vote
Reveal Vote
Finalize Proposal
Execute Proposal
Treasury Execution
Layer 2
RPC Infrastructure
PrivateDAO is also an infrastructure surface: hosted reads, diagnostics, metered RPC posture, and DAO-specific runtime visibility.
Dedicated Solana RPC
Shared RPC
DAO-specific RPC
Read API
Usage diagnostics
Runtime evidence
Layer 3
Gaming DAO Toolkit
Gaming DAO turns reward, guild, clan, and tournament decisions into governance flows with proposal templates and treasury rails.
Game governance
Reward treasury
NFT voting
Clan DAO
Tournament payouts
Game proposal templates
Layer 4
Payments DAO Engine
Payments extends the treasury model into contributors, vendors, subscriptions, and governed payout approvals.
Wallet payments
Contributor payouts
Vendor payments
Subscription billing
Treasury payouts
Payment approvals
Layer 5
Security and Proof Layer
ZK, REFHE, MagicBlock, Fast RPC, diagnostics, and trust packets are exposed as product rails rather than hidden implementation detail.
ZK capability matrix
Proof center
Confidence engine
Incident readiness
Authority hardening
Runtime diagnostics
Layer 6
Developer Platform
The platform also needs a developer-facing surface for SDK, API, templates, billing posture, quotas, and RPC access.
SDK
API
CLI
Templates
API key issuance posture
Quota and billing framing
Operational proof chain
Live product
Real service
Wallet-first command center and dashboard for live governance operations.
Hosted Read API + Ops, confidential operations, and enterprise governance service packaging.
Proof, diagnostics, and trust routes connected to the same product shell customers see.
Verification gates
Automated validation
`verify:frontend-surface`, `verify:browser-smoke`, and `web:verify:live:root` keep the live app honest.
`verify:runtime-surface`, `verify:generated-artifacts`, and wallet/runtime gates keep proof and ops routes synchronized.
Track validation stays tied to the actual sponsor, proof, and buyer surfaces instead of isolated scripts.
Published evidence
Measurable evidence
Runtime evidence, wallet matrix, PDAO attestation, and live proof packets remain published and inspectable.
Competition and mainnet claims are backed by generated artifacts, not only UI text.
The same evidence surfaces support judges, buyers, operators, and future customers.
Commercial delivery
Buyer-ready surface
Pilot, hosted reads, confidential operations, and enterprise governance are presented as real offers.
Trust package, launch trust packet, and mainnet blockers keep sales posture grounded in truth.
Competition workspaces now connect directly into customer conversion and mainnet trajectory.