IETF Internet-Drafts
AlgoVoi-authored specifications filed with the IETF under the Independent Submissions stream (Informational). These are not vendor whitepapers — they are citable IETF documents with assigned datatracker URLs and submission IDs. They are the durable, protocol-neutral home for the formats below: independent of any single repository’s review decision. The nine I-Ds span the receipt and attestation formats, the JCS canonicalisation discipline, NIST post-quantum credential binding (Falcon-1024 / ML-DSA-65, FIPS 204 / 206), and cross-issuer ZKP federation. The last two are, as far as the author is aware, the first agentic-payment I-Ds to anchor credential binding and federation to the NIST post-quantum standards.| I-D | Datatracker | Latest rev | What it specifies |
|---|---|---|---|
draft-hopley-x402-canonicalisation-jcs-v1 | datatracker | rev 04 (2026-05-29) | The JCS canonicalisation discipline urn:x402:canonicalisation:jcs-rfc8785-v1. Five normative rules composing RFC 8785 with the canon_version pin. Sole AlgoVoi authorship. Anchors the 8-impl cross-validation matrix (192/192 byte-for-byte agreements). |
draft-hopley-x402-compliance-receipt | datatracker | rev 02 (2026-05-25) | The Compliance Receipt wire format: seven-field canonical JSON object, closed three-state verdict enum (ALLOW / REFER / DENY), JCS + SHA-256 content-addressing. Cross-validated across 8 independent JCS implementations. Sole AlgoVoi authorship. |
draft-hopley-x402-settlement-attestation | datatracker | rev 01 (2026-05-25) | Categorical post-settlement record: closed three-state enum (SETTLED / PENDING_FINALITY / REVERSED), flat settlement_chain identifier, finality applied at verification time. SETTLED triggers MiCA Art. 80 / AMLR record-keeping and the PSD2 Art. 89 refund-window clock. |
draft-hopley-x402-payment-evidence-frame | datatracker | rev 00 (2026-05-30) | The payment evidence frame: frame_id = SHA-256 over the JCS-canonical preimage binding receipt evidence (receipt_hash) to a claim_type. Protocol-neutral evidence envelope. |
draft-hopley-x402-cancellation-receipt | datatracker | rev 01 (2026-05-25) | Pre-settlement cancellation attestation envelope (PSD2 Article 64). Categorical, JCS-canonical, content-addressed. |
draft-hopley-x402-refund-receipt | datatracker | rev 02 (2026-05-25) | Post-settlement refund attestation envelope (PSD2 Article 89). Categorical, JCS-canonical, content-addressed. |
draft-hopley-x402-composite-trust-query | datatracker | rev 01 (2026-05-25) | Multi-issuer composite trust verdict: closed four-state enum (TRUSTED / PROVISIONAL / INSUFFICIENT_EVIDENCE / UNTRUSTED) composing compliance, settlement, and counterparty-risk evidence into one canonical record. |
draft-hopley-x402-pqc-credential-binding | datatracker | rev 00 (2026-06-04) | Binds Falcon-1024 (NIST FIPS 206 / FN-DSA) and ML-DSA-65 (FIPS 204) credentials to x402 agentic-payment authorization: credential envelope, JCS discipline over signed payloads, gateway verification procedure, and the session-token binding that replaces per-request API-key auth for credentialed agents. First agentic-payments I-D anchored to the NIST post-quantum standards (FIPS 203 / 204 / 206). |
draft-hopley-x402-federation-zkp | datatracker | rev 00 (2026-06-04) | Composes independently-issued post-quantum ZKP credentials from different issuers into a single federation token with no shared trust root. Each credential is a Falcon-1024 / ML-DSA-65 signed Bulletproofs range proof asserting a trust-score threshold; a federation validator verifies each against its issuer key, computes a composite commitment binding all verified proofs, and signs the federation token alone. Solves cross-issuer attestation composition in agentic-payment networks. |
Protocol-level contributions
These land AlgoVoi as a canonical reference inside the protocol’s own repository, not just an entry in an external list.Compliance-evidence and attestation specifications
AlgoVoi authored the compliance-evidence and attestation surface as a set of extension specifications: a categorical compliance receipt, settlement attestation, cancellation/refund envelopes, a composite trust query, and an RFC 9421 transport binding. These were first filed againstx402-foundation/x402. On 2026-06-02 the core team closed the community extensions tree in a single batch: 49 pull requests from roughly 28 different authors, closed within minutes of one another (AlgoVoi’s nine among them, between 17:27 and 17:30 UTC, with no per-PR review comments), and opened its own consolidated vcx-v1 extension PR (#2544) about half an hour later, at 17:59 UTC. None of the AlgoVoi formats were closed on an individual merit review; they were part of a repository-wide reset of the extensions tree.
The specifications do not depend on that repository. Every format below is filed as a citable IETF Internet-Draft (above), carried as an open spec PR in the AP2 repository (next section), and shipped as an installable reference implementation (further below). The table records the original x402 filings for provenance, the close date, and the current home of each format.
| Format | x402 filing (provenance) | Closed | Current home |
|---|---|---|---|
Compliance receipt (ALLOW / REFER / DENY) | x402#2493 | 2026-06-02 | I-D draft-hopley-x402-compliance-receipt; AP2 #269; pkg algovoi-substrate |
| Pre-payment compliance gate | x402#2495 | 2026-06-02 | AP2 #269; A2A #1886 (compliance/gate RPC) |
| Cancellation + refund envelopes (PSD2 Art. 64 / 89) | x402#2494 | 2026-06-02 | AP2 #270; pkgs algovoi-cancellation-receipt, algovoi-refund-receipt |
Settlement attestation (SETTLED / PENDING_FINALITY / REVERSED) | x402#2524 | 2026-06-02 | AP2 #271; pkg algovoi-settlement-attestation |
| Composite trust query (multi-issuer verdict) | x402#2525 | 2026-06-02 | AP2 #272; pkg algovoi-composite-trust-query |
| RFC 9421 / RFC 9530 transport binding | x402#2526 | 2026-06-02 | AP2 #273; pkgs algovoi-rfc9421-verifier, algovoi-rfc9421-signer |
| Payment evidence frame | x402#2527 | 2026-06-02 | AP2 #274; A2A #1898 |
| JCS canonicalisation discipline | x402#2453 | 2026-06-02 | I-D draft-hopley-x402-canonicalisation-jcs-v1; spec file replaces closed #2436 |
Bazaar Compliance category | x402#2322 | 2026-05-27 (superseded) | Compliance-evidence surface carried in AP2 #269 |
privacy_class settlement-plane visibility | x402#2334 | 2026-06-02 | Settlement-visibility attestation carried in AP2 #271 |
Protocol spec PRs (AP2, A2A, MPP)
The compliance-evidence surface above is carried as open spec PRs in the AP2, A2A, and MPP-specs repositories, alongside protocol samples and fixes.| Protocol | Repository | PR | Filed | Status | What it adds |
|---|---|---|---|---|---|
| AP2 | google-agentic-commerce/AP2 | #269 | 2026-05-28 | Open | docs/ap2/compliance_receipt.md — Compliance Receipt format in the AP2 spec. Admission-time ALLOW / REFER / DENY verdict bound to Payment Mandate by JCS canonical hash. |
| AP2 | google-agentic-commerce/AP2 | #270 | 2026-05-28 | Open | docs/ap2/payment_lifecycle.md — cancellation and refund attestation envelopes in the AP2 payment lifecycle (PSD2 Articles 64 and 89). |
| AP2 | google-agentic-commerce/AP2 | #271 | 2026-05-30 | Open | docs/ap2/settlement_attestation.md — categorical post-settlement record (SETTLED / PENDING_FINALITY / REVERSED). MiCA Art. 80 / DORA Art. 14 alignment. |
| AP2 | google-agentic-commerce/AP2 | #272 | 2026-05-30 | Open | docs/ap2/trust_query.md — multi-issuer composite trust verdict envelope. Composes compliance, settlement, and counterparty-risk evidence into one canonical record. |
| AP2 | google-agentic-commerce/AP2 | #273 | 2026-05-30 | Open | docs/ap2/http_message_signing.md — RFC 9421 HTTP Message Signatures binding for AP2 mandate exchanges. Multi-hop proxy-chain survival. |
| AP2 | google-agentic-commerce/AP2 | #274 | 2026-05-30 | Open | docs/ap2/payment_evidence_frame.md — the payment evidence frame: frame_id = SHA-256 over the JCS-canonical preimage binding receipt evidence to a claim type. |
| AP2 | google-agentic-commerce/AP2 | #276 | 2026-06-04 | Open | AP2 extension registration for PQC/ZKP credential binding and the zero-knowledge attestation surface. |
| AP2 | google-agentic-commerce/AP2 | #278 | 2026-06-06 | Open | Spec fix: replace algorithm-class proxy with an entropy-based derivation in the mandate-hash discipline. |
| AP2 | google-agentic-commerce/AP2 | #279 | 2026-06-06 | Open | Conformance: open_mandate_hash derivation vectors. |
| AP2 | google-agentic-commerce/AP2 | #253 | 2026-05-01 | Open | JCS cart-to-payment mandate binding per RFC 8785. |
| AP2 | google-agentic-commerce/AP2 | #228 | 2026-04-24 | Open | crypto-solana human-present sample: AP2 mandate settled via Solana Pay reference binding. |
| AP2 | google-agentic-commerce/AP2 | #218 | 2026-04-13 | Open | crypto-algo human-present sample: AP2 mandate settled in USDC on Algorand. |
| A2A | a2aproject/A2A | #1886 | 2026-05-28 | Open | Registers the Compliance Gate Extension v1 in the A2A example extensions table. Method Extension adding the compliance/gate RPC method. |
| A2A | a2aproject/A2A | #1896 | 2026-05-30 | Open | Registers Settlement Attestation, Composite Trust Query, and RFC 9421 Message Signing extensions in the A2A example extensions table. |
| A2A | a2aproject/A2A | #1898 | 2026-05-30 | Open | Payment evidence frame specification in the A2A extension docs. |
| MPP | tempoxyz/mpp-specs | #275 | 2026-06-04 | Open | MPP extension registration for PQC/ZKP credential binding and the zero-knowledge attestation surface. |
| MPP | tempoxyz/mpp | #633 | 2026-05 | Closed | AlgoVoi multi-chain payment gateway proposed for the MPP services catalogue. Declined by maintainers (also #556, #402). |
| Solana Actions | sendaifun/solana-agent-kit | #561 | 2026-05 | Open | AlgoVoi as a plugin-blinks provider for any solana-agent-kit agent. |
| Solana docs | solana-foundation/solana-com | #1413 | 2026-05 | Open | AlgoVoi documented in the Solana Foundation x402 page. |
JCS canonicalisation substrate
The AlgoVoi-authored RFC 8785 canonicalisation substrate is the sole-AlgoVoi-authored discipline that downstream adopters validate against for receipt-format work. Full reference at /canonicalisation-substrate (v1) and /canonicalisation-substrate-v2 (v2, PQC-aware). The substrate has been cross-validated across eight independent JCS implementations in eight programming languages (Python, TypeScript, Go, Rust, Java, PHP, .NET, Ruby) with 192/192 byte-for-byte agreements across 24 vectors. See the full attestation record.| Artefact | Location | Status | What it anchors |
|---|---|---|---|
| Substrate docs page (v1) | /canonicalisation-substrate | Live | 5 normative rules, conformance vectors, 8-impl matrix (192/192 byte-for-byte agreements). |
| Substrate docs page (v2, PQC) | /canonicalisation-substrate-v2 | Live | PQC-aware additive successor; Falcon-1024, ML-DSA-65, ES256, Ed25519 cross-validated. |
| Conformance vector corpus | chopmob-cloud/algovoi-jcs-conformance-vectors | Live | Vector sets: action_ref_namespace_v0, action_ref_transactional_v0, compliance_receipt_v1, per_chain_envelope_v0. Runner harnesses for Python / JS / Go / Java. |
AP2 open_mandate_hash v0 | gist 1dca25fd | Live | 7 pair-structured vectors; AP2 issue #265. |
| JCS receipt + delegation vectors | gist 5f35eaa5 | Live | 14 vectors; receipt + bilateral-delegation canonicalisation. |
privacy_class v0 + v0.1 | gist 30bcbc71 | Live | 13 vectors; settlement-visibility attestation canonicalisation. |
per_chain_envelope v0 | gist e1bf4c9e | Live | 19 vectors across 7 chain families. |
| Canonicalisation discipline spec PR | x402#2453 | Closed 2026-06-02 | specs/canonicalisation.md, the AlgoVoi-authored normative canonicalisation discipline. Closed by core team; content lives as I-D draft-hopley-x402-canonicalisation-jcs-v1 and at /canonicalisation-substrate. |
| Cross-impl JCS runners in-tree | agentgraph-co/agentgraph#21 | Merged 2026-05-22 | Four AlgoVoi-authored single-file JCS runners (Python / JS / Go / Java) plus vectors and pair invariants in tests/cross-impl/. |
| Cross-validation: hybrid-PQC receipts | x402#2411 | Closed | AlgoVoi ran 4-impl JCS matrix against hybrid-PQC receipt cores; 16/16 byte-for-byte. Result retained at /canonicalisation-substrate-v2. |
| Cross-validation: action-ref-verify | x402#2398 | Closed | AlgoVoi ran 4-impl JCS matrix against work-binding vectors; 9/9 byte-for-byte including divergent-digest pin discipline. |
Conformance fixtures and reference artefacts
| Surface | Location | Status | What it anchors |
|---|---|---|---|
| Cross-extension v0 vector set | https://api.algovoi.co.uk/.well-known/cross-extension/v0.json | Live (schema 1.1) | Settlement / receipt / reputation adversarial-conformance envelope (5 attack classes), Ed25519-signed. Schema 1.1 adds a layer-type registry: the mandate_verification layer type is contributed by Christian Magorrian / A2CN Protocol (a2cn:record:v0.2); the dispute_resolution slot is pending Concordia. Composition envelope AlgoVoi-authored. |
| Compliance receipt JSON Schema | SchemaStore/schemastore#5726 | Merged 2026-05-23 | Draft-07 schema for the AlgoVoi compliance receipt; merged into the schemastore catalog. Every JSON-aware IDE that consumes the catalog now auto-validates AlgoVoi compliance receipts on open. Schema $id: https://json.schemastore.org/algovoi-compliance-receipt-v1.json. |
Reference implementations
Installable substrate primitives published to PyPI and npm with byte-for-byte cross-language parity. All packages Apache 2.0.| Package | PyPI | npm | What it ships |
|---|---|---|---|
algovoi-substrate | PyPI | npm | canonicalize, action_ref, composite_trust_query_hash, build_compliance_receipt, verify_audit_chain, transition_hash, build_transactional_action_chain. |
algovoi-settlement-attestation | PyPI | npm | Settlement attestation builder and verifier. Closed three-state enum (SETTLED / PENDING_FINALITY / REVERSED). |
algovoi-composite-trust-query | PyPI | npm | Multi-issuer composite trust verdict. Closed four-state enum. |
algovoi-cancellation-receipt | PyPI | npm | PSD2 Article 64 cancellation attestation envelope. |
algovoi-refund-receipt | PyPI | npm | PSD2 Article 89 refund attestation envelope. |
algovoi-rfc9421-verifier | PyPI | npm | RFC 9421 HTTP Message Signatures verifier for x402 and AP2 flows. |
algovoi-rfc9421-signer | PyPI | npm | RFC 9421 signer counterpart; produces Signature-Input and Signature headers. |
algovoi-substrate-pqc | PyPI | npm | PQC-aware substrate layer (v2 discipline). Falcon-1024, ML-DSA-65, ES256, Ed25519 cross-validated across three audit-grade PQC implementations. |
algovoi-plugin-semantic-kernel | PyPI | — | Semantic Kernel plugin: screen_recipient (ALLOW / REFER / DENY), create_payment, verify_payment, get_compliance_status. |
algovoi-plugin-autogen | PyPI | — | AutoGen / ag2 guardrail: AlgoVoiGuardrailCapability tool_call_before hook returning a categorical verdict, plus a payment function. |
algovoi-reference-agent | PyPI | npm | Reference A2A agent implementation demonstrating the full substrate stack end-to-end. |
algovoi-audit-verifier | PyPI | npm | CLI (algovoi-verify) and HTTP server for audit chain verification. |
algovoi-receipt-verifier | PyPI | npm | Standalone compliance-receipt verifier: JWS signature plus JCS-canonical re-hash, offline. |
algovoi-receipt-sentinel | PyPI | npm | Receipt sentinel: validates compliance receipts against the canonicalisation discipline and flags drift. |
algovoi-webhook-verifier | PyPI | npm | Verifies the X-AlgoVoi-Signature webhook header (v1 HMAC-SHA256, v2 HKDF-SHA256 / HMAC-SHA384). Offline-capable; 13 cross-validation vectors. |
algovoi-atb | PyPI | npm | Agent Trust Bench credential layer; full Falcon-1024 certificate verification via algovoi-atb[verify]. |
verify.algovoi.co.uk/action-ref — returns the RFC 8785 JCS canonical form and SHA-256 digest, verified byte-identical across 8 independent implementations.
Post-quantum and federation layer
The PQC credential-binding and cross-issuer federation I-Ds above are implemented by a commercial gateway layer (AlgoVoi Commercial License v1.0, not public PyPI):algovoi-federation-validator (composes independently-issued PQC ZKP credentials into a single federation token with no shared trust root), algovoi-zkp-receipt (Falcon-1024 signature covering payment-receipt and ATB ZKP credential fields together), and algovoi-atb-credential-verifier. The Apache-2.0 algovoi-substrate-pqc package (above) is the public PQC-aware canonicalisation substrate (Falcon-1024, ML-DSA-65, ES256, Ed25519 cross-validated). Full catalogue at /package-suite.
Data and registry
| Repository | PR | Status | What it adds |
|---|---|---|---|
| electric-capital/open-dev-data | #2874 | Merged | AlgoVoi MCP Server added to the Electric Capital crypto-ecosystems dataset under Algorand. |
Standards-discussion authorship
Where AlgoVoi authors or shapes spec text inside a protocol’s own RFC / working-group discussion.| Thread | Venue | AlgoVoi role | Status |
|---|---|---|---|
| x402#2326 | x402 Bazaar working group | Sole author of the privacy_class settlement-visibility spec surface; absorbed working-group critique across a five-commit arc | Closed; design on record |
| a2aproject/A2A#1858 | TaskState.PAUSED RFC | Contributed the PAUSED_BY_CLIENT(reason: compliance_review) binding tying the lifecycle state to the compliance-review outcome | Design input on record |
| AP2#262 | AP2 community | Seeded the open_mandate_hash v0 conformance vector set; JCS + four-state mandate patterns adopted by independent downstream implementors | v0 live; independent adopters converging |
urn:x402:), not vendor-scoped.
Agent framework integrations
| Registry / Framework | PR | Status | What it adds |
|---|---|---|---|
| Semantic Kernel | PyPI algovoi-plugin-semantic-kernel | Published | Kernel plugin exposing screen_recipient (categorical ALLOW / REFER / DENY), create_payment, verify_payment, get_compliance_status. |
| AutoGen / ag2 | PyPI algovoi-plugin-autogen | Published | tool_call_before guardrail hook (AlgoVoiGuardrailCapability) returning a categorical verdict, plus a function-style payment tool. |
| ElizaOS | npm @algovoi/plugin-elizaos | Published | Multi-chain A2A payment plugin: CREATE_PAYMENT_REQUEST, VERIFY_PAYMENT, CHECK_PAYMENT_STATUS actions plus an algovoi provider, across all 7 chains. Ships a full elizaos.plugin.json manifest. The npm package is live; the original upstream elizaos-plugins/registry submission predates that registry’s restructure. |
| MCP (any client) | PyPI algovoi-mcp / npm @algovoi/mcp-server | Published | The AlgoVoi MCP server (29 tools) for Claude Desktop, Claude Code, Cursor, Windsurf, or any MCP client. uvx algovoi-mcp / npx -y @algovoi/mcp-server. |
Wallet integrations
| Repository | PR | Status | What it adds |
|---|---|---|---|
| TxnLab/use-wallet | #434 | Open | AlgoVoi added as a wallet provider in the Algorand use-wallet library. |
| webdevalgo/NomadexAmmPublic | #1 | Open | AlgoVoi wallet support added to Nomadex AMM. |
Curated lists and ecosystem indexes
These are recognition entries, but they signal AlgoVoi’s footprint across adjacent open-source communities. Status labels are GitHub-accurate; list maintainers merge on their own cadence and some decline.x402, AP2, and agent-payments ecosystem
A2A ecosystem
| Repository | PR | Status |
|---|---|---|
| pab1it0/awesome-a2a | #51 | Merged |
| sing1ee/a2a-directory | #23 | Merged |
| ai-boost/awesome-a2a | #86 | Open |
MCP and Web3 lists
| Repository | PR | Stars | Status |
|---|---|---|---|
| punkpeye/awesome-mcp-servers | #5109 | 86,075 | Merged |
| TensorBlock/awesome-mcp-servers | #438 | 638 | Merged |
| demcp/awesome-web3-mcp-servers | #80 | 608 | Open |
| badkk/awesome-crypto-mcp-servers | #59 | 133 | Open |
| royyannick/awesome-blockchain-mcps | #56 | — | Open |
Chain-specific lists
AI framework and security lists
| Repository | PR | Notes | Status |
|---|---|---|---|
| TalEliyahu/Awesome-AI-Security | #69 | Agent Trust Bench (adversarial payment-agent security) | Merged |
| crewAIInc/awesome-crewai | #60 | CrewAI payment-gate adapter | Open |
| ganarajpr/awesome-dspy | #20 | DSPy adapter | Open |
| ottosulin/awesome-ai-security | #233 | Agent Trust Bench | Open |
| UKGovernmentBEIS/inspect_evals | #1732 | Agent Trust Bench eval registration | Open (draft) |
| lukecav/awesome-woocommerce | #10 | WooCommerce crypto gateway plugin | Open |
Why we make this list public
Most payment providers ship a marketing site. The thing that distinguishes a real protocol participant is the public commit history, the PRs that maintainers can review and merge, and the contributions that show up upstream. We list all of these in one place — merged, open, and declined alike — so anyone evaluating AlgoVoi (a prospective tenant, a regulator, an investor, a competitor) can verify the contribution footprint without having to take our word for any of it. Where a maintainer declined a PR, we say so and point to where the work now lives. If you are a maintainer of an ecosystem repo we should be listed in and are not, tell us.See also
- Changelog for the AlgoVoi-side timeline
- Adopters for parties pinning
canon_version: jcs-rfc8785-v1in publicly-citable artefacts - Canonicalisation substrate for the full v1 discipline reference