Web-page notarized

A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one

Rendered page — archived HTML, sandboxed · click to collapse

Html-only render: no scripts or original assets, so it may look unstyled. Not the live page; not endorsed by bsv.cx. ⤢ full screen

off by default; remembered for future views
captured2026-08-31T08:20:04.434Z
manifest sha256d34980d87ec904da43a08c1c9f0521e73331a73dbdc34121fe85ac4c4ec71baa
html sha256d999a04ade54113ce166df20545404bba82b2d8dc86074388bebd25011172254
proof⛓ timestamped on-chain
txid17987ed8b48cecdffbe04fe76af8673665d759c0bb0572283149daa10678fc3b
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 964,683 · 10,086 confirmations
SPV proof & how to re-verify it yourself
block height964683
block merkle root01cf31dbef640089790bafa9d55b60b14465a8c8ea012e074c51bb62be7d8f93
tx index925
branch (11)ececa2700894a6ceaa0d245148287b38fe3d2b44c19e0c178f6c9cdc9af4bcc4 04c8c17c8ae368022b04c4579897a8deb8f242e880e25439b84d56bcda2dabe0 3fb7256ea4ad6dd669c6c9e44d5d146b5bea32eebac200cd4c491c604e87f40c fbe01dc5e6cde99877a38ddde7120dc2a95ba03055431becf987f7c3bd4c5206 9e227754ef5f091ae07c6e11515b29be19fc51a1b89825026daa787c8e769da4 89eca42d2061e8062df9a14704522ca5bdfd37a852b01604ce5bd797ced507f2 1129a2fc18107dc64ac09aed32ec165aa6be3a4bba000bd7ed9dc010640acd60 c8a3352ec055644fd5aed39961989efc62b16cba9a3dc47ae2e1c296f1518912 62bdf5ed75325598ee8a249e3e0add0f43f256609e3147af3b398786cd2cb2ba 99dceece5edd2260b8e736093d4362f1066d230da4bbf492fd5f1feb5c5ed2a7 aab5a5d1cc615872368b7b4434bf3b2a757587db5ef834c844b7c3fbe8fad6ec

Trust no one: double-SHA256 the txid up this branch — at each level your hash goes left when index is even, right when odd, halving the index each step — to get the block Merkle root, then confirm that root is the header at height 964683 on any block-header source you trust. We verified it against headers we run ourselves; you verify against yours — no explorer, and no bsv.cx, in the trust path.

Prefer to check it against a second independent source? Paste these fields into our public verifier (POST /spv/verify) — it folds the root itself and checks it against headers we sync, so it can only ever make a bad proof fail.

Or take it to your own tools in the ecosystem standard format: BEEF (BRC-62, tx + proof) · BUMP (BRC-74, path only). Any @bsv/sdk client verifies these with no bsv.cx-specific code — Transaction.fromHexBEEF(hex).

keep your copybsv.cx stores this snapshot as a convenience and does not guarantee to host it forever. Download your own copy now — with it you can prove this timestamp yourself, indefinitely, without depending on us.

⬇ page HTML · manifest JSON

Save both. The manifest's SHA-256 is the anchored id, and it binds the HTML hash — so from your saved files you can recompute every hash and match the transaction's OP_RETURN yourself, with no dependence on bsv.cx ever being online.

Verify it yourself: the manifest is the exact JSON whose SHA-256 is d34980d87ec904da43a08c1c9f0521e73331a73dbdc34121fe85ac4c4ec71baa; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / d34980d87ec904da43a08c1c9f0521e73331a73dbdc34121fe85ac4c4ec71baa, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (185)

← back to bsv.cx · JSON · saved HTML · ⚠ Report