> ## Documentation Index
> Fetch the complete documentation index at: https://docs.algovoi.co.uk/llms.txt
> Use this file to discover all available pages before exploring further.

# AlgoVoi vs Unnamed

> An open, reproducible comparison of the AlgoVoi agentic payments substrate against a current substrate. Names no implementation, states parity plainly.

> The most interoperable and most complete agentic-payments substrate: the only one with a published cross-language byte-for-byte conformance corpus and post-quantum signing, on an open RFC 8785 floor anyone can verify.

This compares the AlgoVoi substrate against a representative current substrate (unnamed). It names no implementation: every row is something you can reproduce from public artifacts. Where the two are at parity, this says so plainly. The point is not that other substrates are broken; it is that AlgoVoi proves more, covers more, and signs for longer.

## The shared floor, stated honestly

Both substrates canonicalise JSON with **JCS (RFC 8785)** and address content with `"sha256:" + lowercase-hex(sha256(JCS(value)))`. On that floor they are equivalent by design, and that is the right floor: it is an open IETF standard. So this is **not** a determinism contest. A conformant JCS implementation in any language produces the same bytes. The difference is everything built on the floor, and whether the interoperability is **proven** rather than asserted.

## Dimension comparison

| Dimension | AlgoVoi | Unnamed (typical current substrate) |
| :- | :- | :- |
| Canonicalisation floor | JCS (RFC 8785), `sha256:` content digest | JCS (RFC 8785), `sha256:` content digest (parity) |
| Cross-language conformance proof | **Published, reproducible: 1226/1226 byte-for-byte agreements across 10 independent JCS implementations in 10 languages** (Python, JavaScript, Go, Rust, Java, PHP, C#/.NET, Ruby, Elixir, Kotlin), including the RFC 8785 author's own Java implementation | Reference implementation only; cross-language byte-for-byte conformance not commonly published |
| Adversarial input agreement | 96/96 byte-for-byte on adversarial inputs, plus an input-bounds reject gate before canonicalisation | Not commonly published |
| Post-quantum signing | **Hybrid Falcon-1024 + ML-DSA-65** envelopes, alongside classical | Classical only (EIP-712 secp256k1 / JWS) |
| Signature survival through proxies | RFC 9421 proxy-chain verified 8/8 across 8 implementations through a 3-hop TLS re-terminating chain | Not addressed |
| Receipt lifecycle coverage | Full stack: admission, settlement, cancellation, refund, composite verdict, payment evidence frame, plus signed decision and audit chains | Typically a subset (identity or settlement envelope) |
| Open corpus | Apache-2.0 open corpus ([details](/canonicalisation-substrate)), plus a one-command self-contained validator | Varies; a full open conformance corpus is uncommon |
| Standards anchoring | IETF Internet-Drafts for the constructions | Varies |
| Scale behaviour vs naive substrates | \~100% identifier retention at 1,000,000 operations, \~118k ops per second single core | Coarse-timestamp or bare-concat substrates drop \~98 to 99.9% and collide at scale (does not apply to JCS peers, which share the floor above) |

## Open tooling you can deploy today

The substrate is not a slide; it is shipped, open, and installable from PyPI and npm right now. Every package below has a published version number; the Unnamed column is blank because a representative current substrate publishes no equivalent versioned package for these layers. Versions are read live from the registries.

**Substrate and hardening**

| Package | What it does | AlgoVoi version | Unnamed |
| :- | :- | :- | :- |
| `algovoi-substrate` | L1 JCS (RFC 8785) canonicalisation, `action_ref`, `sha256:` content digest | 0.4.0 | |
| `algovoi-substrate-pqc` | JCS + post-quantum integration (signature-algorithm open-enum, cross-impl) | 0.1.2 | |
| `algovoi-substrate-guard` | deterministic input-bounds / DoS reject gate that runs before canonicalisation (`profile_ref`) | 0.1.0 | |

**Decision and policy (lite tiers)**

| Package | What it does | AlgoVoi version | Unnamed |
| :- | :- | :- | :- |
| `algovoi-spend-guardrail-lite` | pre-payment ALLOW / DENY decision bound to agent, mandate and policy (`guardrail_ref`) | 0.1.0 | |
| `algovoi-compliance-gate-lite` | no-PII compliance ALLOW / REFER / DENY verdict bound to the policy in force | 0.1.0 | |
| `algovoi-policy-binding` | version-provable, rotation-detectable policy-snapshot binding | 0.1.0 | |

**Receipt and evidence formats**

| Package | What it does | AlgoVoi version | Unnamed |
| :- | :- | :- | :- |
| `algovoi-pef` | Payment Evidence Frame: transport-agnostic wrapper with a deterministic `frame_id` | 0.1.2 | |
| `algovoi-settlement-attestation` | multi-chain settlement attestation format | 0.1.1 | |
| `algovoi-refund-receipt` | refund receipt format | 0.1.1 | |
| `algovoi-cancellation-receipt` | four-state mandate cancellation receipt format | 0.1.1 | |
| `algovoi-composite-trust-query` | verifier-side composite trust-query response format | 0.1.1 | |
| `algovoi-retention-chain` | self-verifiable audit chain linking payment receipts | 0.3.0 | |

**Verifiers, signers and validators**

| Package | What it does | AlgoVoi version | Unnamed |
| :- | :- | :- | :- |
| `algovoi-rfc9421-verifier` | RFC 9421 HTTP Message Signatures + RFC 9530 content-digest verifier | 0.3.0 | |
| `algovoi-rfc9421-signer` | RFC 9421 + RFC 9530 Ed25519 signer | 0.1.0 | |
| `algovoi-audit-verifier` | offline selective-disclosure audit-bundle verifier | 0.1.2 | |
| `algovoi-receipt-verifier` | offline JWS compliance-receipt verifier | 0.1.1 | |
| `algovoi-webhook-verifier` | webhook signature verifier (HMAC-SHA256 / HKDF) | 0.1.0 | |
| `algovoi-receipt-sentinel` | tenant-side tamper / replay / scan / burst detection | 0.1.0 | |
| `algovoi-validate` | offline validator for signed compliance evidence (auto-detects signature type) | 0.1.1 | |
| `algovoi-reference-agent` | reference agent emitting a settlement-attestation-v1 receipt | 0.1.0 | |

**Agent-framework integrations and tooling**

| Package | What it does | AlgoVoi version | Unnamed |
| :- | :- | :- | :- |
| `algovoi-plugin-crewai` | payment guardrail provider and tools for CrewAI | 0.1.0 | |
| `algovoi-plugin-autogen` | payment guardrail capability for AutoGen / ag2 | 0.1.2 | |
| `algovoi-plugin-semantic-kernel` | payment and compliance plugin for Semantic Kernel | 0.1.1 | |
| `@algovoi/plugin-elizaos` (npm) | AlgoVoi plugin for the elizaOS agent runtime | 0.1.1 | |
| `algovoi-mcp` / `@algovoi/mcp-server` | MCP server: payment links, verify payments, probe endpoints | 1.7.0 | |
| `algovoi-atb` / `@algovoi/atb` | Agent Trust Bench client (175 adversarial x402 payment profiles) | 0.1.4 | |
| `@algovoi/use-wallet-algovoi` (npm) | wallet hook for AlgoVoi web integrations | 1.0.1 | |
| `n8n-nodes-algovoi` (npm) | n8n workflow nodes for AlgoVoi | 1.0.0 | |

Every package above is published and versioned on PyPI and npm (a few adapters are npm-only, marked). Licences: the substrate, hardening, decision, receipt, verifier and validator layers are Apache-2.0; the agent-framework plugins are dual-licensed (Apache-2.0 or AlgoVoi-Commercial); the runtime adapters are MIT. The Unnamed column stays empty: there is no equivalent versioned package to cite.

```bash theme={null}
pip install algovoi-substrate algovoi-substrate-guard algovoi-spend-guardrail-lite algovoi-pef
npm install @algovoi/substrate @algovoi/substrate-guard @algovoi/spend-guardrail-lite @algovoi/pef
```

A representative current substrate ships a reference implementation; AlgoVoi ships the whole stack, open, across two language ecosystems.

## What this claims, and what it does not

* **Claims:** AlgoVoi is the most interoperable substrate (the cross-language conformance is published and reproducible, not asserted), the most complete (full receipt lifecycle plus decision and audit chains), and the most future-proof (post-quantum signing today). All of it is open and verifiable.
* **Does not claim:** that a JCS-based peer's canonical bytes are wrong. On the RFC 8785 floor they are equivalent. Claiming otherwise would be false and is not the basis of this comparison.

## Verify it yourself

The full open corpus and the ten-language cross-validation harness live in the conformance-vectors repository (see the [canonicalisation substrate](/canonicalisation-substrate) page for current counts), and the reference package reproduces every vector with no install and no network:

```bash theme={null}
python validate.py            # 8/8 vectors reproduce byte for byte
```

* Conformance corpus and attestations: [`chopmob-cloud/algovoi-jcs-conformance-vectors`](https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors)
* Reference package: [`algovoi-pef`](https://pypi.org/project/algovoi-pef/) (PyPI), [`@algovoi/pef`](https://www.npmjs.com/package/@algovoi/pef) (npm)
* IETF Internet-Draft: [`draft-hopley-x402-payment-evidence-frame`](https://datatracker.ietf.org/doc/draft-hopley-x402-payment-evidence-frame/)

Figures are from corpus manifest v0.38.0. The 1226/1226 cumulative is the directly-executed ten-implementation total (cumulative through 2026-07-21); the 96/96 adversarial-input agreements are counted separately.

***

## Beyond the open tier

The open packages above are the foundation. The commercial tier, [Substrate 2](/substrate-2), adds post-quantum signing (Falcon-1024 + ML-DSA-65) on every receipt, offline-verifiable evidence chains for regulated industries, decision enforcement engines (Spend Guardrail, Compliance Gate, Agent Passport), and a full regulated-records suite, all under one commercial licence. Byte-identical with the open substrate: anything built against the open tier interoperates with Substrate 2 unchanged.

[View the Substrate 2 commercial suite](/substrate-2).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.