Product navigation
This surface is the receipt layer for executed operations: baseline live proof, dedicated V3 hardening proof, integration packets, and the exact routes used after running real Testnet flow through the public product.
See what stays private, what becomes public, and how the chain proves it
This proof route turns privacy into something inspectable: public hashes, runtime logs, and proof packets stay visible while sensitive intent remains protected until the right stage.
Every major route must lead to review, execution, or verification
PrivateDAO is organized as an operating path: intelligence reviews the action, privacy rails prepare the protected packet, the user signs from the wallet, and proof routes expose the receipt or blockchain evidence. The normal user should not need code or a terminal; the interface carries governance, treasury, private intent, encrypted claims, wallet-first signing, and verification as one browser flow.
Move from governance token intent to treasury policy, private intent, wallet approval, and Anchor 1.0.1 proof.
Review wallet, proposal, RPC, provider context, and QVAC local-first risk before signing.
Run local-first sensitive decision intelligence before any treasury or governance signature.
Generate a visitor-repeatable encrypted claim and prepare a Solana Testnet memo.
Open REFHE receipts, Ika Solana final approval, and custody preparation.
Run wallet-first payroll, settlement, treasury, or reward operations.
Proof is the truth boundary for the product. It separates executed on-chain activity, live service health, encrypted intent receipts, and final private settlement evidence so judges and users do not confuse one for another.
Run one real action first, then use Proof to inspect what stayed private and what the chain exposed
Proof is not a theory page. It is the operating surface that turns live Testnet execution into something readable. Create a DAO, submit a proposal, vote, reveal, finalize, or execute. Then open this route to inspect signatures, runtime freshness, screenshots, privacy evidence, and the narrow boundary between public verification and protected intent.
Live Testnet freshness and private visitor signal
Every visit pings the read node without storing personal data. Freshness is backed by a throttled Solana Testnet memo transaction, and usage is counted by hashed browser session only.
Counted privately — no personal data stored.
What this video covers
Hosted review asset
Before opening detailed packets, read the current Testnet operating journey here: what is verified, what is captured from runtime evidence, and what is attached to receipt exports.
The secret parts stay hidden. The proof that the operation happened stays public.
PrivateDAO does not treat privacy as “nothing is visible.” It treats privacy as stage control. Sensitive vote intent and payout context stay protected until the correct step, while the blockchain still records the commitment, reveal, settlement, execute, and proof-anchor transactions that a reviewer can inspect.
Fair voting without early vote leakage
The vote choice stays hidden during the commit stage. The chain records a commitment first, then the reveal later.
The reveal and execute signatures are public, and the proof-anchor transaction shows that the review surface is tied to real proposal context.
Confidential settlement with public execution proof
Sensitive payout intent, recipient context, and settlement posture stay protected until the right review stage.
The chain still records deposit, private-transfer, settle, and execute hashes so a reviewer can see the corridor land on Testnet without reading the hidden payload itself.
Normal users can verify the result from the browser
Nothing secret is forced into plaintext just to make the UI understandable.
The product exposes signatures, logs, status, screenshots, and mobile wallet evidence so the same workflow can be checked from a browser, a wallet app, or Solscan.
The product flow is meant to be clicked, signed, executed, and verified by a normal visitor
This route turns the technical stack into a simple operating loop: connect a Testnet wallet, review the decision, sign the exact action, then verify the hash and proof continuity from the same product shell.
Open the wallet button, choose Solflare first or Phantom, Glow, Backpack, or a Wallet Standard wallet, then confirm the Testnet account you want to operate from.
Open Intelligence to inspect policy, risk, treasury context, and privacy posture before the wallet prompt appears.
Continue to Govern and Execute, then approve the exact wallet request for the DAO action, proposal flow, or treasury movement from the same browser session.
Open Proof or the Testnet lifecycle packet and inspect signatures, accounts, treasury delta, and proof continuity without touching the terminal.
Every product claim is tied to a working surface, evidence packet, or executable route
This is the operating boundary as a product surface: not hidden text, not vague disclaimers. Each row shows what the Testnet product currently proves, where a reviewer can inspect it, and which route a user can open next.
A standalone Anchor verifier program is live on Solana Testnet and emits a reviewer-visible Groth16 receipt through the native BN254 pairing syscall path.
Program 5H7Afy...AW1j · receipt tx zwqNsA3k...cdEah67 · upgrade authority moved to the Squads vault.
The current Testnet proposal index 3 reached threshold approval, and execution remains blocked until the enforced 48-hour timelock release.
Vault CALHr...PqBv · signer approvals 4rcv9Eyf... and 3giWXof... · execution unlock 2026-05-27T02:25:39Z.
The PDAO governance mint is live on Solana Testnet with fixed supply and disabled mint authority.
Mint DFYvBdiv...37Bie · 1,000,000 PDAO · Token-2022 metadata and fixed-supply attestation are published.
DAO creation, proposal creation, voting lifecycle, execution, and treasury delta are verified on Solana Testnet.
Standard Testnet lifecycle packet with program, DAO, proposal, treasury, and transaction signatures.
Votes stay private during commit and become auditable only at the reveal stage.
Commit-reveal instructions, proposal-bound commitments, reveal checks, and runtime proof surfaces.
ZK proof records are bound to proposal payloads and reject substitution or stale interpretation.
V2 proof-policy snapshot tests and V3 governance-policy tests are passing on Testnet.
Confidential payout execution is gated by settlement evidence, policy snapshots, and payout caps.
V2/V3 settlement hardening tests cover SOL and token-asset branches plus negative recipient/mint/authority cases.
The UI does not stop at a toast; it exposes signatures, runtime status, RPC-backed freshness, and reviewer logs.
Runtime metrics, judge logs, RPCFast infrastructure plan, and generated runtime evidence packets.
Treasury routes expose SOL, USDC, AUDD, PUSD, and USDG metadata with governed receive context and stablecoin settlement lanes.
Treasury receive surface, AUDD merchant/treasury profiles, PUSD payroll/reward profiles, and stablecoin reviewer briefs for context.
A frontend developer can move from wallet UX to governance UI, RPC state, private payments, assignments, and quizzes.
Four lecture routes, toolkit, assignments, quizzes, and route sandboxes for wallet/governance/runtime/payment templates.
Choose the privacy posture that matches the operation
PrivateDAO is strongest when the privacy boundary is explicit. Pick the policy that fits the action, then open the matching route and proof path.
Best when judges, buyers, or community reviewers must follow every public hash while sensitive inputs stay abstracted.
Private payments are tied to explorer-visible Testnet receipts
PrivateDAO exposes the MagicBlock corridor as a live proof lane: the read-node verifies the corridor PDA and the deposit, private transfer, withdraw, settle, and execute signatures directly against Solana RPC. Private balance reads still require MagicBlock challenge/login, so sensitive state remains wallet-authorized.
One product surface, four corridors, one proof-backed operating path
The proof route should expose the full operating system behind the screenshots and transactions. Governance decides, intelligence explains, treasury prepares, confidential rails execute, payroll stays encrypted, and wallet-first execution keeps the final approval in the signer’s hands.
Captured Testnet execution evidence, not summary-only proof
This route exposes captured Testnet proposal and settlement signatures from indexed evidence and the dedicated V3 hardening path. It is the fastest way to review what PrivateDAO has already executed on Testnet, even when the visitor has not yet produced a fresh wallet-bound run in the current session.
This compresses the current evidence into one readable operating status before the raw governance and confidential transaction logs below.
Read-node judge activation
Judge backend readiness
Live Solana Testnet stream intake for proof freshness and operational telemetry
PrivateDAO now treats QuickNode as infrastructure, not a logo. Streams can send Testnet block or program-log data into a protected webhook, where the product converts noisy chain payloads into reviewer-safe intelligence: program matches, transaction health, compute usage, and evidence freshness before a signer executes.
Baseline proof and dedicated V3 proof packet are both reviewer-facing
On-chain proof anchors exposed in the Testnet evidence path
Multi-wallet Testnet rehearsal already captured and packaged
Grant, fund, gaming, and enterprise service packs remain part of the UI
Open the canonical Testnet flow that proves create → submit → private vote → execute treasury happened.
Open the additive hardening packet for Governance V3 and Settlement V3 after reviewing the baseline flow.
Open the integrations packet to verify ZK, REFHE, MagicBlock, and Fast RPC surfaces together.
Close the loop with audit packet, launch trust packet, and the release-gate packet so proof is not separated from deployment truth.
Proof center
Canonical Testnet create → vote → execute flow with public reviewer links.
Dedicated additive hardening proof for Governance V3 and Settlement V3.
PrivateDAO-specific matrix for what the ZK stack proves today, how it is verified, and what is still explicitly not claimed.
Deterministic scoring model for how ZK, REFHE, MagicBlock, and Fast RPC strengthen specific proposal patterns.
ZK, REFHE, MagicBlock, backend-indexed reads, and runtime evidence in one surface.
Reviewer and launch artifacts tied together with generated attestations.
Security rails
Layer-by-layer truth-aligned matrix for proofs, anchors, attestation, zk_enforced posture, and verifier boundaries.
Proposal-aware scoring model for privacy depth, enforcement depth, execution integrity, and reviewer confidence across ZK, REFHE, MagicBlock, and Fast RPC.
Token-supply quorum mode, policy snapshots, and reveal rebate vaults stay additive and versioned.
Payout caps, evidence aging, REFHE/MagicBlock requirements, and single-use settlement consumption semantics.
The app keeps launch states clear: live execution, external evidence, custody posture, and audit readiness are shown as separate proof surfaces.
Structured execution receipt for judges and operators
Every executed operation should resolve into one readable receipt surface: what was approved, what was executed, what stayed private, and what can be validated publicly.
Proof Matrix
Browser-run governance signatures and operation receipts are shown together so reviewers can move from wallet action to Testnet evidence without leaving the product.
Live operation receipts from storage
Receipt timeline is connecting to Supabase in the background.