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-29T08:20:04.975Z
manifest sha256598c77b0f8e9d3ef661c190c0bfb124638f6d4af6b83eaa137cac02de7ce2470
html sha256ff820ec7b20e1f890b9d48d7ba5c46bcf16fe54770eba08f37b5cbe69ef931d5
proof⛓ timestamped on-chain
txid3ca9d6b002c59fa21492b76f8b2637f35a6b756b692b01c28ae24a8572cc69e6
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 964,393 · 10,376 confirmations
SPV proof & how to re-verify it yourself
block height964393
block merkle root423fa4afc96555140fbd3d46ae8b3ee87824ff5de95e609918bb6728008e2bbb
tx index92
branch (9)e60c05778d596667b1767cce32a50f5c7fb5d51431b03cb2f13b2457c233e4b1 23dae3d7c38dfbf7ee1fab7d8d159be62c6a02ddff904250b8df6b210109d6d6 b2fe80686a7092c987c7a89e7edc1f48c061d56ea5067251239b08db525c236d f5b127a1771a74c50affbd559fb0ef1d2ed250660df6af8847c0766710dec6a8 46be5a650f4705f6f6b4845980980893764fd9d4d0162b42b32359692a607e51 86e905eccbfc4c915f74fe574125219d7886068ce11ac89676473d0a373a79a6 8e9700114e21377cf4eef725353e0217efadba4ff66e05011537593e8caf1a4c a252fbdc0940393648af5e65c6cf7f40fdeb7d25617c048d96e03f97729ba1cc 487077dd080e852228a7ce19955d3075a01440ebc9f331be631f1a2322918331

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