CoolFace
Datasetpublic

MarkovianProtocol/bitcoin-anchored-ai-provenance

Bitcoin-Anchored AI Provenance Receipts Status (July 2026): this corpus is from the protocol's v1 "chain" era and is kept as a historical artifact. Every row remains independently verifiable: the OpenTimestamps proofs are portable and check against Bitcoin with the stock ots client, and the verify_url endpoint is still live. The protocol's current architecture is a C2SP transparency log cosigned by independent witnesses (log.markovianprotocol.com, browser verification at… See the full description on the dataset page: https://huggingface.co/datasets/MarkovianProtocol/bitcoin-anchored-ai-provenance.

sourceHugging Faceapache-2.0updated 2mo agoView on Hugging Face
0likes23downloads
Dataset Card

Bitcoin-Anchored AI Provenance Receipts

Status (July 2026): this corpus is from the protocol's v1 "chain" era and is kept as a historical artifact. Every row remains independently verifiable: the OpenTimestamps proofs are portable and check against Bitcoin with the stock ots client, and the verify_url endpoint is still live. The protocol's current architecture is a C2SP transparency log cosigned by independent witnesses (log.markovianprotocol.com, browser verification at markovianprotocol.com/trace.html). The zk_commitment field is a legacy of the v1 design and plays no role in verification.

A corpus of real provenance receipts committed to the Markovian chain and anchored to Bitcoin. Every row is an actual on-chain record, and every row is independently verifiable, with no trust in the producer. To the best knowledge of the authors this is the first public dataset of Bitcoin-anchored provenance receipts for AI-agent and model outputs.

Each receipt proves that a specific output existed at a specific time. It does not claim the output is correct. Provenance, not truth.

What is in it

The corpus spans the standards that agents already use. Labels include receipts produced through A2A, C2PA, CloudEvents, W3C Verifiable Credentials, ERC-8004, and x402, alongside TRACE lineage nodes (model, data, policy, input, agent decision), a DeepProve inference node, and deterministic-replay resolution and convergence-call records.

Schema

Each line in provenance.jsonl is one receipt:

fieldmeaning
merkle_rootthe commitment root, and the verification key
data_hashSHA-256 of the committed content
zk_commitmentBN128 Pedersen commitment over the same bytes
markovian_block_heightthe Markovian chain commit height. This is NOT a Bitcoin block height
labela short description of what was stamped
data_previewa truncated preview of the committed content
stamped_atcommit timestamp (UTC)
walletanonymous stamper identity (keyless)
mkv_burnedprotocol units burned. 0 means free, keyless stamping
verify_urlhttps://api.quantsynth.net/verify/<merkle_root>
bitcoin_ots_urlthe portable OpenTimestamps proof for the root

How to verify a row (no trust required)

  1. 1.Open verify_url to confirm the root and its commitment on the chain.
  2. 2.Fetch bitcoin_ots_url and verify the .ots against Bitcoin block headers with the stock ots client. The trust root is Bitcoin, not the issuer, and the check needs no Markovian endpoint.

markovian_block_height is the immediate, low-latency chain commit. The dispute-grade Bitcoin anchor is the OpenTimestamps proof. A freshly stamped root is calendar-committed and upgrades to a confirmed Bitcoin block within roughly one to two hours.

Uses

  • —Study a real, cross-standard provenance receipt format.
  • —Build and test a provenance verifier against genuine on-chain data.
  • —Benchmark tamper-evidence and independent-verification tooling for agent outputs.

Source

Markovian Protocol: markovianprotocol.com. Live MCP server: https://api.quantsynth.net/mcp/. License Apache-2.0.

Update, July 2026 — beyond agent stamps

The corpus now includes real-world Bitcoin-anchored provenance records produced with the open audit-anchor tooling and the C2SP tlog-witness at witness.markovianprotocol.com:

  • —a canonicalised CamFlow whole-system provenance graph (Bitcoin block 957400)
  • —a GNU Guix channel checkpoint (Bitcoin block 957403)
  • —an AI decision-receipt (decision-receipt/v0.1) whose evidence reference binds to an eval-result content root

Each is canonicalised with RFC 8785 (JCS), committed by SHA-256, and anchored to Bitcoin via OpenTimestamps. Every record is independently verifiable offline against Bitcoin block headers, with no operator in the trust path.