Explore

Product navigation

Judge Route
Canonical reviewer path with product proof, integrations, awards context, and runtime evidence
Try
Shortest private governance workflow
Start
Guided onboarding and wallet-first flow
Learn
Workflow-first onboarding and product operating guide
Help
Product guide across routes, docs, and proof
Govern
Create, vote, reveal, and verify private governance
Intelligence
Risk scoring, market context, and signer decision support
Treasury
Treasury health, solvency context, and agent policy routes
Proof Workflows
Standalone process proof product for non-DAO organizations
Payroll
Private payroll CSV, stablecoin choice, and auditor receipt flow
Gaming
Guilds, tournaments, inventory proposals, and reward operations
Compliance
Scoped compliance packs and bounded viewing-key evidence
Execute
Private payroll, vendor settlement, and treasury actions
Proof
Operation receipts, runtime logs, and verification routes
Developers
API docs, SDK starters, and integration surfaces
RPC Services
Hosted reads, relayer checks, QVAC status, and runtime endpoints
API Status
Backend health, visitor counters, and freshness endpoints
Command Center
Ops dashboard, indexed proposals, and readiness gates
Live State
Proposals, treasury, and action logs
Story
Live product story and fast explanation
Community
Join, updates, pilot interest, and support routing
Benefit
theMiracle wallet-placement benefit and Founding Governor access
Versus
PrivateDAO compared with Realms, Squads, Snapshot, and DAOhaus
Revenue
Self-hosted, managed SLA, and enterprise commercial tiers
Android
Mobile app, APK download, parity plan
Trust
Security, proof, and operating boundaries
Health
Runtime status and verification health
Custody
Multisig, authority transfer, and custody evidence
Analytics
Votes, proposals, actions
API & Pricing
Pilot, API, commercial packs
Engage
Buyer path, pilot motion, mainnet trajectory
Search
Search routes, docs, tracks, and proof
Docs
Curated reviewer and trust docs
Open-source core
Review access
Official use reserved
Legal Notice
Public review is open; official use requires coordination

PrivateDAO remains open source where the license applies and visible for judges and ecosystem reviewers while protecting project authorship, brand identity, digital proof artifacts, and sensitive product packaging.

Legal notice
IP and evidence boundary
Security review friendly

This notice is intended to protect the public-good review posture of PrivateDAO while keeping the path open for judges, auditors, Solana ecosystem contributors, partners, and serious institutional collaborators. It is not a substitute for formal legal counsel or a signed commercial agreement.

Official ownership record

PrivateDAO, PDAO, the official website, GitHub repository, service matrix, privacy execution claims, proof routes, AI-readable manifests, media assets, product packaging, and official deployment surfaces are authored and maintained by Fahd Kotb / Eslam Kotb under X-PACT unless a specific file states otherwise.

Public source review

The repository remains open source where the repository license applies, and the website remains available so judges, auditors, partners, and ecosystem reviewers can inspect the work. Review access does not grant permission to impersonate PrivateDAO, redeploy official surfaces, reuse brand identity, or commercialize official service packages without written coordination.

Code and license boundary

Source files that explicitly remain under AGPL-3.0-or-later keep the rights and duties of that license. PrivateDAO brand, product design, documents, evidence packets, roadmap material, media assets, service packaging, and official deployments are reserved unless separately licensed.

Digital evidence

On-chain transaction hashes, Supabase receipt traces, runtime proof packets, screenshots, and submission evidence are preserved as PrivateDAO review artifacts. They may be cited for evaluation, security reporting, and ecosystem coordination, but not copied into misleading or competing official claims.

Coordination path

PrivateDAO is open to ecosystem collaboration, audits, pilots, and official integration work. Open-source forks must respect the repository license; brand use, official-looking derivative deployments, commercial packaging, or government/institutional reuse should be coordinated through official PrivateDAO channels first.

DAO entity and IP package

The Futardio and PrivateDAO launch path uses a DAO entity workflow so PDAO ownership can be tied to enforceable project control. The future entity should hold or control repository administration, domains, brand assets, official launch materials, deployed program authorities, infrastructure administration, proof materials, and future production deployment rights.

Anti-impersonation boundary

Forks, references, research, and integrations must not mislead users, judges, investors, search engines, AI evaluators, or ecosystem partners into believing they are the official PrivateDAO project, official PDAO token identity, or official PrivateDAO deployment.

Trust surface
Open security, proof, and operating boundaries.
Repository
Review the source with the repository notice attached.
Futardio launch legal route

Public terms URL and IP packet for launch review

Use this page as the public legal terms URL for launch review. The companion IP packet lists the repository, domains, brand assets, deployed program boundaries, infrastructure controls, and DAO entity rights that should be administered for the benefit of the future PDAO ownership community.