PrivateDAO Agent Exchange

PrivateDAO

Private decisions. Verifiable outcomes.

PrivateDAO is a privacy-first operating layer for organizations that need to run sensitive work without making every detail public. It helps teams define rules, run workflows, approve actions, execute through the appropriate infrastructure, and share evidence of the outcome.

PrivateDAO is built for organizations entering Web3 as well as organizations that never intend to become crypto companies. A business can keep its existing operating model and add verifiable Web3 capability only where it is useful: private payroll, controlled treasury actions, governance, procurement, and verification. Privacy is the product principle; blockchain, wallets, and cryptography are execution infrastructure behind that principle.

Product direction

The project is organized around six core organizational workflows:

1. Confidential Payroll - pay people without publishing salary records.
2. Treasury Coordination - approve and reconcile sensitive spending.
3. Private Governance - make and prove decisions without exposing every discussion.
4. Confidential Auctions - run sealed procurement and competitive bids.
5. Blind Verification - prove that a condition was met without revealing the underlying information.
6. Record Verification - prove that a document, event, or result is valid without publishing private fields.

These workflows share the PrivateDAO Kernel, policy controls, execution adapters, receipts, and reconciliation boundaries. The public product surface is intentionally simple; technical network details remain available for builders, reviewers, and operators.

Next milestone: PDAO Wallet

The next product milestone is PDAO Wallet, an account and policy layer for organizations rather than a single consumer wallet. The planned wallet suite will support:

• corporate accounts for the six core workflows and institution management;
• an autonomous AI wallet for bounded, policy-controlled agent operations;
• a B2B wallet for organizations, counterparties, and service settlement;
• role-based permissions, approval thresholds, spending policies, signing boundaries, receipts, reconciliation, and audit-ready evidence.

PDAO Wallet will be developed as a capability layer above the PrivateDAO Kernel. It will remain independent from any single chain or provider, while each network adapter is required to provide real implementation and evidence before it is described as supported.

Quantum-security roadmap

PrivateDAO plans a quantum-resilience layer above the Kernel and PDAO Wallet. This work will evaluate current post-quantum and hybrid cryptographic libraries, key-agility patterns, signing policies, migration paths, and hardware-backed execution as the standards and production libraries mature. The implementation will use maintained, independently reviewed libraries and explicit compatibility gates. This roadmap is not a claim that PrivateDAO is currently quantum-safe, certified, or externally audited for post-quantum security.

Ecosystem programs and technology partners

PrivateDAO is participating in the following programs based on accepted program communications and the partnership records maintained by the project owner:

These program relationships do not by themselves mean endorsement of every PrivateDAO product, certification, customer reference, grant award, or joint commercial offering. Product capabilities remain subject to the evidence and status recorded in the repository. The supporting acceptance emails and public announcements are retained by the project owner; this repository records the program names and their intended technical role without reproducing private correspondence.

The PDAO Wallet roadmap will use these relationships for storage, AI inference, hardware/performance testing, developer tooling, and operational validation as the relevant integrations are enabled. See the ecosystem program record for the technical scope and disclosure boundary.

Evidence language

This repository distinguishes three states:

• Verified - backed by current source, runtime, or independently checkable execution evidence.
• Planned - an approved product or engineering milestone that is not yet a completed production capability.
• Historical - retained material that explains prior work but is not a current product claim.

Network configuration, an address, a UI label, or a passing unit test alone is not evidence of a live product execution path. See the capability matrix and linked evidence for the status of each network and workflow.

Live Testnet program: EP9xE8MJZ6FfyEwLqns6HDdUZBknEa7WGYs1Jzsecuva

Historical Devnet proof registry program: 5AhUsbQ4mJ8Xh7QJEomuS85qGgmK9iNvFqzF669Y7Psx (docs/proof-registry.json); this is retained as provenance and is not the current Testnet deployment.

An organization does not need to become a Web3 or crypto company to use PrivateDAO. A company, institution, financial team, DAO, data provider, or Web3 operator can start with a familiar business workflow and add wallets, networks, settlement, or verifiable Web3 capability only where it creates value.

What PrivateDAO provides

Private operations

• Confidential Payroll - prepare payroll, apply tax and deduction rules, collect approvals, settle through a supported private-payment path, and produce a verifiable result without exposing employee records.
• Treasury Coordination - manage spending requests, budgets, approvals, execution, reconciliation, and evidence for sensitive financial operations.
• Private Governance - coordinate proposals, committees, delegation, and decisions while keeping sensitive discussion and voting context private where the workflow requires it.

Private transactions and markets

• Confidential Auctions - protect competing bids until the agreed close, then produce a fair and checkable result.
• Private Settlement Workflows - move an approved operation through a supported settlement provider and retain a receipt with clear lifecycle status.

Verification

• Blind Verification - prove that a condition or policy was satisfied without revealing the underlying data.
• Record Verification - create a shareable, tamper-evident record for a document, event, approval, or business result without publishing private fields.
• Private Identity Verification - support selective confirmation of identity, entity, jurisdiction, or authorization requirements while keeping the source material private.

Agent and community products

• PrivateDAO Agent Exchange - an MCP-compatible service marketplace for verification, blockchain intelligence, market context, agent discovery, and verifiable receipts.
• PDAO Worlds - an independent community game about privacy, trust, evidence, and coordination. It is a separate product and does not define the commercial workflow runtime.

Community

PDAO Worlds is the community layer for education, experimentation, and shared participation around PrivateDAO. It is separate from the organization workflow products and does not change the evidence or security requirements of the Kernel, PDAO Wallet, or settlement paths.

PDAO token surface

The current published token surface is documented in docs/pdao-token.md and the machine-readable attestation is docs/pdao-attestation.generated.json. The documented Testnet governance token is PDAO with mint DFYvBdivHCe4bSErgCiKm2RhwGEcZYbBPFQzLNr37Bie and a published initial supply of 1,000,000 PDAO. These references describe the current evidence surface; they do not claim Mainnet launch, market liquidity, or speculative returns.

How it works

Choose the workflow

-> define rules and participants -> run privately -> approve and execute -> reconcile the result -> share only the evidence that others need

The customer-facing workflow comes first. Wallets, providers, networks, RPC clients, cryptography, and settlement details remain behind the product boundary until execution requires them.

Agent Exchange

The production Agent Exchange is available at:

• Marketplace: https://agents.privatedao.org/
• MCP endpoint: https://agents.privatedao.org/mcp
• Connection hub: https://agents.privatedao.org/connect
• Agent card: https://agents.privatedao.org/.well-known/agent-card.json

The endpoint is designed for standard MCP clients and exposes discovery, verification, intelligence, agent matching, job lifecycle, payment-aware receipts, and marketplace capabilities. Free discovery and read-only tools are separate from paid service execution. A client must use the published schemas and receipts; a frontend response is not payment proof.

Current payment and network claims are capability-specific. Where a service requires payment, the active payment rail and supported target network are returned by the service catalog. Do not infer that every advertised target network has the same execution or payment capability.

Kernel and runtime architecture

The current separation between the six enterprise products and the external Agent Exchange is documented in docs/architecture/enterprise-kernel-boundary-20261014.md.

The repository contains provider-neutral runtime contracts in packages/privatedao-runtime. The Kernel and Protocol layers provide common boundaries for:

• product capabilities and permissions;
• provider selection and lifecycle states;
• wallet-signing boundaries;
• preparation, submission, confirmation, and receipts;
• reconciliation, idempotency, normalized errors, and telemetry;
• MCP, REST, SDK, and agent-facing contracts.

Network-specific transaction construction belongs behind adapters. The runtime package does not store private keys, contain a wallet signer, or invent a successful receipt. A configured network is not considered supported merely because it appears in a UI or configuration file; it needs a real adapter and independent evidence.

Review and operating references

The repository keeps security, release, runtime, and operating evidence available for reviewers. These documents describe engineering evidence and boundaries; they are not claims of incorporation, certification, partnership, or mainnet readiness unless the referenced document says so explicitly.

• Security review
• Threat model
• Security coverage map
• Failure modes
• Replay analysis
• Live proof
• Devnet release manifest
• Verification gates
• [Mainnet readiness](do