Operation receipts, runtime evidence, and trust packets in one premium verification surface
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.
Proof continuity stays explicit across governance, intelligence, execution, and receipt export lanes.
Submitted pitch link upgraded
This proof link now opens the strongest pitch packet and live demo path.
For competitions and grant reviewers that already received `/proof/?judge=1`, this page keeps the proof center intact and routes immediately to the current demo, pitch deck, reviewer packet, and application-ready traction metrics.
Privacy is useful only when the outcome remains verifiable.
The proof route explains explorer links, API receipts, ZK evidence, custody packets, and reviewer-visible audit trails in one place.
Evidence
On-chain signatures, receipts, ZK and custody docs
Audience
User, reviewer, auditor, operator
Rule
Private process, verifiable outcome
Route summary
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.
Public accountability. Private coordination. Verifiable execution.
PrivateDAO keeps coordination private while a decision is active, then publishes a simple report with the final outcome, execution status, proof hash, and audit trail.
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.
Live execution
A route actually prepares or submits a real runtime action on its current rail.
Health / status
A route checks vendor availability, relayer readiness, or runtime state without moving funds.
Intent receipt
A route records a review-safe intent or receipt so operators and judges can inspect continuity.
Full private settlement
A route reaches the actual payout rail and finishes the confidential transfer lifecycle.
Proof operating model
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.
Govern first, then use Proof as the inspection layer.
Hashes, explorer links, and logs should always be easy to follow.
The protected part of the workflow should stay private until the correct proof stage reveals only what must be reviewed.
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.
A direct website walkthrough: private governance, treasury intelligence, confidential payroll, gaming DAO flows, compliance, proof, QVAC guidance, and how the user moves without code or terminal work.
It is designed to work as the first-pass demo for users, judges, buyers, infrastructure partners, and YouTube review.
Use this asset as the fast submission reel from the product learning routes.
Operating journey
Proof-side operating journey
Freshness
34d old
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.
Connect
Scaling
Wallet evidence intake is active across desktop and mobile paths
Review
Verified
DAO bootstrap and proposal creation are captured in the governance evidence lane
Sign
Verified
Commit, reveal, finalize, and execute signatures are all captured in the wallet-driven lifecycle
Verify
Scaling
Verification continuity exists, but some evidence lanes are still being expanded
Next step
Expand wallet/device evidence
On-chain lifecycle is captured, and wallet/device evidence is attached through signed capture packets as each path is verified.
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.
Commit-reveal + ZK proof anchors
Fair voting without early vote leakage
What stays protected
The vote choice stays hidden during the commit stage. The chain records a commitment first, then the reveal later.
What the reviewer can still verify
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
What stays protected
Sensitive payout intent, recipient context, and settlement posture stay protected until the right review stage.
What the reviewer can still verify
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
What stays protected
Nothing secret is forced into plaintext just to make the UI understandable.
What the reviewer can still verify
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.
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.
ZK on-chain verification
Program deployed
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 clearest current competition path starts with MagicBlock private payments, then expands into Umbra, Cloak, Encrypt / IKA, and the intelligence and governance rails that explain why each execution lane exists. Reviewers should not have to infer the current track from older pages.
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.
7wallet-signed private reads through challenge/login
Operating map
Private processes. Verifiable outcomes.
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.
Each card links first to the live feature it describes, then to the closest proof packet or evidence surface for that exact lane. Use `/judge` when you need the full reviewer map; use this proof center when you need receipts and runtime evidence.
MagicBlock private payments
Current Frontier track lane: live corridor PDA check, finalized Testnet private payment receipts, challenge/login private reads, and wallet-signed execution continuity for judges.
Captured Testnet execution evidence, not summary-only proof
Freshness
34d old
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.
Operating journey
Judge-facing operating journey
Freshness
34d old
This compresses the current evidence into one readable operating status before the raw governance and confidential transaction logs below.
Connect
Scaling
Wallet evidence intake is active across desktop and mobile paths
Review
Verified
DAO bootstrap and proposal creation are captured in the governance evidence lane
Sign
Verified
Commit, reveal, finalize, and execute signatures are all captured in the wallet-driven lifecycle
Verify
Scaling
Verification continuity exists, but some evidence lanes are still being expanded
Next step
Expand wallet/device evidence
On-chain lifecycle is captured, and wallet/device evidence is attached through signed capture packets as each path is verified.
Judges should see that read-node is not a claim buried in docs: the indexed read path, telemetry packet, and deployment target are part of the proof story with an explicit backend gap.
Activation state
Indexed reads and same-domain backend serving are live for Testnet reviewer checks
Public product routes consume indexed read evidence and the hosted `api.privatedao.org` lane now serves health, relayer, QVAC, Covalent GoldRush, Torque, Zerion, and SNS checks.
Judges should see the same backend truth as operators: the host target, public health and metrics proofs, and the fallback policy stay explicit until `/api/v1` is truly live.
Readiness state
Host-ready lane defined; same-domain public serving is in final security hardening before release cutover
Use https://api.privatedao.org/api/v1 as the live read-node boundary. Same-domain `/api/v1` on the static frontend remains a future reverse-proxy consolidation step, not the current production-candidate API host.
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.
Authenticated webhook for Solana Testnet Programs + Logs or Block datasets. Do not point QuickNode at privatedao.org; use the api subdomain.
Payload posture
live stats
Large raw blocks become accepted-payload counters, program hits, compute usage, and proof freshness signals.
Security
env-token only
Secrets live in deployment environment variables; no stream token is committed to GitHub.
Decision use
data-to-intel
QuickNode feeds runtime telemetry, GoldRush adds wallet context, and QVAC turns both into signer guidance.
Supabase receipt continuity is browser-direct: confirmed operations write to governance_receipts, operation_receipts, and cloak_delivery_state without relying on static-export API routes. Realtime subscriptions refresh this proof surface when new rows land.
Live proofs
2
Baseline proof and dedicated V3 proof packet are both reviewer-facing
ZK anchors
3
On-chain proof anchors exposed in the Testnet evidence path
Wallets
50
Multi-wallet Testnet rehearsal already captured and packaged
Commercial rails
4
Grant, fund, gaming, and enterprise service packs remain part of the UI
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.
Browser-run governance signatures and operation receipts are shown together so reviewers can move from wallet action to Testnet evidence without leaving the product.
No local proof rows are available yet. Run a signed Testnet operation from Execute, then return here.
Supabase timeline
Live operation receipts from storage
Receipt timeline is connecting to Supabase in the background.
Showing 0 of 0 timeline receipts.
Receipt timeline is readying the live query without blocking the page.
Visual chain proof
Open the current Testnet lifecycle packet with real Solscan signatures, treasury deltas, and the agentic micropayment rail. This helps a non-technical reviewer verify that the product is already creating real on-chain activity before they inspect the raw explorer records.