PrivateD△O
Search or ask AI
Operational Surface

Quick route navigation

Start
Guided onboarding and wallet-first flow
AI Assistant
Internal AI-style guide across routes, docs, and proof
Story
Hosted product video and why-us reel
Community
Join, updates, pilot interest, and support routing
Command Center
Create, vote, execute
Dashboard
Governance state and treasury
Proof
Baseline and V3 evidence
Security
Hardening and cryptography
Intelligence
Proposal, treasury, voting, RPC, and gaming analysis
Diagnostics
Runtime and artifact health
Custody
Multisig, authority transfer, and custody evidence
Analytics
Votes, proposals, actions
Services
Pilot, API, commercial packs
Engage
Buyer path, pilot motion, mainnet trajectory
Tracks
Competition readiness and fit
Search
Search routes, docs, tracks, and proof
Documents
Curated reviewer and trust docs
Docs and viewers
Reviewer-ready
Track-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.

Open command centerOpen dashboardOpen curated docs
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.
Open focus packetOpen strategic opportunity map

Developer portal

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

Recommended path
RPC and hosted reads path

Start with the services route for shared or dedicated RPC, diagnostics, runtime evidence, and hosted API framing.

Open RPC path
RPC access

Dedicated RPC, shared RPC, DAO-specific RPC, and hosted read surfaces tied to diagnostics and runtime evidence.

API and SDK

Developer-facing API, SDK, CLI, and templates for integrating governance, payouts, and proof-aware reads.

Gaming DAO templates

Proposal templates for events, rewards, guild voting, and game economy changes.

Payments and governed payouts

Contributor, vendor, and subscription approvals routed through the same treasury and proof rails.

RPC plans
Free
Free
100K requests · Devnet
Builders evaluating PrivateDAO RPC and diagnostics on Devnet.
Pro
Subscription
5M requests · Devnet + 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 Devnet operation and proof stay visible in the app today.
Open engageOpen diagnostics

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 governance core
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

Search or ask AI

42 results
Ask in natural language: “I need pilot funding”, “vendor payout”, “treasury top-up”, “custody proof”, “reviewer packet”, “multisig intake”, “best wallet for consumer demo”, or “what is blocking privacy track mainnet?”.
AI routing answer
Start from the product shell

If the goal is unclear, begin at onboarding or the command center. That gives the shortest route to a real product flow, wallet action, proof surface, or competition workspace.

Open start workspaceCommand CenterSearchTracks
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.
Command Center
Route
Create, vote, execute, and track proposal confidence in one workspace.
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 devnet operational evidence.
Services
Service
Pilot, API, RPC, enterprise governance, and hosted operational packages.
Tracks
Track
Submission corridor center across Frontier, runtime infrastructure, confidential governance, grants, and adjacent reviewer opportunities.
Frontier Primary Workspace
Track
Primary first-place startup-quality submission chain for the Frontier Hackathon.
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 command-center payout path.
PDAO Token Surface
Document
Reviewer-safe token truth for the live Devnet governance mint, including mint details, attestation, and what PDAO does now.
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 ingestion workspace for multisig, timelock, signer roster, and authority-transfer proof.
Canonical Custody Proof
Document
Repo-backed custody truth packet with exact pending items, observed readouts, and explorer-linked closure points.
Custody Proof Reviewer Packet
Document
Reviewer-facing custody packet that condenses what is proven now, what is still pending, 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 accelerator, regional grants, data and telemetry, confidential payout, and hardening-first corridors around the Frontier 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 Workspace
Track
Confidential-governance submission bundle and validation steps.
Live App Workspace
Track
Wallet-first live app corridor for buyer-facing demos and polished product flow.
Runtime Infrastructure Workspace
Track
Hosted read path, diagnostics, runtime evidence, and Fast RPC packaging.
Wallet-First Product Workspace
Track
Best path for normal users, onboarding, clarity, and consumer-grade UX.
Frontend Execution Workspace
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.

Proof center

Live proof

Canonical Devnet create → vote → execute flow with public reviewer links.

Open judge view
Live proof V3

Dedicated additive hardening proof for Governance V3 and Settlement V3.

Open curated V3 packet
ZK capability matrix

PrivateDAO-specific matrix for what the ZK stack proves today, how it is verified, and what is still explicitly not claimed.

Open curated ZK matrix
Cryptographic confidence engine

Deterministic scoring model for how ZK, REFHE, MagicBlock, and Fast RPC strengthen specific proposal patterns.

Open engine specification
Frontier integrations

ZK, REFHE, MagicBlock, backend-indexed reads, and runtime evidence in one surface.

Open integrations packet
Audit packet

Reviewer and launch artifacts tied together with generated attestations.

Open curated audit packet

Security rails

ZK Capability Matrix

Layer-by-layer truth-aligned matrix for proofs, anchors, attestation, zk_enforced posture, and verifier boundaries.

Cryptographic Confidence Engine

Proposal-aware scoring model for privacy depth, enforcement depth, execution integrity, and reviewer confidence across ZK, REFHE, MagicBlock, and Fast RPC.

Governance Hardening V3

Token-supply quorum mode, policy snapshots, and reveal rebate vaults stay additive and versioned.

Settlement Hardening V3

Payout caps, evidence aging, REFHE/MagicBlock requirements, and single-use settlement consumption semantics.

Mainnet blockers

The app keeps launch boundaries honest: what is live now, what is pending-external, and what still needs custody/audit work.

Reviewer and trust links

Story video

The comprehensive product reel that explains everything PrivateDAO offers and why the project is competition-ready.

Judge proof view

Fastest reviewer path into the live product proof surface.

Audit packet

Generated audit-facing packet that ties reviewer and launch evidence together.

Launch trust packet

Commercial and launch trust narrative with boundaries kept explicit.

Mainnet blockers

Honest list of what still needs custody, audit, and runtime evidence before real-funds launch.

Presentation deck

Pitch-ready investor and competition presentation surface.

Live proof V3

Dedicated additive hardening proof packet for Governance V3 and Settlement V3.

Why this matters

Custody summary
Custody workflow exists, but no structured ceremony evidence is recorded yet.
Pending external

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.

Evidence completion: 0/6
Recognition tied to evidence

The awards surface should not be vanity-only. It needs to route judges, buyers, and operators directly into proof packets, trust surfaces, and launch boundaries.

Boundary discipline

This Next.js surface keeps the same discipline as the current site: Devnet proof is shown as Devnet proof, and pending-external launch work stays marked as pending-external.