Skip to main content
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

​
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 Decision and policy (lite tiers) Receipt and evidence formats Verifiers, signers and validators Agent-framework integrations and tooling 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.
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 page for current counts), and the reference package reproduces every vector with no install and no network:
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, 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 or acquisition details.