Markovian Protocol

We check what organisations say about their own systems, using their own public data. Every result, script and reply is pinned in a log nobody can rewrite, us included.

36 claims checked · 17 didn’t hold · 8 organisations answered or fixed what we found

---

— records · — witnesses signing now

Measurements

9 seals from 8 organisations, each for answering on the record or fixing what we measured. Round trips.

Of 36 published claims we checked, 17 did not hold and 19 held. We have sent questions on 19 of them; 8 have had an answer. All measurements · Registry · Know a claim that doesn’t add up? Send it to us.

How we work

1. Quote the claim. An organisation’s own words about its system, copied from its own page and saved.
2. Measure it again. Our own code against its own public data. Every script and data file is published.
3. Ask, and print the answer. The questions go to whoever can fix it; replies go on the page in full, and answers and fixes earn a seal.

Every paper is stamped into the log below when it’s published, so anyone can show later that it hasn’t been quietly changed. More on method.

A receipt, checked live

Log

Log name	markovianprotocol.com/log
Public key	markovianprotocol.com/log+0302c6c8+ATkpOWo95UuEiW2EhNZAol4f0CS8hMluJfPcTSzrr03v
Records	—
Witnesses signing now	—
Latest Bitcoin stamp	—
Listed on	witness-network.org (testing list)

Check it yourself

• Any record, fully offline: download /proof/{i} and the policy file, and you don't need the network after that.
• In your browser, check all seven witness signatures on the current state: verify live
• One record in your browser, from its hash to the Bitcoin block that covers it: verify a record
• With a script that has the witness keys built in: verify_checkpoint.py
• Look up a record by its hash: GET https://markovianprotocol.com/anchor/{sha256-hex}
• Check a Bitcoin stamp with the standard ots tool, no trust in us needed: anchor proofs
• Our monitor, which re-checks the whole log every hour from a separate machine: the log monitor

Witness policy

A state counts as witnessed once at least 4 of our 7 witnesses, run by 6 different operators, have signed it. We copied each witness's key from its operator's own page. A witness signature means our history was never rewritten. It doesn't mean any record is true. Machine-readable: /policy · for people: witness-policy.

We also run a witness

Our witness, witness.markovianprotocol.com, checks and signs other people's transparency logs, for free: get witnessed.

Notarize anything

h=$(sha256sum yourfile | cut -c1-64)
curl -X POST -d "sha256:$h" https://log.markovianprotocol.com/submit

Free, no account. You send a file's fingerprint (its SHA-256 hash). We store those 32 bytes, and you keep the file. You get back a receipt with the links to prove it later. Or drop a file in the browser: it's hashed on your machine and never uploaded. AI agents can use the MCP server at https://api.markovianprotocol.com/mcp/ (tools: notarize, stamp, verify, trace).

For developers

Base URL https://log.markovianprotocol.com — every path below starts there.

GET /checkpoint	the latest state, signed by us and the witnesses
GET /checkpoint/unwitnessed	the newest state, signed by us only; the witnesses catch up within the hour
GET /leaf/{i}	one record
GET /leaves?start=&end=	many records
GET /tile/…	the whole log in tiles, for copying it bit by bit (C2SP tlog-tiles)
GET /inclusion?leaf=&size=	proof a record is in the log (RFC 6962)
GET /consistency?old=&new=	proof the log only grew between two sizes
GET /receipt/scitt/{i}	a SCITT receipt for a record (RFC 9942)
GET /proof/{i}	everything you need to check a record offline, in one file (C2SP tlog-proof)
GET /policy	which witnesses we trust, machine-readable (C2SP tlog-policy)
POST /submit	notarize a file's hash and get a receipt (10 an hour per address)
GET /anchor	the hourly Bitcoin stamps (OpenTimestamps), each checked against real Bitcoin blocks