MarkovianProtocol/markovian-provenance
Markovian Provenance
Prove that an AI agent or model output existed at a time, verifiable by anyone against Bitcoin, with no trust in the producer. Existence and ordering only. It complements signing and provenance, it does not replace them, and it is not a coin.
What it does
A record is canonicalised (RFC 8785), committed by SHA-256, and anchored to Bitcoin via OpenTimestamps. A third party who was not there confirms the record existed before a given Bitcoin block, offline, against block headers alone.
This Space is also an MCP server: tools markovianprovenancestamp and markovianprovenanceverify at /gradio_api/mcp/.
The wider stack
- A live C2SP tlog-witness at witness.markovianprotocol.com that cosigns another log checkpoints, so a split view is refused by an independent party.
- Real provenance records anchored to Bitcoin and public in audit-anchor: a canonicalised CamFlow provenance graph (block 957400), a Guix channel checkpoint (block 957403), and an AI decision-receipt.
- A dataset of Bitcoin-anchored provenance receipts: bitcoin-anchored-ai-provenance.
- The canonicalisation substrate: canoncheck, RFC 8785 with matching Python and JS.
Existence, not truth. The anchor proves a record existed and its order in time. It says nothing about whether the content is correct.
More at https://markovianprotocol.com
