PrivateDAO

PrivateDAO helps organizations keep sensitive operations private and make the final outcome independently verifiable.

The public product message is:

Private decisions. Verifiable outcomes.

The current live website is privatedao.org. This repository is the engineering and evidence repository behind the platform; it is not the production deployment. Amazon, the live website, and the current production database are operated separately.

Current Product Surface

These are the primary product lanes currently presented on the live site:

Supporting routes include Pricing, Pilots, Developers, Trust, Docs, and Community.

What Is Live

The live homepage currently presents PrivateDAO as Solana-based confidential coordination infrastructure for organizations. Its central workflow is:

1. Choose a workflow.
2. Keep sensitive details private while the work is active.
3. Finish with a clear result, receipt, or on-chain reference.

The live site is the source of truth for public availability and wording. This repository is the source of truth for the implementation that is committed here. A feature is not production-supported merely because its code, route, badge, or documentation exists in this repository.

Repository Map

See docs/REPOSITORY_MAP.md for source ownership, generated-file rules, and the cleanup boundary.

Confidential Auctions

The auction implementation is intentionally isolated from the existing large PrivateDAO program:

• Program: privatedao-auction
• Program ID: 4Z7AeFRZHBCok68hhbUgVLC3uFaEP2aDWozsYVksPuQd
• Runtime target: Solana Devnet and MagicBlock development environment
• Public status: Devnet implementation; not Mainnet or production-certified
• UI route in source: /auctions
• Walletless verification route in source: /verify/auction

The intended lifecycle is:

Create auction
  -> delegate the selected state
  -> submit private bids in the private execution session
  -> close and compute the result
  -> commit the final result to Solana
  -> undelegate/reconcile
  -> publish a durable verification receipt

MagicBlock-specific evidence and limitations are kept under docs/magicblock/. The primary UI should describe the customer outcome, not internal runtime terminology.

Development

Prerequisites:

• Node.js 22+
• Rust stable
• Solana CLI
• Anchor CLI compatible with the checked-in workspace
• A local Solana wallet for Devnet testing only

Install web dependencies and run the web app:

npm --prefix apps/web install
npm --prefix apps/web run dev

Build and check the auction program:

cargo check -p privatedao-auction
bash scripts/build-auction-sbf.sh

Run the auction Devnet certification gate only when the required development wallets and MagicBlock development credentials are available:

npm run certify:auction:devnet

The certification command must never be interpreted as production or Mainnet certification. It must fail rather than manufacture a signature, receipt, or runtime session.

Deployment Boundaries

GitHub is used for source control and review. A push to GitHub is not an Amazon deployment. Production release requires a separate reviewed deployment step, environment configuration, migration plan, visual check, and rollback plan.

Evidence And Security

• Never commit .env files, PEM files, wallet keypairs, private keys, secrets, production receipts, or deployment state.
• Never treat a UI label, hash, metadata field, or documentation statement as runtime evidence.
• Keep private bid values and losing bids out of public Solana state and public receipts.
• Use the reports under docs/magicblock/ for diagnostic evidence, not as public product claims.
• Review SECURITY.md, NOTICE.md, and TERMS_OF_REVIEW.md before redistribution.

Known Repository Boundaries

This repository still contains historical static mirror output and older operational integrations because other scripts and review checks reference them. They are not automatically part of the current commercial product surface. The cleanup plan classifies them before removal so generated release artifacts, rollback evidence, and existing runtime paths are not confused with canonical application source.

For current public availability, use the live site. For implementation status, use the source tree, tests, and evidence files together.

License And Brand

Core source remains subject to the applicable repository licenses. PrivateDAO brand identity, official deployments, product design, protected evidence, and commercial service packaging are reserved. See NOTICE.md, TERMS_OF_REVIEW.md, and LICENSE.