Proof21
Protocol previewFor agents
EN
Menu

P21 / Visual reference

Trace the boundaries.

Readable SVG diagrams paired with editable Mermaid source. Design artifacts—not evidence of a live network.

Proof21 proposed system architecture Source adapters feed deterministic checks. A separate consumer verifies findings and applies its own policy. Bitcoin timestamping is optional. Optional / asynchronous Instruction + policy Evidence adapters Bitcoin / DMT / TAP EVM + signed artifacts P21 deterministic checks Findings + evidence Consumer verification Local acceptance policy Bitcoin timestamp
Proposed architecture. Preserve source assumptions; the consuming platform retains its own acceptance policy.
Integrity is not evaluation or acceptance A recipient checks the artifact, reproduces a named evaluation and applies its own acceptance requirements. Invalid or unresolved Fail or indeterminate Original evidence + instruction P21 report VERIFY: integrity + bindings EVALUATE: named policy ACCEPT: receiver policy Reject or review Receiver decides next action
A valid signature is not the same as a passing policy or permission to move funds.
Experimental selection commitment lifecycle Commit the inputs before observing the specified future source. The receiver independently checks the derivation. Sampling does not establish completeness. Missing source or reorg Fix eligible set + order + policy Observable precommitment Wait for agreed future source Check confirmation requirements Apply specified selection mapping Consumer reproduces selection Pending / failed - no silent reroll
Experimental design. Precommitment, source verification, and mapping are separate checks; completeness is not established by sampling.
A service fee and the requested payout are different events P21 relates an instruction, a commercial payment receipt and the underlying execution evidence. Paying an API does not prove a payout. Agent instruction Payout service x402 / B402 service fee Requested financial payout Commercial receipt Execution evidence P21 supported checks Findings - no automatic fund release
The payment for an API service and the requested financial payout must be checked as separate events.
Fast checks and optional asynchronous commitment Consumer verification need not wait for a Bitcoin timestamp unless the local policy requires it. A pending timestamp is not a verified anchor. Optional Evidence P21 checks Report Consumer verification Digest batch Timestamp pending Verify Bitcoin evidence Verified / failed
Optional timestamp status is independent of report integrity and evaluation. Pending is not verified.
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