PrivateDAO judge hub: demo, live tracks, and Testnet proof in one route
Start with the three-minute demo, then open a live track and verify the exact Testnet evidence. This page consolidates old judge links, proof routes, and partner submissions into one clean review path.
Your DAO votes, payroll, and treasury are public. They shouldn't be.
Most DAOs expose votes, salaries, treasury activity, and internal operations. PrivateDAO enables organizations to operate privately while remaining cryptographically verifiable on Solana. Start with the video, then open any track below to run the live route instead of reading disconnected pages.
Problem
Public payroll, public governance, public treasury, and public internal operations expose too much.
Solution
Private processes, wallet authorization, encrypted coordination, and verifiable outcomes are one guided flow.
Proof
REFHE, MagicBlock, ZK verifier, Token-2022, Squads, and backend JSON are Testnet-linked.
Generated from the repo render script with safe text margins and a music bed for judges who need the newest awards, backend rebuild, encryption, intelligence, and launch-gate story in one asset.
Run the track, then verify it
One clean operating path replaces the old scattered judging links
Old judge links remain alive, but this page is the canonical hub. Each card opens the product route first and the closest proof route second.
The judge route is backed by a live host / 46-page / 16-API execution check.
This is the operational gate used after each backend change. It verifies the public pages, provider endpoints, privacy matrix, Ika custody preparation, Torque delivery, GoldRush/Zerion intelligence, Umbra intent, Jupiter routing, QuickNode stream stats, MagicBlock receipts, and REFHE proof endpoint.
Load the wallet runtime only when the visitor is ready to claim
The page stays fast first. When a visitor starts, PrivateDAO loads the encrypted claim console, builds the AES-GCM packet locally, and anchors a digest through a Solana Testnet Memo transaction.
Reviewer path: every service claim resolves to a signed action, receipt, or live proof endpoint
Judges can open the claim console, prepare the selected service, sign the Testnet memo or verify the provider proof, and copy the public attestation without leaving the product flow.
Submission fast links
Four focused review links for the active partner lanes
These links are the cleanest submission surfaces for Jupiter, Umbra, Eitherway, and Encrypt / Ika. Each route starts at product value, then exposes the proof and execution boundary.
Fresh Testnet custody, ZK, timelock, and Token-2022 proof is visible before the archived judge logs.
This panel is the current reviewer entry point. It separates live Testnet evidence from older Devnet packets, and links every high-impact claim to a transaction, document, or proof surface.
Awards are shown here only as review context. The primary judge path remains the live product, Testnet proof, runtime status, and integration map across QVAC, Cloak, Umbra, MagicBlock, Covalent GoldRush, Jupiter, Zerion, Torque, Eitherway, Supabase, and the AWS read-node.
Regional recognition attached to proof, product clarity, and operating discipline.
3rd Place
Superteam UAE Frontier Hackathon
Frontier recognition for the integrated private-governance, payments, AI, and infrastructure surface.
Top 1%
Solana ecosystem signal
Credibility signal shown beside live Testnet proof rather than replacing technical verification.
Verification fast lane
Start with the smallest review surface that still proves the product is real
The fastest review path is operational, not theoretical. Inspect one governance cycle, one privacy explanation, and one treasury execution lane before opening the deeper packets. A normal reviewer should be able to understand what happened, run a comparable Testnet action, and verify the public hashes without reading internal engineering notes.
1. Proposal lifecycle from create to execute.
2. Vote, reveal, and execution signatures on Solana Testnet.
3. Agentic Treasury Micropayment Rail with real Testnet transfer rehearsal.
These are captured reference executions on Testnet. When you later run your own wallet flow, use this verification route and the proof center as the comparison point. The visible blockchain layer should reassure a normal reviewer that governance happened fairly, settlement happened for real, and the protected parts stayed private for the right reasons instead of disappearing into a black box.
The platform also exposes a compact map showing how recurring ecosystem requirements were translated into product capabilities across private governance, treasury rails, analytics, growth loops, wallet UX, and runtime infrastructure.
PrivateDAO monetizes without overstating mainnet maturity: open-source Testnet adoption builds trust, a $2,500 four-week pilot proves one buyer workflow, a $750/month managed plan supports recurring private operations, and sovereign deployments capture teams that need dedicated infrastructure and controls.
The judge path shows how large adjacent product types are completed inside one operating layer: governed intelligence, confidential treasury, payroll, payments, Android access, Testnet proof, and a buyer-readable pilot path in one product surface.
The current upgrade path is organized as ten product levels: first-minute understanding, wallet execution, Android parity, proof continuity, confidential operations, intelligence before signing, business conversion, security discipline, repository reviewability, and judging-grade narrative.
The most current reviewer lane starts with MagicBlock private payments, then branches into Umbra recipient privacy, Cloak settlement, and Encrypt / IKA operational privacy. Intelligence is not separate from these lanes; it prepares governance, treasury, payroll, and wallet-first action before any signature is requested.
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
Ecosystem message
Built as infrastructure, not a competition-only artifact
This product was built in the true spirit of Solana frontier innovation: identify real ecosystem pain points and engineer operational infrastructure that organizations, DAOs, and AI-native systems can use in production. The support of trusted reviewers, ecosystem catalysts, and foundational supporters accelerates this mission and strengthens confidence in the next generation of Solana builders.
Operating map
Private processes. Verifiable outcomes.
Reviewers need a clean system view: governance sets policy, intelligence prepares the decision, treasury selects the route, confidential rails execute private value movement, payroll remains encrypted, and wallet-first UX preserves user control at the final signing edge.
Each lane below opens the live feature and the closest proof packet directly, so a reviewer can validate the implementation without digging through the entire site.
MagicBlock private payments
Primary Frontier track lane with challenge/login auth, private balance boundary, and wallet-signed execution path.
What was approved: proposal policy and governance state
What was analyzed: intelligence and runtime context
What was executed: on-chain signatures and receipt lanes
What stayed private: recipient and payout sensitivity
What stayed verifiable: hashes, logs, and proof artifacts
Why each rail exists: governance, privacy, market, proof
What the product surface unlocks underneath
This view is for reviewers who want the shortest bridge from a visible route into the underlying execution core, proof path, learning path, and productized service lane.
Private governance execution
A normal user can create a DAO, submit a proposal, vote, and execute from one wallet-first flow while the product keeps proof and treasury discipline attached.
Visible surface
Start from onboarding
Commercial shape
The base service lane for grant committees, enterprise DAOs, fund governance, and internal operating councils.
Execution core
DAO lifecycle orchestrationproposal registry and policy snapshotswallet-signed execution pathruntime-linked proof visibility
Treasury motions, payout requests, and sensitive execution paths stay private where needed, yet still produce reviewer-safe evidence and operator-readable state.
Visible surface
Open security lane
Commercial shape
This is the premium confidentiality lane for payroll, grants, vendor payouts, and high-trust treasury operations.
Execution core
treasury receive routingsettlement receipt and closure surfacesconfidence engine and policy-bound reviewreviewer-visible payout evidence
Stablecoins are not shown as token badges; they are activated as governed settlement rails for merchant billing, treasury reserves, payroll, and reward distribution.
Visible surface
Open treasury receive surface
Commercial shape
This lane becomes merchant settlement, programmable finance, payroll, grants, and stablecoin-native treasury services.
Execution core
AUDD merchant and treasury settlement profilesPUSD payroll and gaming reward profileswallet-signed stablecoin transfer constructionmemo-coded billing rehearsal and reviewer context
Automation is turned into a bounded treasury assistant instead of an unscoped bot, so teams can automate repetitive payouts and rebalances without surrendering wallet control.
Visible surface
Open services rail
Commercial shape
The commercial lane is treasury operations automation for teams that need bounded execution, not god-mode agents.
The infrastructure layer is visible as product value: faster reads, clearer logs, analytics, reviewer packets, and operator confidence after every signed action.
Visible surface
Open services
Commercial shape
This becomes hosted read API, DAO-specific RPC, infrastructure support, and analytics-grade governance operations.
Execution core
diagnostics and live state surfacesreviewer telemetry packethosted read proof and API-facing opsindexed proposal and runtime freshness snapshots
The platform can onboard, educate, activate, and measure users inside the same product instead of outsourcing product understanding to offsite docs and ad-hoc community support.
Visible surface
Open learn route
Commercial shape
This supports community activation, contributor onboarding, operator enablement, and measurable growth loops for live governance products.
Execution core
lecture-to-route learning loopcustom_events for activation and retentionassignment and quiz completion surfacesroute-linked onboarding and adoption tooling
Choose the narrow review lane that fits the scenario instead of opening every internal detail at once
The reviewer does not need the full internal operating view every time. Pick the scenario, open the matching packet, and inspect only the hashes, custody state, and proof needed for that review window.
Auditor evidence
Open custody proof and reviewer-grade documents when the reviewer needs authority and control-chain evidence.
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.
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.
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.
Read the technology in plain language, then open the live route and the on-chain proof yourself
This guide is intentionally simple. It explains what each production lane does for a real user, which PrivateDAO route lets you try it, and which Testnet transaction lets you verify that the chain recorded the action.
with ZK + commit-reveal
Keep voting fair before execution
The governance flow protects vote intent during the sensitive stage, then exposes the public execution trail when the DAO action is ready to verify.
Users see fresh state, signatures, logs, and action status quickly enough to trust what happened instead of guessing from a wallet popup or stale status.
Approved DAO policy can drive repeated on-chain settlement actions, so the judge can inspect a real batch settlement trail instead of a single isolated transfer.
Captured Testnet execution evidence, not summary-only proof
Freshness
6d 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
6d 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.