Verify It Yourself | Apache 2.0 | the whole agentic-payment substrate, verified offline in one command

[chopmob-cloud]

We have published an offline conformance harness for the AlgoVoi agentic-payment substrate, Apache 2.0. It runs the entire vector corpus plus an end-to-end lifecycle composition proof, and tells you whether your implementation reproduces the canonical bytes.

git clone https://github.com/chopmob-cloud/algovoi-jcs-conformance-vectors
cd algovoi-jcs-conformance-vectors/composition
pip install -r requirements.txt    # full 24/24; or: pip install algovoi-substrate for the JCS+SHA-256 core + composition
python verify_corpus.py

Exit code 0 means every canonical byte was reproduced on your machine. No servers, no accounts, no issuer callbacks. SHA-256 and a JSON parser are the whole trust model for the core; the four signature sets add Ed25519 / Falcon-1024 / RFC 9421 and are flagged with their install command rather than failing.

What is new here is the composition. Most conformance suites prove that individual primitives hash correctly. This one also proves they link: the full regulated lifecycle composes into one self-verifiable chain, using published vectors only, with no new vector and no new hashing primitive.

action_ref -> transition_hash (COMMITTED) -> settlement_ref -> retention_chain_ref -> binding_ref

The four inputs to the settlement-action binding are byte-identical to the published outputs of the four upstream sets, and recomputing the binding reproduces the published reference:

binding_ref = sha256:7dc4a2bf62b3c5eabd10fc875ff7fc10f188666f15838c4a51464cc72e80f6ca

Spec: draft-hopley-x402-retention-chain, Section 7. Vectors and harness: chopmob-cloud/algovoi-jcs-conformance-vectors. The constructions satisfy the recording and audit obligations of MiCA Article 80, DORA Article 14, and AMLR Article 56. Key constructions are cross-validated byte-for-byte across eight independent implementations (for example the settlement-action binding set: 48/48, six vectors across Python, Node, Ruby, PHP, Go, Rust, Java, .NET). The corpus also pins per-chain receipt envelopes across seven chain families (Algorand, VOI, Hedera, Stellar, Base, Solana, Tempo) in per_chain_envelope_v0, so chain coverage is something you verify, not something we assert.

This is L1 substrate work, maintained and kept stable. If you are building an L2 on top, a mandate lifecycle, a settlement flow, a receipt family, an agent framework, this is the tool that lets you prove you are byte-compatible with everyone else building on the same ground. We maintain the L1 and we help you build the L2. The single condition is attribution: keep the NOTICE when you redistribute, and attributed work is taken into account as the substrate evolves.

If you want help verifying your output against the canonical bytes, the offer is genuine: chopmob@gmail.com. That is a genuine offer, not a pitch.