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-09-09T04:20:05.388Z
manifest sha256f8a1150c0efb204042edcc7f365ddcd22cb690710a9c5692b4c4fb887c3ef108
html sha256af566e402bee34d5252d2811cb3b5f4943580acf7e9bf6003ff34be0b695e13c
proof⛓ timestamped on-chain
txid3240401c889ca09b1b9aa6febd69e0c0817dee031614c4aa1597e6cbf81b47a9
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,944 · 8,825 confirmations
SPV proof & how to re-verify it yourself
block height965944
block merkle root948d2b77611bead59426619ec5150a40d99f966b713b0b50c39fec4098f90756
tx index263
branch (9)19db3a0c056db29de0c78a400f54253daf7652692d35c5df04bfc3aa23ebe1b6 42a595aff3b51a3efce54788ded5ccc1d2a1a601d1f4f3f600607fcb6817d23f fdeec3825f64a14b66613eaab8f50781df8bfd20f800f845eaff364fe01a19e9 82eb52b9cb7d6219d5c16cd6c389ca4eafb7b67df52cfdadf03459f98104a231 73ca439130b3f29708f89cee023ec59df7def1cab489bb59252ba06a19e113ba c98b2b5878cbf8f0448dd00951fbd245c44a0d50e2aeeb01706e00a95c2340c2 aff50d33a7fd91da0fd2ce8c5361b759ecc39b7fafbe7c4c4408f1072a2fa919 7428076199f2d4c9550d5e623a7587e59b7023c3780f7803abf0cd3792030d88 3ef1552ad0998620da5671de1f6a222c6da88f3141606f6259634dc0c8231ff5

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 965944 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 f8a1150c0efb204042edcc7f365ddcd22cb690710a9c5692b4c4fb887c3ef108; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / f8a1150c0efb204042edcc7f365ddcd22cb690710a9c5692b4c4fb887c3ef108, 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