Proof21
EN
Menu
Browse documentation
Protocol specification

Status and roadmap

Read Markdown

Documentation baseline: 2026-09-09 · website/source release 0.10. Repository history is authoritative for subsequent changes.

Surface Current state
Name, palette, typography Recorded in versioned brand files
Documentation and static website Full self-hosted docs and simplified homepage prepared for review
Educational offline demo Working Node example with synthetic signed fixtures; not a production SDK
Production runtime, SDK, CLI verifier Not released
Live paid endpoints Not deployed
Bitcoin selection security Experimental design; not audited
Third-party integrations Targets, not partnerships
Token Not issued by this foundation

Build sequence

Foundation: establish sources, brand, precise scope, architecture, and conformance cases.

Reference core: implement shared evidence handling, financial checks, supported DMT derivations, and the three-stage consumer decision. Reject unsupported semantics explicitly.

Interfaces: add a thin TypeScript SDK, CLI, HTTP service, and MCP wrapper around the same core. Add test-payment support and asynchronous commitment handling.

Experimental selection: implement the commitment state machine and source adapters against test vectors. Review miner/operator influence, rerolls, omissions, and reorganizations before meaningful-value use.

External pilots: run shadow-mode workflows with independent operators and consumers. Measure usefulness, error handling, costs, repeat use, and willingness to pay.

Network expansion: add chain and partner profiles based on measured demand. Consider independent operators and a token only when they improve a demonstrated network function.

Release gates are tested behavior, defined scope, and review—not an estimated launch date.

Offline onboarding

The website now includes a downloadable, dependency-free Node demonstration and a permission-aware agent reading guide. npm run demo executes a local repository script; no npm registry package is published. The demonstration uses synthetic evidence and cannot authorize a real payment. See Offline demo.

<!-- p21-source-payment-v08 -->

Commercial activation and implementation status

NAT and USDC are both required for the initial commercial-launch acceptance test. Public documentation, source code and policy fixtures are not live payment endpoints. The static payment-policy resource lists required launch methods with enabled: false, no recipient and no live endpoint until each rail passes end-to-end settlement, accounting, failure/reorganization, security and owner-approval gates. Do not advertise a USDC-only release as the completed initial payment scope.

No token has been issued, no source element is announced, and no mainnet inscription, customer charge, treasury swap or wallet authorization is performed by this release. Production service availability remains separate from website publication. No Trac partnership, hosted SLA or independent cryptographic audit is implied.

[1] https://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/digital-elements/.element-registry

[2] https://github.com/Trac-Systems/ord-tap/blob/b8f6ea35cf6b9d405d4db7c58555e3c8ab33e8cd/src/index/updater/inscription_updater/tap/ops/dmt_element.rs

[3] https://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/nat-use-cases/usdnat-method-1-live

[4] https://digital-matter-theory.gitbook.io/digital-matter-theory/introduction/non-arbitrary-tokens-nats/nat-token-transfer

[5] https://docs.x402.org/core-concepts/network-and-token-support

[6] https://github.com/Trac-Systems/ord-tap/blob/b8f6ea35cf6b9d405d4db7c58555e3c8ab33e8cd/README.md

[7] https://arxiv.org/abs/1605.04559

<!-- p21-ecosystem-payments-v09 -->

v0.9 publication scope

This revision adds cross-chain NAT representation references and integration-specific stablecoin policies. The source includes full signal-orange 21 branding and managed motion on the journal listing as well as articles. Existing research is preserved; payment, DMT, interoperability and economics notes receive dated additions. Tests distinguish static policy validation and browser behavior from live settlement, audited bridge mapping and production verifier availability. All payment endpoints and merchant recipients remain unconfigured.

Binance assets and methods · Binance integration · Coinbase facilitator · PayAI assets · Virtuals ACP · NAT Ethereum listing · NAT Solana record · NAT BNB Chain contract

<!-- p21-enforcement-v10 -->

v0.10 enforcement/accountability scope

The specification now defines an optional P21 Execution Gate, exact action binding, acceptance-policy precommitment, signed consumer decisions, contradiction/equivocation evidence and an optional TAP threshold-enforcement profile. Machine-readable draft schemas are published with the static site.

Implementation status remains conservative: the production execution gate, P21 policy signer, wallet/MPC/HSM adapters, consumer-decision service and dispute/reputation service are not released. The existing Alpha model remains evidence/shadow mode. No customer funds, wallet keys or spending authority are transferred to P21 by this documentation release.

Private DMT element selection/registration moves into the near-term operational roadmap. The element stays to be announced until historical uniqueness validation, inscription, confirmation and independent index verification are complete.

v0.10.1 presentation maintenance

Auditable Selection now illustrates a visible deterministic scan and the same sample on each loop. The workflow uses translucent paper on narrow sticky layouts; Preferences remains in the footer rather than the header. Presented-frame monitoring supplements media-clock checks. DMT guidance distinguishes catalogue fields from supported profiles and private preparation from public reveal. Production runtimes, payment activation, element inscription and legal publication approval are unchanged.

v0.10.2 workflow layers

Scrolling words sit behind one continuous translucent paper sheet and the fully opaque foreground artwork. On compact screens, a Remotion-rendered transparent animated image is the primary medium, avoiding the opaque video matte observed in WebKit. A transparent still image remains when motion is disabled or the animation cannot load. The mobile illustration loops while text and progress indicators follow scrolling; desktop video scrubbing is unchanged. Blank paper softly transmits words, while the white cards conceal them. The sheet covers the progress-dot margins. Content-versioned styles and motion code avoid stale browser assets. Production activation and the unannounced DMT element are unchanged.

Local search · No prompts or queries sent to an AI provider

Privacy & preferences

Essential

Website delivery and security; a local record of your privacy choice for up to 180 days. No advertising identifier.

Save your motion preference on this browser. Optional; off unless you choose it.

Use static illustrations. Your device setting takes priority. No storage permission is needed.

Analytics & advertising

Currently off. Future cookies, pixels, or analytics will be disclosed and require a new choice where applicable. These buttons do not authorize future tracking.

Privacy · Cookies