Protocol v2.0 — Post-Quantum Capable
Specification: Final v2.0
Implementation: Active
Maturity: Early Adoption

The Trust Layer for AI Agents

Every AI agent needs a verifiable identity, declared intentions, and a tamper-evident audit trail. DCP is designed to provide all three through verifiable protocol artifacts, with post-quantum-capable cryptographic mechanisms and decentralized verification workflows.

5
SDKs
10
Integrations
4
Security Tiers
NIST
DCP-AI implements post-quantum cryptographic mechanisms based on NIST FIPS 203, 204, and 205. These references indicate standards alignment at the algorithm and protocol-design level, and do not imply CMVP or FIPS 140-3 module validation unless explicitly stated.

AI agents operate without accountability

Billions of AI agents are being deployed across industries. But today, there is no standard way to verify who controls them, what they intend to do, or what they actually did.

01

No Verifiable Identity

When an AI agent accesses your API, sends an email, or executes a transaction — who is responsible? Today, there is no cryptographic way to verify the human or organization behind an agent.

02

No Declared Intentions

Agents act without declaring what they intend to do before doing it. There is no pre-action commitment, no policy gate, and no risk assessment — just execution.

03

No Tamper-Evident Audit Trail

When things go wrong, there is no tamper-proof record of what happened. Logs can be altered, deleted, or simply not exist. Compliance and forensics become significantly harder and less reliable.

DCP: A portable accountability layer

The Digital Citizenship Protocol (DCP) binds every AI agent action to a verifiable chain of accountability — from the responsible human to the sealed audit record. Any party can independently verify it using published verification procedures.

Identity

Every agent is bound to a real human or organization through a Responsible Principal Record, signed with dual keypairs.

Intent

Before acting, the agent declares what it intends to do. A policy engine evaluates risk and authorizes or blocks the action.

Policy

Automated risk scoring across 4 security tiers determines the cryptographic assurances used for each action.

Audit

Every action produces a hash-chained, Merkle-sealed audit entry. The complete trail is packaged into a portable, verifiable bundle.

Three-layer design — modular by default

DCP separates concerns into three distinct layers. Only the Core is required for conformance; Profiles and Services extend capabilities without creating dependencies.

DCP Core

Core Protocol

Minimum interoperable protocol: specifications, artifacts, and verification procedures. Required for all conformant implementations.

Profiles

Extension Profiles

Crypto, A2A, and governance extensions. Optional modules that add capabilities without affecting core interoperability.

Services

Infrastructure Services

Verification, anchoring, and transparency services. Infrastructure layer, not normative — implementations may use alternatives.

From human to sealed proof — in one pipeline

Every AI action flows through a cryptographically signed pipeline. The output is a Citizenship Bundle — a portable, independently verifiable proof of authorized activity.

Human
RPR
Passport
Intent
Policy
Audit
Bundle

1. Bind Identity

A Responsible Principal Record ties a real person or organization to an Agent Passport using Ed25519 + ML-DSA-65 composite keypairs. Cryptographically attributable chain of responsibility.

2. Declare Intent

Before any sensitive action, the agent declares intent: what it wants to do, which data is involved, and the estimated impact. A policy engine gates the action.

3. Audit Everything

Every action produces an audit entry with dual-hash chains (SHA-256 + SHA3-256). Post-quantum checkpoints periodically seal the chain with hybrid signatures.

4. Seal & Verify

All artifacts are assembled into a Citizenship Bundle with a cryptographic manifest. Composite-signed, portable, and independently verifiable with published tools and procedures.

TypeScript
import { BundleBuilder, KeyManager } from '@dcp-ai/sdk';

const keys = await KeyManager.generate({ algorithm: 'hybrid' });
const bundle = await new BundleBuilder()
  .setIdentity({ name: 'my-agent', operator: 'org:acme' })
  .addIntent({ action: 'api_call', resource: 'payments', tier: 'elevated' })
  .sign(keys)
  .build();
// bundle is now a portable, verifiable Citizenship Bundle

Formal specification suite

DCP is defined by a suite of numbered specifications. Each spec is independently implementable and references the normative v2.0 document.

SpecTitleScopeStatus
DCP-01Identity and Human BindingRPR, Agent Passport, composite keypairsFinal
DCP-02Intent Declaration and Policy GatingIntent schema, risk scoring, 4-tier modelFinal
DCP-03Audit Chain and TransparencyHash chains, Merkle trees, transparency logFinal
DCP-04Agent-to-Agent CommunicationA2A protocol, mutual auth, delegationFinal
DCP-AI v2.0Post-Quantum Normative SpecificationFull specification, profiles, bundle formatFinal

Four tiers — automatic risk-based selection

DCP can automatically select the appropriate cryptographic tier based on risk score, data classification, and action type, with support for policy overrides where needed.

Tier 0 — Routine

Routine

  • Ed25519 classical signatures
  • Public data reads, browsing
  • Risk score < 200
Tier 1 — Standard

Standard

  • Ed25519 + hybrid preferred
  • API access, general writes
  • Risk score 200–499
Tier 3 — Maximum

Maximum

  • Full hybrid + immediate verification
  • Credentials, critical infrastructure
  • Risk score ≥ 800

Built on open standards and proven cryptography

Open Source — Apache-2.0

Full source code, specifications, and SDKs are publicly available. Audit it yourself.

NIST FIPS 203/204/205

Post-quantum algorithms (ML-DSA-65, ML-KEM-768, SLH-DSA) follow NIST finalized standards.

Post-Quantum Capable

Hybrid Ed25519 + ML-DSA-65 composite signatures are designed to improve resilience against classical and future quantum threats.

Blockchain Anchoring

Optional L2 anchoring (Base, Arbitrum, Optimism) provides on-chain proof of existence for bundles.

Transparency Log

Certificate Transparency-style Merkle log with inclusion proofs.

Bug Bounty Program

Up to $15,000 for critical vulnerabilities. Responsible disclosure with 48-hour acknowledgment.

Supports AI governance relevant to the EU AI Act

DCP provides technical capabilities that can support traceability and accountability workflows relevant to the EU AI Act (Art. 14, 15). Tamper-evident audit chains can help meet evidence trail expectations.

Aligned with the NIST AI RMF Core

DCP-AI maps governance, risk identification, measurement, and mitigation workflows to the Govern, Map, Measure, and Manage functions of the NIST AI Risk Management Framework.

W3C DID/VC Bridge

Interoperable with the W3C decentralized identity ecosystem. Agent Passports can be represented as DIDs with Verifiable Credentials.

Your language, your choice

Reference SDKs for major languages, with conformance-focused implementations under active development.

TS
TypeScript
@dcp-ai/sdk
Py
Python
dcp-ai
Go
Go
dcp-ai-go
Rs
Rust
dcp-ai
W
WASM
@dcp-ai/wasm

Plug into your existing stack

LangChain
CrewAI
OpenAI
Express
FastAPI
AutoGen
Google A2A
Anthropic MCP
W3C DID/VC
OpenClaw

Get started in minutes with the CLI and reference SDKs.

Initialize a DCP identity, generate hybrid keys, and create your first verifiable bundle with a single command.

npx @dcp-ai/cli init

Read the Documentation → Read the Genesis Paper

Be among the first to integrate DCP

Join our co-design partnership. Get direct access to the core team, priority support, influence over protocol decisions, and a published case study.

Apply Now → Learn More

Frequently asked questions

What is a Citizenship Bundle?
A Citizenship Bundle is a portable cryptographic package that contains all proof of authorized AI activity: the identity binding, declared intent, policy decision, audit trail, and a composite signature. Any party can independently verify it using published verification procedures.
Do I need to understand post-quantum cryptography?
No. The SDKs handle all cryptographic complexity. You call simple methods like KeyManager.generate() and BundleBuilder.sign(). The SDK automatically generates Ed25519 + ML-DSA-65 hybrid keypairs and creates composite signatures behind the scenes.
Is DCP ready for use?
The v2.0 specification is finalized and core implementation milestones are in place. SDKs are in active development with conformance test suites. The Early Adopter Program is the bridge between specification completeness and broader production hardening.
Does DCP require a blockchain?
No. The core DCP protocol does not require blockchain anchoring. Blockchain anchoring is an optional service for organizations that want on-chain proof of existence; the protocol and verification workflows do not depend on it.
What frameworks does DCP integrate with?
DCP offers integrations and adapters for LangChain, CrewAI, OpenAI, Express, FastAPI, AutoGen, Google A2A, Anthropic MCP, W3C DID/VC, and OpenClaw. Each provides idiomatic APIs for the framework.
Is there a cost to use DCP?
DCP-AI is open source under Apache-2.0. Optional blockchain anchoring may involve transaction fees, and deployment may also involve infrastructure or third-party service costs depending on the implementation.
Who is behind DCP?
DCP is governed through an open governance model documented in GOVERNANCE.md. The foundational vision is described in the Genesis Paper. All protocol decisions are made transparently through public proposals and community review. Contributions from both humans and AI agents are welcome — DCP belongs to everyone who uses it.