Private governance, confidential treasury operations, and audit-grade runtime evidence for Solana organizations.
Regional 1st Place recognition, March 2026.
PrivateDAO engineering already carries a real first-place regional signal. That matters here because this repo is built the same way: live protocol code, live Testnet execution, explicit trust boundaries, and machine-checked reviewer evidence. See docs/awards.md.
Core development, wallet hardening, localization, and service packaging run in continuous release cycles.
If a route is being refreshed:
- retry in a few minutes
- check
https://privatedao.org/trust/ - check
https://privatedao.org/community/
PrivateDAO is live on Solana Testnet: the preserved Anchor program is deployed, the standard governance lifecycle has executed end to end, and treasury movement is verified by public hashes.
- Track-by-track delivery board and submission artifacts:
submissions-new/TRACK_EXECUTION_BOARD.md - Submission index and publish log:
submissions-new/README.md - Security baseline snapshot (current gate findings and mitigations):
docs/security-baseline-2026-04-24.md
PrivateDAO is a Solana governance and treasury product for organizations that need privacy without losing operational discipline.
It combines:
- Private voting: commit-reveal governance with proposal-bound commitments.
- Confidential treasury operations: payroll, bonus, and payout flows with aggregate on-chain settlement state.
- Execution safety: timelocks, veto and cancel boundaries, duplicate-execution resistance, and strict treasury account validation.
- Evidence and reviewability: Devnet rehearsals, Testnet lifecycle proof, ZK proof anchors, runtime packets, manifests, and generated audit surfaces.
- Operational packaging: Realms migration, hosted read/API packaging, trust exports, pilot material, and operator docs.
PrivateDAO is being built as public-good governance and treasury infrastructure for Solana.
The goal is not only to ship one strong product surface. The goal is to make advanced governance, privacy, telemetry, and treasury discipline easier for the ecosystem to adopt, inspect, and build on.
That matters because the same core system can serve:
- grant and allocation committees
- treasury and payout governance
- protocol operating councils
- security-sensitive decisions
- contributor, vendor, and payroll-style payout workflows
The roadmap is intentionally simple and fundable:
- make the wallet-first Testnet flow effortless for first-time visitors
- keep proof, telemetry, custody, and diagnostics attached to the same product corridor
- strengthen audit, monitoring, real-device wallet coverage, and settlement publication
- close the remaining production gates and ship the strongest possible release candidate
PrivateDAO is already a live Solana Testnet governance infrastructure product, not a concept deck:
- Anchor program deployed on Solana Testnet with the same canonical program id
- Devnet rehearsal history preserved as the transition evidence base
- Wallet-connected frontend
- Operational routes for onboarding, command, dashboard, proof, diagnostics, and services
- PDAO governance token surface
- Web wallet DAO bootstrap on Testnet
- Web wallet proposal submit on Testnet
- Repo-native and device-native proof paths for the broader governance lifecycle
- Confidential payout paths with
REFHEandMagicBlockintegration surfaces Strict V2hardening for proof, settlement, cancellation, and policy snapshotsGovernance Hardening V3for token-supply quorum snapshots and dedicated reveal rebate vaultsSettlement Hardening V3for payout caps, evidence-aging windows, and explicit REFHE/MagicBlock execution requirements- Backend read node and RPC Fast-oriented evidence path
- Testnet billing rehearsal route with wallet-signed on-chain service charge proof
- Standard Testnet lifecycle rehearsal with create DAO, proposal, commit, reveal, finalize, execute, and treasury delta verification
- Reviewer-facing runtime, security, and launch packets
The public product UI is intentionally responsible for:
- Connect Wallet
- Create DAO on Testnet from the connected web wallet
- Create Proposal on Testnet from the connected web wallet after live DAO bootstrap
- Commit Vote
- Reveal Vote
- Finalize Proposal
- Execute Proposal
- View Logs
- Diagnostics
The public repo and CLI remain available for:
- Advanced debugging
- Batch operations
- Emergency recovery
- Migration tools
- Stress tests
This keeps the buyer-facing product clean while preserving engineering and protocol discipline in the repo.
The non-terminal path is now explicit:
- Open
https://privatedao.org/start/. - Connect a Testnet wallet. Solflare, Phantom, Glow, Backpack, and Wallet Standard wallets are surfaced from the browser product.
- Continue to
https://privatedao.org/govern/and run the flow: create DAO, create proposal, commit, reveal, finalize, and execute. - Open
https://privatedao.org/proof/?judge=1anddocs/testnet-lifecycle-rehearsal-2026-04-19.mdto verify the public signatures, accounts, treasury delta, and explorer links. - Use
https://privatedao.org/learn/for the lecture, code, quiz, and assignment corridor that explains what the user just executed.
Repo scripts remain the reproducible reviewer path, but the ordinary product path is browser-first: click, sign, run, verify.
Current web/runtime boundary:
Create DAOnow has a live wallet-first Testnet bootstrap path in the web action workbench.Create Proposalnow has a live wallet-first Testnet submit path in the same workbench once a live DAO bootstrap has already established the DAO lane, including the current liveSendSolandSendTokentreasury-motion lanes.Commit Vote,Reveal Vote, andFinalize Proposalnow use the same live wallet-first workbench lane once a real DAO and proposal already exist in session state.Execute Proposalnow also has a live wallet-first path for standard proposals and the current liveSendSolandSendTokentreasury-motion lanes.- Repo-script lifecycle proof, browser-wallet execution proof, Android Solflare mobile capture, and standard Testnet lifecycle proof are now recorded as separate evidence packets.
CustomCPIstill requires the richer payout path; the current live web builder now carries the supported treasury transfer variants, but it does not claim arbitrary treasury action coverage.
The rule is strict:
- If a normal user needs it, it belongs in the UI.
- If it is for protocol maintenance, incident handling, migrations, or engineering-only control, it belongs in the public repo and CLI.
PrivateDAO is actively being advanced as a live Testnet product under continuous community review.
The public message stays simple:
- one coherent governance product
- private and confidential treasury operations
- clear runtime evidence and trust surfaces
- stronger operator and reviewer readability with each shipping tranche
PrivateDAO is already strong enough for Testnet evaluation, judge review, and pilot packaging, and the current execution strategy is designed to convert that foundation into mainnet-grade readiness with the right support and closure evidence:
| Stage | Current status | Evidence |
|---|---|---|
| Product and protocol | Live on Solana Testnet with browser product surfaces and reviewer proof | Live frontend, Anchor program, PDAO governance mint, commit-reveal lifecycle, confidential payout flows, Strict V2 hardening. |
| Reviewer evidence | Implemented and generated | 50-wallet Devnet rehearsal, standard Testnet lifecycle proof, Android Solflare capture, ZK anchors, operational evidence, audit packet, cryptographic manifest, and npm run verify:all. |
| Launch operations | Repo-defined and ready for closure | Multisig intake, authority transfer runbook, launch ops checklist, monitoring rules, wallet E2E plan. |
| Production custody | Structured for execution with recorded evidence next | 2-of-3 multisig, 48+ hour timelock, authority transfer signatures, signer backups, and post-transfer authority readouts. |
| Mainnet real funds | Final production gate | External audit, live monitoring, real-device captures, source-verifiable MagicBlock/REFHE receipts, and final cutover ceremony. |
Operational launch docs:
docs/mainnet-blockers.mddocs/multisig-setup-intake.mddocs/authority-transfer-runbook.mddocs/launch-ops-checklist.mddocs/monitoring-alert-rules.mddocs/wallet-e2e-test-plan.mddocs/launch-trust-packet.generated.mddocs/final-closure-workplan-2026-04-19.mddocs/track-funding-integration-closure-plan-2026-04-19.mddocs/production-custody-ceremony.mddocs/external-audit-engagement.mddocs/pilot-onboarding-playbook.mddocs/browser-automation-audit.mddocs/security-audit-remediation-2026-04-08.md
The README should stay aligned with this rule: implemented surfaces are described as implemented; external launch steps are described as pending until real evidence is recorded.
The canonical custody source of truth is:
docs/multisig-setup-intake.jsondocs/custody-observed-readouts.jsondocs/canonical-custody-proof.generated.mddocs/custody-proof-reviewer-packet.generated.mddocs/production-custody-ceremony.mddocs/authority-transfer-runbook.mddocs/mainnet-blockers.md
Strict operator ingestion path:
- Build the packet in
https://privatedao.org/custody/ - Save it locally as
docs/custody-evidence-intake.json - Run
npm run apply:custody-evidence-intake
Current official custody state from the canonical intake:
- status:
pending-external - production mainnet claim allowed:
false - network:
mainnet-beta - threshold target:
2-of-3 - signer public keys recorded:
0/3 - multisig implementation:
pending-selection - multisig address:
pending - timelock configuration evidence:
pending - rehearsal signature:
pending - upgrade / DAO / treasury transfer signatures:
pending - post-transfer authority readouts:
pending - current deployed authority readout observed on
devnet:4Mm5YTRbJuyA8NcWM85wTnx6ZQMXNph2DSnzCCKLhsMD - target-network program readout on
mainnet-beta:not found
Live proof surface:
https://privatedao.org/custody/https://privatedao.org/documents/https://privatedao.org/documents/canonical-custody-proof/https://privatedao.org/documents/custody-proof-reviewer-packet/https://privatedao.org/documents/launch-trust-packet/https://privatedao.org/documents/mainnet-blockers/
This is intentional: the product now exposes the exact custody proof shape and the live operating milestones around it, while the transfer ceremony keeps moving toward a reviewer-ready closeout with real addresses, signatures, explorer links, and readouts. The goal is not to overstate readiness. The goal is to keep making the system stronger, more credible, and more defensible with every serious execution tranche.
The launch boundary is now surfaced in-product through https://privatedao.org/custody/, where multisig creation, authority transfer, and evidence requirements are shown as a live operating workflow rather than a hidden note.
PrivateDAO is presented publicly as one coherent product with multiple reviewer-visible lanes.
| Reviewer lane | Live route | Strongest visible fit |
|---|---|---|
| Primary product lane | https://privatedao.org/learn/ | Product shell, trust surfaces, proof continuity, and buyer path |
| Confidential operations lane | https://privatedao.org/security/ | Commit-reveal governance, privacy-aware treasury motion, and settlement posture |
| Runtime and infrastructure lane | https://privatedao.org/analytics/ | Hosted reads, diagnostics, API packaging, and runtime evidence |
The operating rule stays strict:
- one product thesis
- multiple reviewer corridors under the same product narrative
- no contradiction between site, README, deck, product walkthrough, or proof
Beyond the main product route, PrivateDAO is also packaged through adjacent reviewer and buyer corridors that strengthen the same commercial product thesis instead of fragmenting it.
| Corridor | Current strongest route | What it proves now |
|---|---|---|
| Startup capital corridor | https://privatedao.org/start/ -> https://privatedao.org/story/ -> https://privatedao.org/services/ |
Startup-quality product shell, buyer corridor, and reviewer-safe trust packaging |
| Regional grant corridor | https://privatedao.org/awards/ -> https://privatedao.org/learn/ |
Ecosystem credibility, product maturity, and proof continuity |
| Data and telemetry corridor | https://privatedao.org/diagnostics/ -> https://privatedao.org/analytics/ |
Runtime evidence, indexed proposal state, and hosted-read credibility |
| Confidential payout corridor | https://privatedao.org/security/ -> https://privatedao.org/services/ -> https://privatedao.org/custody/ |
Private treasury approvals, encrypted operations framing, and custody-aware payout discipline |
| Audit and hardening corridor | https://privatedao.org/documents/canonical-custody-proof/ -> https://privatedao.org/diagnostics/ |
Canonical custody truth, authority hardening, and incident-readiness posture |
Canonical strategic reference:
docs/strategic-opportunity-readiness-2026.mddocs/reviewer-telemetry-packet.generated.mddocs/ecosystem-focus-alignment.generated.md
The current ecosystem-facing fit is documented in:
This packet keeps the case disciplined across:
- decentralisation
- censorship resistance
- DAO tooling
- education
- developer tooling
- payments
- selective cause-driven fit
The rule remains strict: only corridors already visible in the live product are presented as shipped, and every area keeps an explicit next gap instead of inflated claims.
These are the public-facing routes reviewers, users, and buyers should see first:
| Surface | Link |
|---|---|
| Story video route | https://privatedao.org/story/ |
| Weekly / public YouTube | https://www.youtube.com/@privatedao |
| Official Discord | https://discord.gg/PbM8BC2A |
| Public project profile | https://arena.colosseum.org/projects/explore/praivatedao |
| Guided product flow | docs/product-guided-flow.md |
| Live proof V3 | docs/test-wallet-live-proof-v3.generated.md |
| Domain mirror plan | docs/domain-mirror.md |
.xyz mirror checklist |
docs/xyz-mirror-cutover-checklist.md |
| Audit packet | docs/audit-packet.generated.md |
| Operational evidence | docs/operational-evidence.generated.md |
| Integration evidence | docs/integration-evidence.generated.md |
| Reviewer telemetry packet | docs/reviewer-telemetry-packet.generated.md |
| Mainnet blockers | docs/mainnet-blockers.md |
| Trust package | docs/trust-package.md |
| Service catalog | docs/service-catalog.md |
| Investor / reviewer pitch deck | docs/investor-pitch-deck.md |
flowchart LR
User["Wallet user / DAO operator"] --> Frontend["Live web app - apps/web static export at repo root"]
User --> Android["Android native path - Solana MWA"]
Frontend --> Wallet["Wallet signing - Phantom / Solflare"]
Android --> Wallet
Wallet --> Program["PrivateDAO Anchor program - Solana Testnet"]
Program --> DAO["DAO PDA"]
Program --> Proposal["Proposal PDA"]
Program --> Treasury["Treasury PDA"]
Program --> VoteRecord["VoteRecord PDA"]
Program --> StrictV2["Strict V2 companion accounts - policy, proof, settlement, consumption"]
Frontend --> ReadNode["Read-only backend node - pooled RPC and metrics"]
ReadNode --> RPC["Solana RPC / RPC Fast path"]
Program --> Evidence["Runtime evidence - ZK anchors, manifests, reports"]
Evidence --> Reviewers["Judges / auditors / operators"]
flowchart LR
Start["Start"] --> DaoCreated["DAO created"]
DaoCreated --> ProposalCreated["Proposal created"]
ProposalCreated --> Commit["Commit vote hash"]
Commit --> Reveal["Reveal vote and salt"]
Reveal --> Finalize["Finalize after reveal window"]
Finalize --> Timelock["Timelock for passed proposal"]
Timelock --> Execute["Execute after delay"]
Timelock --> Vetoed["Veto during timelock"]
ProposalCreated --> Cancelled["Early cancel / V2 safe cancel"]
Execute --> Done["Done"]
Vetoed --> Done
Cancelled --> Done
The frontend can expose public treasury intake rails for:
SOLUSDCUSDG
These are configured through public environment variables only:
NEXT_PUBLIC_TREASURY_RECEIVE_ADDRESSNEXT_PUBLIC_TREASURY_SOL_RECEIVE_ADDRESSNEXT_PUBLIC_TREASURY_USDC_RECEIVE_ADDRESSNEXT_PUBLIC_TREASURY_USDG_RECEIVE_ADDRESSNEXT_PUBLIC_TREASURY_USDC_MINTNEXT_PUBLIC_TREASURY_USDG_MINTNEXT_PUBLIC_TREASURY_NETWORK
Use only public receive addresses here. Do not place signer keypairs, seed phrases, or treasury secrets in the frontend or this repository.
/proof now includes a live operation timeline backed by Supabase table public.operation_receipts.
- Set public env values in
.env.local:NEXT_PUBLIC_SUPABASE_URLNEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY
- Open Supabase SQL editor and run:
- Run the normal flow in
/govern(create, commit, reveal, finalize, execute) or/executebilling rehearsal, then open/proofto confirm receipt rows.
The timeline remains non-blocking: on-chain actions still run even if Supabase is not configured, and recent browser receipts are shown as local fallback.
| Layer | What exists now | Key references |
|---|---|---|
| Governance core | DAO creation, proposal creation, commit, reveal, finalize, execute, veto, cancel, delegation, keeper reveal. | programs/private-dao/src/lib.rs, tests/private-dao.ts |
| Treasury execution | SOL and Token-2022/SPL treasury paths with recipient, mint, owner, and duplicate-execution checks. | docs/security-review.md, docs/failure-modes.md |
| Confidential payouts | Proposal-bound payroll and bonus plans with encrypted manifests and aggregate settlement. | docs/confidential-payments.md, docs/confidential-payroll-flow.md |
| Confidential Treasury Command Center | Live guided UI path that turns Create -> Commit -> Reveal -> Execute into one product flow, then explains proposal-by-proposal whether ZK, REFHE, MagicBlock, and backend-indexed RPC are active, optional, or not required. The builder now includes smart presets for standard treasury grants, confidential payroll, confidential bonus, and private token distribution. |
apps/web, docs/frontier-guided-flow.md |
| Checkout-like onboarding rail | The proposals page now starts with a storefront-style onboarding rail that walks normal users through product pack selection, DAO bootstrap, treasury funding, proposal launch, and private vote/execute flow before they reach the lower-level consoles. The storefront now personalizes hero CTAs and compare cards based on the selected operating pack. | apps/web |
| Storefront and service entry | The homepage now exposes product packs, Realms migration as a first-class entry, and a service catalog for hosted API, review exports, onboarding, and pilot support without pretending a self-serve SaaS checkout already exists. | apps/web, docs/service-catalog.md, docs/migration-story.md |
| Commercial buyer surface | The homepage now also frames the commercial buying path directly in-product: pilot package, hosted read API + ops, confidential operations premium, and enterprise governance retainer, each linked to the exact pricing, SLA, trust, and onboarding documents behind it. | apps/web, docs/pricing-model.md, docs/pilot-program.md, docs/service-level-agreement.md |
| Buyer journey narrative | The homepage now explains who should buy PrivateDAO, why it exists beyond Realms or Squads alone, what happens in the first 30 days of a pilot, and what is live now versus still pending-external for real-funds launch. | apps/web, docs/trust-package.md, docs/mainnet-blockers.md, docs/pilot-program.md |
| Conversion-ready pilot rail | The homepage now includes a commercial checkout rail for weeks 1-4 of a pilot plus a Request Pilot Packet action that copies the exact buyer-facing packet from the current repo truth surface. |
apps/web, docs/pilot-program.md, docs/pricing-model.md, docs/trust-package.md |
| Product-proof hero strip | The hero now includes quick-switches for judge, buyer, and operator views plus a prominent live-success proof strip that surfaces Testnet lifecycle proof, V3 hardening packets, reviewer packets, and the explicit mainnet boundary from the first screen. | apps/web, docs/testnet-lifecycle-rehearsal-2026-04-19.md, docs/test-wallet-live-proof-v3.generated.md, docs/operational-evidence.generated.md, docs/mainnet-blockers.md |
| Persona-adaptive landing surface | The hero now shifts between buyer, judge, and operator narratives without changing the underlying proof links, and the proposals page now carries a sticky pack summary that turns the active preset into a clear operator and buyer brief. | apps/web, docs/grant-committee-pack.md, docs/fund-governance-pack.md, docs/enterprise-dao-pack.md |
| Commercial decision surface | The proposals page now includes a dedicated conversion layer: compare plans, open the API and operations surface, inspect the live-versus-pending boundary, and copy a buyer-ready service packet directly from the active pack. | apps/web, docs/service-catalog.md, docs/trust-package.md, docs/mainnet-blockers.md |
| Proposal-aware commercial guidance | The selected proposal panel now adapts its buyer, operator, judge, and launch-boundary guidance to the live proposal itself, including pack inference, proposal packet copy, and proof-bound next steps tied to the actual on-chain phase. | apps/web, docs/trust-package.md, docs/mainnet-blockers.md, docs/test-wallet-live-proof.generated.md |
| Realms migration storefront | The Realms migration page now includes organization-specific migration packs, live command generation, and next-step guidance so operators can move from migration intent to a concrete PrivateDAO bootstrap path faster. | apps/web, docs/migration-story.md, docs/grant-committee-pack.md, docs/fund-governance-pack.md, docs/enterprise-dao-pack.md |
| REFHE | Proposal-bound encrypted evaluation envelope with settlement gate and explicit trust model. | docs/refhe-protocol.md, docs/refhe-security-model.md |
| MagicBlock | Private-payment corridor support for confidential token payout flows, with runtime capture/evidence docs. | docs/magicblock/private-payments.md, docs/magicblock/runtime-evidence.md |
| Integration evidence gate | One machine-checked package that binds ZK anchors, MagicBlock settlement, REFHE settlement, and backend-indexed RPC state into a single Devnet-verified review surface. | docs/frontier-integrations.generated.md, docs/read-node/ops.generated.md |
| ZK layer | Groth16 companion proofs, on-chain proof anchors, ZK registry, and zk_enforced readiness documentation. |
docs/zk-proof-registry.json, docs/zk-layer.md |
| Strict V2 hardening | Additive companion accounts for DAO security policy, proof verification, settlement evidence, consumption, cancellation safety, and voter-weight scope. | docs/security-hardening-v2.md, docs/protocol-spec.md |
| Governance Hardening V3 | Additive governance-policy snapshots, token-supply participation quorum, dedicated reveal rebate vaults, and V3 finalize/reveal paths that do not reinterpret legacy proposals. | docs/governance-hardening-v3.md, docs/test-wallet-live-proof-v3.generated.md, programs/private-dao/src/lib.rs |
| Settlement Hardening V3 | Additive settlement-policy snapshots, payout caps, minimum evidence age, and optional REFHE/MagicBlock execution requirements for confidential payout execution. | docs/settlement-hardening-v3.md, docs/test-wallet-live-proof-v3.generated.md, programs/private-dao/src/lib.rs |
| Read node | Read-only backend node for proposal/DAO inspection, ops snapshots, pooled RPC reads, and same-domain deployment path. | docs/read-node/indexer.md, docs/read-node/ops.generated.md |
| Mobile surface | Android-native path with Kotlin, Jetpack Compose, and Solana Mobile Wallet Adapter. | apps/android-native/, docs/android-native.md |
| Review automation | Generated audit packet, runtime evidence, operational evidence, cryptographic manifest, and release drill artifacts. | docs/audit-packet.generated.md, docs/cryptographic-manifest.generated.json |
The preserved reviewer evidence package includes the completed Devnet rehearsal with persistent wallets, adversarial checks, ZK artifacts, and generated runtime evidence. The current public operating path is Solana Testnet.
| Metric | Value |
|---|---|
| Network | Devnet |
| Wallets | 50 |
| Total attempts | 212 |
| Successful attempts | 180 |
| Expected security rejections | 32 |
| ZK proof artifacts | 7 |
| On-chain ZK proof anchors | 3 |
| Canonical reviewer gate | npm run verify:all |
Primary artifacts:
docs/load-test-report.mddocs/operational-evidence.generated.mddocs/runtime-evidence.generated.mddocs/devnet-resilience-report.mddocs/devnet-race-report.mddocs/zk-proof-registry.jsondocs/performance-metrics.json
The current Testnet packet proves the standard governance and treasury lifecycle on Solana Testnet with the preserved canonical program id.
| Metric | Value |
|---|---|
| Network | Testnet |
| Program | 5AhUsbQ4mJ8Xh7QJEomuS85qGgmK9iNvFqzF669Y7Psx |
| ProgramData | CeggEn3sNVbiuJHLKDaCPMH4uLczu1Dr3ZGKKcaKBqeN |
| IDL account | BKV4bWESswfKteav82yZWPdN6wCd172UryGkaN8mxfGR |
| DAO | HZkVYf1bizstbEonRr7AS8HRQdR6sAgTB5Av9EuJFvGa |
| Proposal | HXMsqWWKosqgTM1PnPTeHrzq1i5ZygtrKZ5kjozH3T4A |
| Result | Passed and executed |
| Treasury delta | 5,000,000 lamports |
| Execute transaction | 5rLufq61qfdtgcaWtorYCy7CzDuxsYt13McxBi5MwgmHEKVmmdsxXqA6FMzz9ZxzQJGrdXj3iG6CbJpS59uMmFeD |
Primary artifacts:
docs/testnet-lifecycle-rehearsal-2026-04-19.mddocs/testnet-lifecycle-rehearsal-2026-04-19.jsondocs/testnet-migration-report-2026-04-18.md
This section intentionally keeps the reviewer contract visible. The README is concise, but every core review surface stays one click away.
PrivateDAO is explicit about the difference between implemented enforcement, attestation, and future cryptographic upgrades.
- Commitments bind
vote_byte || salt_32 || proposal_pubkey_32 || voter_pubkey_32. - Vote records and delegation markers are proposal-bound PDAs to prevent cross-proposal replay.
- Treasury execution is timelocked and checks recipient, mint, owner, source/destination, and executed-state invariants.
- Strict V2 paths are additive and do not reorder old account layouts or remove legacy instructions.
- Settlement evidence is proposal/payout-bound and single-use under the V2 model.
- ZK proof artifacts are generated and verified off-chain today, with representative proof anchors recorded on-chain for the preserved Devnet evidence path and current Testnet review path.
- Full mainnet production still requires external audit, production authority hardening, monitoring, and stronger source-verifiable receipt paths for external systems.
Important security docs:
docs/security-review.mddocs/threat-model.mddocs/security-hardening-v2.mddocs/security-architecture.mddocs/replay-analysis.mddocs/zk-assumption-matrix.mddocs/mainnet-readiness.generated.md
PrivateDAO preserves the Devnet PDAO governance-token evidence for reviewer continuity, while the governance program now has a preserved-id Testnet deployment and standard lifecycle proof.
| Field | Value |
|---|---|
| Token | PDAO |
| Network | Devnet |
| Utility | Governance voting token |
| Platform | DeAura |
| Mint | AZUkprJDfJPgAp7L4z3TpCV3KHqLiA8RjHAVhK9HCvDt |
| Program | Token-2022 |
| Initial supply | 1,000,000 PDAO |
The canonical PrivateDAO governance program id is:
Live devnet program: 5AhUsbQ4mJ8Xh7QJEomuS85qGgmK9iNvFqzF669Y7Psx
Live Testnet program: 5AhUsbQ4mJ8Xh7QJEomuS85qGgmK9iNvFqzF669Y7Psx
5AhUsbQ4mJ8Xh7QJEomuS85qGgmK9iNvFqzF669Y7Psx
The Token-2022 program id belongs to the governance token mint surface; it is not a second PrivateDAO governance program.
programs/private-dao/src/lib.rs Anchor program and account model
apps/web/ Next.js product source for the published web surface
index.html Published GitHub Pages entrypoint from apps/web export
apps/android-native/ Android native Solana MWA app
scripts/ Devnet, operator, verifier, and evidence automation
tests/private-dao.ts Core governance/security test coverage
tests/full-flow-test.ts End-to-end lifecycle and treasury tests
sdk/src/index.ts Commitment and client helpers
docs/ Reviewer docs, generated evidence, archive UI, and raw-reference assets
zk/ Groth16 companion proof circuits and setup artifacts
For navigation inside the large docs and scripts surfaces:
If you only have a few minutes:
- Open the live product: https://privatedao.org/
- Open judge mode: https://privatedao.org/proof/?judge=1
- Read
docs/reviewer-fast-path.md - Read
docs/security-hardening-v2.md - Read
docs/testnet-lifecycle-rehearsal-2026-04-19.md - Read
docs/operational-evidence.generated.md - Read
docs/technical-verification-status-2026.md - Inspect the program:
programs/private-dao/src/lib.rs - Run the unified gate:
npm run verify:all
PrivateDAO is being developed as long-horizon governance and treasury infrastructure for the Solana ecosystem rather than a closed showcase surface.
The strategy is straightforward:
- ship real wallet-first governance and treasury flows on Testnet
- keep proof, trust, and technical review surfaces public
- convert each production milestone into evidenced closure
- grow the product into infrastructure the ecosystem can actually use and build on
We build for privacy, operational clarity, and long-horizon trust. We keep the work visible, keep the product verifiable, and work with the conviction that PrivateDAO can become stronger, more useful, and more trusted over time as the ecosystem turns support into durable technical, financial, and human momentum.
The most useful forms of community support are:
- runtime testing and wallet feedback on Testnet
- reviewer scrutiny on trust, proof, and operating-readiness surfaces
- protocol, frontend, and infrastructure contributions
- introductions to operators, grants, and security reviewers who can help accelerate production readiness
We invite the community to support this work with real testing, review, introductions, integrations, and amplification. With that kind of support, the product mission becomes practical: PrivateDAO can mature from live Testnet proof into shared ecosystem infrastructure with higher trust, stronger operations, broader reach, and the staying power needed to keep building for the ecosystem over the long term.
Start from the live product at https://privatedao.org/, then use the trust and documents routes to inspect the current evidence boundary directly.
Prerequisites:
- Rust stable
- Solana CLI
- Anchor CLI
0.32.1 - Node.js 20+
- npm or Yarn
Install and check:
npm install
npm run typecheck
npm run verify:local-validatorBuild:
anchor buildRun the portable core suite:
npm run test:coreRun the full local Anchor suites on an AVX2-capable host:
npm run test:core:anchor
npm run test:full:anchor
npm run demoStart the read node:
npm run start:read-nodeVerify reviewer evidence:
npm run build:devnet:review-artifacts
npm run verify:generated-artifacts
npm run verify:allThe current public product path is Testnet-first. Use the commands below only when intentionally regenerating the preserved Devnet reviewer evidence package.
Set wallet and RPC:
export ANCHOR_WALLET=~/.config/solana/id.json
export ANCHOR_PROVIDER_URL=https://api.devnet.solana.comDeploy to Devnet:
anchor build
anchor deploy --provider.cluster devnetRun the canonical Devnet evidence package:
npm run test:devnet:allRun larger wave profiles when you intentionally want heavier Devnet traffic:
npm run test:devnet:100
npm run test:devnet:350
npm run test:devnet:500The 50-wallet package is the canonical reviewer baseline. Larger profiles write profile-specific artifacts and should be treated as stress operations, not routine verification.
Set wallet and RPC:
export ANCHOR_WALLET=~/.config/solana/id.json
export ANCHOR_PROVIDER_URL=https://api.testnet.solana.comRun the Testnet setup, deployment, and standard lifecycle proof path:
npm run setup:testnet
npm run deploy:testnet
npm run live-proof:testnetThe current Testnet proof keeps the canonical program id aligned with the frontend, IDL, reviewer packets, and public migration report. Use Testnet as the final public rehearsal layer before any mainnet release ceremony.
Upload-ready weekly update videos are generated from the repository evidence surface:
docs/assets/weekly-updates/private-dao-week-1-update.mp4docs/assets/weekly-updates/private-dao-week-2-update.mp4docs/assets/weekly-updates/private-dao-week-3-update.mp4docs/assets/weekly-updates/private-dao-week-4-update.mp4
References:
Commands:
npm run render:weekly-updates
npm run verify:weekly-updatesPrivateDAO is live on Solana Testnet today as a review-ready, audit-forward candidate, with a clear execution path toward unrestricted mainnet production readiness for real funds.
Ready now:
- live Solana Testnet program and product surface
- preserved-id Testnet deployment and standard lifecycle proof
- preserved PDAO Devnet governance-token evidence
- full governance lifecycle evidence
- Strict V2 additive hardening model
- Devnet rehearsal and adversarial reports
- generated audit packet and cryptographic manifest
- read-node and RPC reliability path
Next strategic closures before production mainnet:
- external audit or focused independent security review
- multisig/timelock upgrade authority hardening
- production monitoring and alerting
- real-device wallet capture closure
- operational sign-off for MagicBlock/REFHE source-verifiable receipts
- final mainnet release ceremony and cutover checklist
Key docs:
docs/mainnet-go-live-checklist.mddocs/mainnet-readiness.generated.mddocs/mainnet-proof-package.generated.mddocs/mainnet-blockers.mddocs/authority-hardening.mddocs/multisig-setup-intake.mddocs/custody-proof-reviewer-packet.generated.mddocs/monitoring-alert-rules.mddocs/wallet-e2e-test-plan.mddocs/release-ceremony.md
- Public story video: https://privatedao.org/story/
- Public YouTube reel: https://youtu.be/HiCz0vb8kgk
- Direct MP4 backup: https://privatedao.org/assets/private-dao-product-overview.mp4
- Upload-ready file:
/home/x-pact/Desktop/PrivateDAO-Product-Overview/PrivateDAO - Product Overview - Everything We Offer and Why Us.mp4 - Canonical lifecycle video brief:
docs/demo-video.md - Hosted lifecycle video: https://privatedao.org/assets/private-dao-demo-flow.mp4
- Repo-native lifecycle video:
docs/assets/private-dao-demo-flow.mp4 - Upload-ready lifecycle video:
/home/x-pact/Desktop/PrivateDAO-Demo-Video/PrivateDAO - Real Demo Flow - Create DAO Submit Proposal Private Vote Execute Treasury - Clean.mp4 - Investor / reviewer pitch deck:
docs/investor-pitch-deck.md - Product overview brief:
docs/investor-video.md - Repo-native product reel:
docs/assets/private-dao-product-overview.mp4 - Hosted product reel page: https://privatedao.org/story/
- Hosted product reel MP4 backup: https://privatedao.org/assets/private-dao-product-overview.mp4
- Poster:
docs/assets/private-dao-product-overview-poster.png - Product dossier:
docs/submission-dossier.md - Final submission pack:
SUBMISSION_FINAL.md - Operator answer packs:
docs/colosseum-submission-answers.md - Official YouTube channel: https://www.youtube.com/@privatedao
- Official Discord server: https://discord.gg/PbM8BC2A
- Brand kit:
docs/brand-kit.md - Hosted brand avatar: https://privatedao.org/assets/brand/privatedao-avatar-1024.png
- Technical explainer:
docs/investor-video.md
PrivateDAO development is maintained in public through X-PACT/PrivateDAO. Use the contact surface below for investment, strategic help, integrations, pilots, or direct operator coordination around the live Testnet product and its path to mainnet release.
For investment, strategic help, integrations, pilots, or direct operator coordination:
- Primary email: fahd.kotb@tuta.io
- Operations email: i.kotb@proton.me
- Additional contact: eslamkotb.369@gmail.com
- WhatsApp: +20 112 403 0209
- Telegram: @Fahdkotb
- Discord: PrivateDAO community server
- Operating contact packet:
docs/ownership-and-contact.md
See LICENSE, LICENSE-APACHE, LICENSE-MIT, and LICENSE-COMMERCIAL.md.