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-10-16T16:20:05.067Z
manifest sha256e5d3558c1a4daf53a9876496ea1c8286484c53a04711e9a0ffb27802c565fff5
html sha25613d9def850eb47c6f76cca5463360034b12f89af450a00a4c7265e6ef89d89fe
proof⛓ timestamped on-chain
txid6f06b6b7b1d58218a8747c9aec9db6114388265d8fe8af7504b8a63d54e3da9d
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 971,336 · 3,433 confirmations
SPV proof & how to re-verify it yourself
block height971336
block merkle rootc766980e785400e83756c98e4014c47f04edebefa102a4e58e9be1746012998d
tx index535
branch (11)d8db506b43173498d75ed7073834cca0f804860ef9715d5268c347e285b33679 546067bab3ea92ba528eb8c5581ec760e41e299f52bf74e7e4a361672149caf2 97473776cc7dc88824d92931b38648a80cc823ac39cfa7e3caf16101a5d63850 431fd156cc43d84e0e16f22ce281c209776cf1e617f1e9fe679bbea8e2625273 2e33b0354b68b46d273eec64c67b7a3b131420cb539bec21ec0009dc0902b548 9b99dc9b1f9d3dd92465048a256f135ec494578debdbfa02de6a72a6d317217f b480861f4175ffa74c3026075cab87fa3fbde6d1f566d4c2868447891df99560 f95c392722a513edc856843cacf61288cf56bbf73e0edea8ff839a1a9f830ed4 54c7d7075771c8aea87ce8aad8f3d74924599a9a597608b7525e8ba096f607f8 c20616ceed41f6275815f320aac19c8bcd298f342a0cf6692b3514eaaf5a8d4a f477d8aaae1fc92f891dd4317bbc05261aa95ca98fe8d8cb45b56550a983093b

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