Skip to main content
AlgoVoi exists inside an open-protocol ecosystem (x402, MPP, AP2, A2A, Solana Pay, Algorand, VOI, Stellar, Hedera, Base, Tempo). The fastest way to evaluate whether a payment provider is a real participant or a marketing site is to look at what they have contributed back upstream. Every link below is a public pull request on a public repository. Each one is verifiable from a browser, no AlgoVoi account needed. Status labels are GitHub-accurate as of the date shown and reflect the real merge/close state, including PRs a maintainer declined.

​
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.

​
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 against x402-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.

​
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.

​
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 880/880 byte-for-byte agreements directly executed (cumulative as of 2026-06-18). See the most recent attestation.

​
Conformance fixtures and reference artefacts

​
Reference implementations

Installable substrate primitives published to PyPI and npm with byte-for-byte cross-language parity. All packages Apache 2.0. Public verifier endpoint: 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

​
Standards-discussion authorship

Where AlgoVoi authors or shapes spec text inside a protocol’s own RFC / working-group discussion. The throughline: AlgoVoi contributes converged spec text and deterministic conformance artefacts, scoped as seeds the protocol communities own long-term, not vendor-proprietary surfaces. URN rows are protocol-scoped (urn:x402:), not vendor-scoped.

​
Agent framework integrations

​
Wallet integrations

​
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

​
MCP and Web3 lists

​
Chain-specific lists

​
AI framework and security lists

​
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