Explore

Product navigation

Judge Route
Canonical reviewer path with product proof, integrations, awards context, and runtime evidence
Start
Guided onboarding and wallet-first flow
Learn
Workflow-first onboarding and product operating guide
Help
Product guide across routes, docs, and proof
Govern
Create, vote, and execute on Solana Testnet
Intelligence
Risk scoring, market context, and signer decision support
Treasury
Treasury health, solvency context, and agent policy routes
Payroll
Private payroll CSV, stablecoin choice, and auditor receipt flow
Gaming
Guilds, tournaments, inventory proposals, and reward operations
Compliance
Scoped compliance packs and bounded viewing-key evidence
Execute
Private payroll, vendor settlement, and treasury actions
Proof
Operation receipts, runtime logs, and verification routes
Developers
API docs, SDK starters, and integration surfaces
RPC Services
Hosted reads, relayer checks, QVAC status, and runtime endpoints
API Status
Backend health, visitor counters, and freshness endpoints
Command Center
Ops dashboard, indexed proposals, and readiness gates
Live State
Proposals, treasury, and action logs
Story
Live product story and fast explanation
Community
Join, updates, pilot interest, and support routing
Benefit
theMiracle wallet-placement benefit and Founding Governor access
Versus
PrivateDAO compared with Realms, Squads, Snapshot, and DAOhaus
Revenue
Self-hosted, managed SLA, and enterprise commercial tiers
Android
Mobile app, APK download, parity plan
Trust
Security, proof, and operating boundaries
Health
Runtime status and verification health
Custody
Multisig, authority transfer, and custody evidence
Analytics
Votes, proposals, actions
API & Pricing
Pilot, API, commercial packs
Engage
Buyer path, pilot motion, mainnet trajectory
Search
Search routes, docs, tracks, and proof
Docs
Curated reviewer and trust docs
Docs and viewers
Reviewer-ready
Product-aware
Developers
Documentation, proof packets, viewers, and engineering surfaces

Developer-facing access should start with curated docs and continue into the broader repository viewer and proof surfaces.

Ecosystem fit

Developer tooling fit should be obvious on the developer route

Keep the tooling, telemetry, censorship-resistance, and infrastructure fit legible before the reviewer dives into proof packets and repo artifacts.
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.

Developer portal

The developer surface should make PrivateDAO feel like a platform: RPC, API, SDK, templates, diagnostics, and proof-aware integration paths.

RPC plans
Free
Free
100K requests · Testnet
Builders evaluating PrivateDAO RPC and diagnostics on Testnet.
Pro
Subscription
5M requests · Testnet + hosted reads
Teams running governance, payouts, and app reads on a shared product rail.
Enterprise
Custom
Unlimited / negotiated · Dedicated endpoint
Organizations that need DAO-specific RPC, higher trust boundaries, and operator support.
Access model
PrivateDAO presents the commercial surface now and keeps the launch boundary honest: API key issuance posture, metered quotas, and usage billing belong to the product strategy and services layer while Testnet operation and proof stay visible in the app today.

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
Open govern flow
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
Open RPC surface
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
Open gaming corridor
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
Open payments corridor
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
Open trust layer
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
Open developer portal

Find the problem, open the solution, verify the action

48 results
Search works like a product guide: describe the problem, then open the page where PrivateDAO shows the solution, the signing path, and the proof route.
Route-aware answer
Start from the product shell

If the goal is unclear, begin at onboarding or the govern flow. That gives the shortest route to a real product flow, wallet action, proof surface, or learning path.

Start
Route
Guided onboarding, wallet-first flow, and easiest entry for normal users.
Story Video
Route
Hosted product reel for judges, users, and sponsors.
Community
Route
Join Discord, follow product updates, open pilot interest, and route into support or operator paths.
Dashboard
Route
Governance dashboard with proposal cards, treasury data, and execution visibility.
Govern
Route
Create a DAO, submit a proposal, vote, finalize, and execute in one guided product flow.
Proof Center
Proof
Baseline proof, V3 proof, runtime evidence, and reviewer entrypoints.
Security
Proof
ZK matrix, confidence engine, policy composer, and hardening surfaces.
Intelligence
Route
Proposal Review AI, Treasury Review AI, Voting Summary, RPC Analyzer, and Gaming AI in one operational layer.
Diagnostics
Route
Runtime health, readiness, reviewer bundle, and live Testnet operational evidence.
Services
Service
Pilot, API, RPC, enterprise governance, and hosted operational packages.
Zerion Agent Policy
Service
Policy-bound autonomous execution surface with Solana chain lock, spend caps, expiry windows, blocked actions, and approve-before-execute treasury controls.
REFHE Payroll Proof
Service
Encrypted payroll proof route with browser-side ciphertext generation, computation commitments, and live Ika SDK custody readiness.
Covalent GoldRush Intelligence
Service
Counterparty and wallet analysis lane using Covalent GoldRush status with Zerion and Solana RPC fallback when credits are exhausted.
Torque Growth Loop
Service
Custom event workbench for turning DAO creation, proposal creation, billing signatures, and learning completion into measurable retention loops.
Learn
Track
Learning and product route hub across governance, payments, proof, and operator surfaces.
Start Product Route
Track
Primary wallet-first product route for real Testnet operations and reviewer verification.
Assistant
Route
Internal product guide for finding the best route, proof packet, or submission path fast.
Payments Reviewer Fast Path
Document
Shortest reviewer-safe route into treasury packet, custody truth, services payments rail, and govern payout path.
PDAO Token Surface
Document
Reviewer-safe token truth for preserved PDAO governance-token evidence, including mint details, attestation, and how it connects to the current Testnet path.
Zerion Autonomous Agent Policy
Document
Agent policy packet for safe Zerion CLI fork execution: no god-mode agent, no unbounded treasury movement, and explicit DAO approval before wallet execution.
Torque Growth Loop
Document
Growth packet for emitting PrivateDAO product actions as Torque-style custom_events tied to real governance, billing, and learning activity.
Token Architecture
Document
Canonical architecture note for what PDAO is, what it gates, and what remains future-facing without speculative tokenomics.
Documents
Document
Curated reviewer and trust document library inside the product.
Custody
Route
Strict custody evidence route for multisig, timelock, signer roster, and authority-transfer proof.
Canonical Custody Proof
Document
Repo-backed custody truth packet with exact ceremony gates, observed readouts, and explorer-linked closure points.
Custody Proof Reviewer Packet
Document
Reviewer-facing custody packet that condenses what is proven now, what remains ceremony-gated, and the strict ingestion route.
Treasury Reviewer Packet
Document
Generated treasury-facing reviewer packet with strict sender checklist, reference-linked rails, reviewer truth links, payments fit, and exact blocker visibility.
Reviewer Telemetry Packet
Document
Reviewer-safe packet for telemetry, hosted reads, runtime evidence, and infrastructure-facing product value.
Read-Node Backend Cutover Packet
Document
Deployment-target packet for turning reviewer-visible read-node evidence into a real hosted backend corridor with route binding and UI fallback policy.
Strategic Opportunity Readiness
Document
Opportunity map for startup acceleration, regional grants, data and telemetry, confidential payout, and hardening-first corridors around the current review cycle.
Ecosystem Focus Alignment
Document
Reviewer-safe mapping from the live product into decentralisation, censorship resistance, DAO tooling, education, developer tooling, payments, and selective cause-driven fit.
Multisig Setup Intake
Document
Canonical intake shape for signer keys, multisig address, timelock, and authority-transfer evidence.
Confidential Governance Route
Track
Confidential-governance product bundle and validation steps.
Live App Route
Track
Wallet-first live app corridor for buyer-facing walkthroughs and polished product flow.
Runtime Infrastructure Route
Track
Hosted read path, diagnostics, runtime evidence, and Fast RPC packaging.
Wallet-First Product Route
Track
Best path for normal users, onboarding, clarity, and consumer-grade UX.
Frontend Execution Route
Track
Frontend excellence, route architecture, deployment discipline, and polished shell.
Cryptographic Confidence Engine
Document
Deterministic scoring for ZK, REFHE, MagicBlock, Fast RPC, and governance posture.
Proposal Review AI
Service
Pre-vote proposal review for amount size, recipient context, timelock strength, and treasury framing.
Treasury Review AI
Service
Treasury execution review for payout size, route history, timing context, and destination visibility.
Voting Summary
Service
Compress governance discussion into support, concern, and execution-safety signals.
RPC Analyzer
Service
Turn latency, success rate, error rate, and retry pressure into a readable RPC health posture.
Gaming AI
Service
Evaluate reward changes, payout fan-out, and clan impact before game-governance rollout.
ZK Capability Matrix
Document
What the ZK stack proves today, how it is verified, and what is not claimed.
Live Proof V3
Proof
Dedicated additive hardening proof for Governance V3 and Settlement V3.
Trust Package
Document
High-signal trust packet for buyers, judges, and operators.
Authority Hardening for Mainnet
Document
Multisig, upgrade authority, treasury authority, and admin-boundary discipline before Mainnet.
Incident Readiness Runbook
Document
Monitoring, alerts, logs, and operator response loop for RPC, wallet, and governance failures.

Why this matters

Custody summary
Structured custody evidence is partially recorded: 4/6 gates passed.
Partially evidenced

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.

Evidence completion: 4/6
Recognition tied to evidence

The awards surface should not be vanity-only. It should route judges, buyers, and operators directly into proof packets, trust surfaces, and production-readiness context.

Readiness discipline

This Next.js surface keeps the same discipline as the current site: Testnet proof is shown as current operating proof, historical rehearsal evidence stays separated as archive material, and the remaining launch-critical work stays visible as the next readiness gate rather than hidden behind vague claims.