Trust Layer
Markovian Protocol / Bitcoin Timestamping

OpenTimestamps Live

OpenTimestamps is an open standard for Bitcoin timestamping, maintained by Peter Todd. Markovian does not compete with it, Markovian consumes it. Every root is submitted to the public OTS calendars and carries a standard .ots proof, so "Bitcoin-anchored" stops being a claim on this site and becomes an artifact anyone can verify against Bitcoin itself, with no trust in Markovian.

COMMIT roots, anchored through OpenTimestamps

A stamped record becomes a leaf in the public transparency log at log.markovianprotocol.com, hashed as RFC 8785 canonical JSON under SHA-256, and the log's Merkle structure produces a root. Markovian submits that root to the public OTS calendars, which batch it into their own Merkle tree and write a single root to Bitcoin. The returned proof links the Markovian root through that tree to a Bitcoin block. Hashes are sent, never the data.

// Markovian submits a COMMIT's merkle_root to the public OTS calendars stamp(merkle_root) // alice, bob, finney, catallaxy // each calendar batches it into a Merkle tree and writes ONE root to Bitcoin. // a .ots proof links: your root -> aggregated tree -> Bitcoin block. // anyone verifies against Bitcoin, no calendar, no Markovian, no trust ots verify <merkle_root>.ots

Provenance, not truth

An OpenTimestamps proof establishes that data existed before a Bitcoin block time. It commits to a hash and nothing more. It makes no claim about whether the data is correct, which is exactly the Markovian claim. Provenance, not truth, holds on both layers.

The OTS proof is a second, independent anchor sitting beside the witnessed transparency log record. The two are adversary-disjoint: an OTS proof can be checked against Bitcoin L1 with stock tooling even if Markovian is offline.

A real proof, verifiable against Bitcoin

The record below is a real COMMIT root submitted to all four public OTS calendars. The .ots downloads straight from the public verifier and checks with the unmodified ots client. The Bitcoin attestation attaches at the next calendar aggregation block; the proof upgrades automatically.

OpenTimestamps Proof, Bitcoin Mainnet
anchorBitcoin mainnet (OP_RETURN, Merkle-aggregated)
calendarsalice.btc · bob.btc (opentimestamps.org) · finney (eternitywall) · catallaxy
commit merkle_rootab1f55694ab6078fcccc6526ef401d7596b446029d04d69a53d6fb4a146e0c61
verify commandots verify ab1f5569....ots
statuscalendars committed bitcoin attestation upgrading

Why Markovian stands on OpenTimestamps

OpenTimestamps already does Bitcoin timestamping for free, accountless, with a decade of trust behind it. Competing with it would be a losing fight. Consuming it borrows Bitcoin's neutrality and that established trust, and lets Markovian add what OTS does not carry: the canonical markovian-provenance/v1 record, inclusion in a transparency log cosigned hourly by seven independent witnesses, and native interop with the other doors, W3C VC, A2A, MCP, ERC-8004, and C2PA.

The same record, two independent checks: the witnessed transparency log for the structured record and the doors, OpenTimestamps for a stock-verifiable Bitcoin proof.

Check it without trusting this page

Download the .ots and run the unmodified OpenTimestamps client against Bitcoin. The public verifier returns the provenance record behind the same root, with no account and no dependency on this site.