PrivateD△O
Try Testnet VoteReviewVoteVerify
Explore

Product navigation

Judge Route
Canonical reviewer path with product proof, integrations, awards context, and runtime evidence
Try
Shortest Testnet vote path
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
4 lectures
Product-first
Proof-aware
Quizzes
Check understanding before you ship

These quiz prompts are designed to keep the builder honest: if they cannot explain the product boundary, they are not done with the feature.

Open governOpen executeOpen curated docs
PrivateDAO Frontend Bootcamp
L1L2L3L4SlidesToolkitTasksQuiz
Lecture 1
From Web2 Frontend to Solana Wallet-First UX
Why is wallet-first UX a core Solana requirement here?
  • A)Because a signer is part of the product flow, not a backend detail.Correct
  • B)Because it replaces proof entirely.
  • C)Because it avoids Testnet usage.
What should a normal user do after connecting a wallet?
  • A)Choose the right corridor and continue into the live route.Correct
  • B)Open the terminal and inspect RPC logs first.
  • C)Read every protocol spec before clicking anything.
What is the first practical step in Solana wallet-first UX?
  • A)Connect the wallet and surface signer context.Correct
  • B)Deploy a new program before opening the UI.
  • C)Generate a PDA before showing any interface.
Why does PrivateDAO show corridor selection immediately after connect?
  • A)So the user can enter the right governance, treasury, or analytics path without confusion.Correct
  • B)So the user is forced to read all documents first.
  • C)So the wallet can be disconnected faster.
What makes the starter shell production-useful instead of tutorial-only?
  • A)It routes directly into real product surfaces like Start and Command Center.Correct
  • B)It hides all runtime state until later lectures.
  • C)It only works with screenshots instead of live routes.
Lecture 2
Building Governance UI: Create, Vote, Reveal, Execute
Why does commit-reveal matter in this product?
  • A)It protects vote intent until the right proof stage.Correct
  • B)It removes the need for wallet signatures.
  • C)It replaces runtime logs.
What is the role of voice governance here?
  • A)It reduces friction while keeping the final signer boundary intact.Correct
  • B)It executes on-chain actions without wallet approval.
  • C)It hides every governance state from the user.
Which governance UI states should stay visible to a normal operator?
  • A)Create, vote, reveal, execute, and final verification state.Correct
  • B)Only the final execute button.
  • C)Only backend logs and raw account data.
Why should execution remain wallet-signed even with a smoother UI?
  • A)Because the cryptographic boundary still matters even when the UI is simple.Correct
  • B)Because commit-reveal is not compatible with signatures.
  • C)Because Solana wallets cannot sign governance actions.
What is the correct user flow after a proposal is approved?
  • A)Open verification or proof and inspect the resulting signatures and status.Correct
  • B)Close the app because governance is finished.
  • C)Hide the outcome until mainnet.
Lecture 3
Solana Runtime UX: Hosted reads, Diagnostics, and Activity Tracking
Why does Hosted reads matter to the user experience here?
  • A)It makes proposal, proof, and payout state update quickly enough to feel trustworthy.Correct
  • B)It removes the need for analytics.
  • C)It only matters to validators, not to users.
What should happen after a wallet action lands?
  • A)The user should be able to follow the hash, status, and logs.Correct
  • B)The UI should stop explaining anything.
  • C)The app should hide runtime state until mainnet.
What does RPC stand for in this learning path?
  • A)Remote Procedure Call.Correct
  • B)Runtime Privacy Corridor.
  • C)Rapid Program Chain.
Why are diagnostics part of product UX instead of backend-only tooling?
  • A)Because they help the user understand freshness, retries, and what the chain actually recorded.Correct
  • B)Because diagnostics replace wallet signatures.
  • C)Because analytics pages should never show transactions.
What makes a runtime widget useful for a non-expert?
  • A)It shows the last action, tx hash, current status, and the next recovery hint.Correct
  • B)It only displays raw JSON responses.
  • C)It hides status until the session ends.
Lecture 4
Private Payments, Gaming DAO, Proof, and Agentic Rails
What is the correct product role for ZK here?
  • A)Protect sensitive intent first, then expose the right proof after execution.Correct
  • B)Hide all blockchain evidence permanently.
  • C)Replace wallets and signatures.
Why include encrypted treasury execution in the learning path?
  • A)Because it shows how governed policy can drive many real on-chain actions without turning the user into a script operator.Correct
  • B)Because it removes governance from the product.
  • C)Because it only matters for a one-off sandbox.
What should a judge or operator understand after using the private payment lane?
  • A)What stayed private, what became public on-chain, and where the proof lives.Correct
  • B)That all payment details are hidden forever with no verification.
  • C)That privacy eliminates the need for logs.
Why is MagicBlock discussed in this lecture?
  • A)Because responsive execution lanes matter when advanced flows must still feel immediate in the browser.Correct
  • B)Because it replaces Solana RPC entirely.
  • C)Because it removes the need for governed execution.
Why are Jupiter and Kamino shown inside the same product story?
  • A)Because treasury coordination, routing, and capital posture belong in one practical operator flow.Correct
  • B)Because they are only branding partners with no product role.
  • C)Because gaming rewards cannot use treasury rails.