PrivateDAO is loading wallet-ready controls, Devnet context, and proof-linked routes so the app lands with real content instead of an empty frame.
This route trains the operator-facing payment story: what stays confidential, what becomes public, and how to move from an easy UI explanation into the real payment, proof, and explorer lanes on Devnet.
This route turns the starter into a live in-product sandbox. Use it to understand the UI pattern quickly, then move directly into the production Devnet corridor and verify the blockchain result from the linked proof route.
The sandbox teaches the operator-facing wording: what stays confidential, what becomes public, and where the reviewer should click next. The verification link below points to a real Devnet signature from the current payment evidence set.
This starter shows how to explain what remains confidential, what becomes public, and where the reviewer can verify the result without exposing the user to cryptographic jargon.
Explain privacy in human terms before the user ever sees a proof route, ZK note, or explorer link.
Keep the public verification path one click away so a reviewer can confirm the evidence immediately after reading the explanation.
Tie the payment starter to the existing agentic treasury rail and confidential payout evidence already recorded on Devnet.