Most DAOs expose everything: votes, salaries, treasury activity, and internal operations. PrivateDAO enables organizations to operate privately while remaining cryptographically verifiable on Solana.
A normal user can learn why public Solana operations expose sensitive work inLearn, connect a wallet, review the plain-English action, sign the exact request, then inspect when intent became visible, where payroll or treasury movement is proven, and how encrypted IKA / REFHE-style payment evidence stays linked to proof.
Judges can install the APK, open the live product routes, connect a Testnet wallet, and participate on-chain from mobile while proof, diagnostics, payroll, encrypted payments, and gaming reward paths stay one tap away.
A no-terminal Solana operating system for governance, payroll, payments, rewards, intelligence, and proof.
The same Testnet product is promoted as an Android APK path so a normal user can try the live stack immediately.
Privacy is not lack of transparency. PrivateDAO keeps sensitive processes private while making outcomes verifiable through commit-reveal governance, proof receipts, encrypted settlement metadata, and Solana Testnet evidence.
Covalent GoldRush, QVAC, SNS, Zerion policy, counterparty trust, and proposal context before signing.
Create DAO, create proposal, commit/reveal, finalize, execute, and open Solscan from the wallet.
Health scoring, rebalancing context, solvency posture, and agent policy lanes.
CSV preview, stablecoin selection, Umbra/Cloak receipts, and auditor views.
Guild hub, tournament rewards, inventory proposals, and private winner payouts.
Scoped viewing keys, date-windowed report flow, and dWallet-signed evidence.
Proof Matrix, ZK badges, viewing-key evidence, Solscan links, and runtime logs.
Integration docs, privacy SDK starter, read-node lanes, and builder entry points.
Read-node health, relayer evidence, QVAC runtime checks, and infrastructure proof.
Live operating status, treasury routes, indexed proposal context, and readiness gates.
PrivateDAO maps each sponsor rail to a concrete operating lane: intelligence before signing, private execution after governance, and proof after every action.
Prepare payroll, choose USDC/PUSD/AUDD context, generate privacy receipts, and keep audit context bounded.
Review Covalent GoldRush context, policy limits, and treasury routes before the wallet signs.
Create guilds, tournaments, and inventory proposals with governed reward settlement linked back to proof.
Pick any card and jump directly to its live route. This keeps the product simple for users and fast for reviewers.
Public DAO votes, payroll, rewards, and treasury moves expose intent too early. PrivateDAO shows the problem in plain language before asking anyone to sign.
Connect a Testnet wallet, create a DAO, submit a proposal, commit/reveal, finalize, and execute from the same operating shell.
Open Judge and Proof to inspect Testnet receipts, Solscan links, encrypted payment evidence, intelligence context, and runtime logs.
Start from Learn or Start, connect a Testnet wallet, and confirm the right account before any approval flow begins.
Open learnUse Intelligence to read policy, privacy mode, route quality, and execution risk before the signer sees a wallet prompt.
Open intelligenceUse Govern and Treasury to create the proposal, commit or reveal when needed, then approve the exact wallet action on Testnet.
Open governOpen Proof and Judge to inspect the signature, receipt, runtime logs, and the current blockchain continuity from the same product shell.
Open proofA concise product entry leads first; the deeper operating narrative remains available for reviewers, investors, and technical partners who want the full system context.
PrivateDAO is being built as reusable governance and treasury infrastructure for Solana. The value is not only one product instance. The value is a cleaner pattern for privacy, proof, treasury discipline, and operator trust that other teams can inspect and build on.
The strongest current use cases are easy to explain: private treasury approvals, grant and allocation committees, protocol operating councils, and payout workflows where privacy and execution discipline must stay together.
The roadmap is straightforward: simplify first-use verification, strengthen proof and telemetry continuity, complete custody and audit gates, and then publish the strongest possible production release candidate.
The ambition is straightforward: earn trust through real product quality, visible proof, and operational discipline, then turn ecosystem support into the technical and financial momentum that carries PrivateDAO from upgraded Testnet execution into durable mainnet infrastructure.
PrivateDAO is not just a UI shell. It combines privacy, local intelligence, responsive execution, reliable reads, and a current Anchor 1 program so a real Testnet action can move from wallet click to visible result without forcing the user to learn the architecture first.
REFHE supports the encrypted payout and settlement path so sensitive treasury actions do not depend on plain-text operating flow alone.
Zero-knowledge proof surfaces give judges, partners, and operators a verifiable trust layer without turning the main product route into a proof maze.
MagicBlock gives the product a faster action corridor for treasury and governance execution where slow, clumsy wallet UX would otherwise kill momentum.
Hosted reads and telemetry keep live state, signatures, proposal progress, and execution logs visible so users can tell what really happened after a wallet action.
QVAC frames proposal context, translation, OCR, and operational guidance as sovereign AI that can run near the user instead of centralizing sensitive DAO data.
The active Testnet program, ProgramData, deploy signature, web constants, Android config, and reviewer docs now point to the Anchor 1.0.1 migration evidence.
PrivateDAO uses each rail for a specific user-facing job. The public story should make that obvious: governance runs the DAO, gaming uses the same responsive decision corridor, confidential payout depends on privacy rails, and read-node telemetry keeps the result visible.
Used when the product needs to prepare private treasury movement without flattening the whole flow into plain-text operating steps.
Used when judges, partners, or operators need proof-linked trust without turning the normal user route into a cryptography lecture.
Used where wallet-first actions need a faster execution lane so DAO and game-linked decisions do not feel stuck behind slow runtime behavior.
Used to keep Testnet reads, proposal status, and action feedback visible after a wallet action instead of leaving the user guessing.
Used to turn Solana Testnet block and program-log flow into reviewer-safe counters, proof freshness, and backend health evidence.
Used where proposal summaries, compliance context, OCR, translation, and operating guidance should stay on-device or local-first before signing.
Used to keep the Solana program, IDL, web client constants, Android config, and reviewer evidence aligned around the upgraded Testnet deployment.
The current work is focused on turning PrivateDAO into infrastructure that can be reviewed, tested, funded, and then deployed with confidence. The strategy is to keep shipping real product proof while steadily converting each operational and protocol target into something stronger, clearer, and easier to trust.
The active Testnet program now runs from the Anchor 1.0.1 migration path, with matching web, Android, IDL, README, and reviewer evidence updates.
Local-first AI is framed around proposal context, compliance explanation, translation, OCR, and private operating assistance instead of a decorative chatbot.
Payroll, gaming, compliance, developers, RPC, command center, proof, and services routes now tell one Testnet-ready product story with explicit mainnet gates.
PrivateDAO is being built as governance and treasury infrastructure that can serve the Solana ecosystem broadly. We are working continuously to make it more capable, safer, and more valuable, and that mission moves faster with practical support: testing, technical review, integrations, operator discipline, and serious ecosystem distribution.
What support accelerates most is not vague enthusiasm. It is the kind of help that turns a strong Testnet product into stronger ecosystem infrastructure: wallet testing, security review, operational introductions, integrations, and funding that maps directly to visible milestones.
It is already a live Solana Testnet product with wallet-first governance, proof, trust, telemetry, and service rails. The current phase is final security hardening, broader device coverage, and release certification ahead of mainnet publication.
ZK, REFHE proof receipts, MagicBlock execution receipts, and read-node telemetry each map to a concrete product lane: privacy review, confidential payout proof receipts, responsive execution receipts, and reliable live reads. They are presented as service rails, not badge-only theory.
Runtime testing, wallet feedback, security review, infrastructure support, and aligned funding all help accelerate the path from strong Testnet operation into a hardened production release.
Each route starts with the user problem, shows the product answer, then opens the exact page where that operation is reviewed, signed, and verified.
See the full problem-to-solution narrative for private governance, treasury, payroll, gaming, and proof.
Open storyInspect current Testnet state for proposals, treasury actions, receipts, and execution logs.
Open live stateVerify signatures, receipts, ZK markers, viewing-key lanes, and public evidence after execution.
Open proofWe think that is broken. PrivateDAO enables organizations to operate privately while remaining cryptographically verifiable on Solana. Each layer below has a live route, a proof route, and when available a one-click API exercise.
Confidential decisions for Solana-native organizations.
Create or review DAO state, prepare proposals, commit/reveal private votes, inspect PDAO context, then verify the Testnet action.
Private budget and execution coordination before funds move.
Review treasury risk, preview Jupiter routing, keep encrypted payment metadata bounded, and route approved actions to proof.
Confidential payouts from organizations to contributors, operators, and task executors.
Generate a private settlement intent, preserve a receipt reference, and route the visitor to the matching proof lane.
Payroll integrity without exposing every contributor detail.
Use REFHE payroll proof, encrypted manifests, stablecoin payout context, and proof continuity for auditor-safe payroll review.
Decision support before governance or treasury authorization.
Summarize proposals, score risk, inspect wallet and treasury context, and detect abnormal governance or payment posture before signing.
Execution lineage for intent -> approval -> execution -> outcome.
Forward an approved operational event to the agent/growth rail while keeping the approval and outcome tied to verifiable receipts.
Private governance, payroll, and treasury operations on Solana. A visitor connects a Testnet wallet, reviews a governance, treasury, payment, or rewards action, authorizes from the wallet, and verifies the receipt onchain, through the API, or in reviewer documents.
Create a DAO, prepare a proposal, commit, reveal, execute, inspect PDAO governance-token context, and verify the coordination event on Solana Testnet.
Run encrypted payments, confidential payroll, stablecoin billing, Jupiter treasury routing, and receipt-backed settlement from one finance path.
Use the same governance and treasury rails for communities, prize pools, tournaments, rewards, and reviewer-visible competition flows.
Use QVAC, GoldRush/Covalent, SNS, Zerion, QuickNode status, and policy context before approving governance or treasury operations.
Open live API evidence, explorer signatures, ZK/Groth16 proof packets, Token-2022/PDAO context, and repository evidence from one route.
Ika, Encrypt, REFHE, ZK, MagicBlock, Umbra, Cloak, Torque, Zerion, and GoldRush are rails inside one coordination layer.
Start from a browser or APK, connect a Testnet wallet, sign, verify, and keep normal users away from terminal-only operations.
Explorer signatures, API receipts, ZK/Groth16 proof, Squads timelock, PDAO/Token-2022 context
Custody gates, remediation, audit packets, monitoring surfaces
Short lessons that open the matching live product route
Three-minute purpose, demo video, test paths, repo, proof, and route inventory
PrivateDAO should read from the first viewport as relief from a real pain: your votes, salaries, treasury activity, and internal operations are public by default. PrivateDAO makes the process private and the outcome verifiable through governance, payroll, treasury, payments, intelligence, and proof-linked execution lanes.
Fallback values are pinned to the published Testnet proof ledger while the live visitor API is unavailable.
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.