One BSV anchor, inside the receipt formats your auditors already read.
Five live mainnet samples for the
chain-anchor/v1
scheme — an Agent Action Receipt, an RFC 3161 timestamp, a
C2PA-credentialed image, a Visa TAP request — each
carrying its own inclusion proof so an auditor with just one
receipt can verify the on-chain commitment independently,
without seeing the others. Every leaf and root reproduces
byte-for-byte from the JSON in this directory; every txid below
is live on BSV mainnet.
Start here: RECEIPTS.md — full reproduction recipe, all five samples in one document, pure-stdlib verification snippets.
What’s in this directory.
AAR batch
Four Agent
Action Receipts under one BSV anchor. Each carries a
chain-anchor/v1 evidenceRef with
its merkle leaf + inclusion proof.
Dual-attest (RFC 3161 + BSV)
The same AAR receipt with two independent
evidenceRef entries: a real RFC 3161 token
from freetsa.org alongside the BSV
chain-anchor entry. Either path verifies on its own.
Cross-domain
Three real public artifacts under one BSV anchor: a mainnet Ethereum block hash, a HuggingFace README at a pinned commit, and a C2PA-credentialed JPEG.
C2PA-credentialed image
The same BSV anchor surfaced as a
com.chain-anchor assertion inside a real C2PA
manifest on a signed JPEG. c2patool reads the
manifest end-to-end; the chain-anchor assertion confirms
independently against the on-chain root.
Visa Trusted Agent Protocol
A TAP-signed agent request batched with its registration record under one BSV anchor. The TAP signature verifies against Visa’s ECDSA path; the chain-anchor leaf verifies against BSV. Two independent trust roots over the same agent action.
For implementers.
- Scheme spec:
/spec-chain-anchor. - Wire format (28-byte MBNT header + TLV section all anchor
categories share):
/spec-mbnt. - Machine-readable scheme registry:
/schemes.json. - Sibling sample directory (selective row-reveal):
/samples/merkle-row/RECEIPTS.md.