How it works, and its limits

Existed By is a free front end to OpenTimestamps, an open standard for anchoring a file's fingerprint in Bitcoin. This page explains every step, what the result proves, and whom you're trusting.

1. The fingerprint

Your browser reads the file in pieces and computes its SHA-256 hash (FIPS 180-4), a 256-bit number written as 64 hexadecimal characters. Changing a single byte of the file changes the fingerprint completely, and nobody knows how to make a different file with the same fingerprint. Hashing happens in a background thread on your device; a 2 GB video takes seconds to a minute depending on the device.

2. The calendars

The page appends 16 random bytes to the fingerprint, hashes the result again, and sends only that 32-byte value to three public OpenTimestamps calendars run by independent operators (a.pool.opentimestamps.org, b.pool.opentimestamps.org, a.pool.eternitywall.com). Because of the random bytes, a calendar can't tell which file it is, or even whether two submissions are the same file.

Each calendar answers at once with a receipt: the first steps of a path from your value to a hash it promises to anchor. Every so often, usually within a few hours, each calendar combines everything it has received into a single hash and puts it in a Bitcoin transaction. Several calendars means the proof completes even if one of them disappears.

3. Bitcoin

Once that transaction is in a block, the calendar can supply the rest of the path: from your value, through the transaction, to the block header's Merkle root. That makes the proof complete. A complete proof no longer depends on any calendar, or on this site: only on Bitcoin's block chain.

The check page verifies a complete proof by fetching the block header at the stated height from two block explorers (Blockstream and mempool.space), checking that both give the same header, that the header carries real Bitcoin proof of work, and that the proof's path leads exactly to its Merkle root. The time shown is the block's timestamp. Bitcoin only requires block times to be roughly right: they are accurate only to within an hour or two.

What a timestamp proves

What it doesn't prove

So the useful claims are about order: “this footage existed before that manipulated version appeared”, or “this file is unchanged since the day of the event”. For capture details (device, edits, signer) look at Content Credentials, which work well alongside a timestamp.

Whom you're trusting

Check for yourself that your video isn't uploaded

Every page carries a Content Security Policy that your browser enforces. It allows scripts only from this site and network requests only to the calendars and block explorers listed in it:

default-src 'none'; script-src 'self'; worker-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; media-src 'self' blob:; connect-src https://a.pool.opentimestamps.org https://b.pool.opentimestamps.org https://a.pool.eternitywall.com https://alice.btc.calendar.opentimestamps.org https://bob.btc.calendar.opentimestamps.org https://finney.calendar.eternitywall.com https://btc.calendar.catallaxy.com https://blockstream.info https://mempool.space; form-action 'none'; base-uri 'none'

To watch it, open your browser's developer tools (F12, or Cmd+Option+I on a Mac), choose the Network tab and stamp a file. You'll see three small requests to the calendars, 32 bytes each, and nothing else. No accounts, no cookies, no analytics. Your files are fingerprinted on your device and never uploaded.

Check links

A check link carries the whole proof, plus the file name and size you stamped, after the # in the address. Browsers don't send that part to any server. Anyone with the link can see the file's name, size and fingerprint, so share it where you'd share the file's name.

Contact

Bugs and questions: open an issue on GitHub (issues are public).