Web-page notarized

A tamper-evident timestamp of a page's content. UK, France tighten digital asset rules; BoE studies tokenization

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-11-04T16:20:26.821Z
manifest sha2566a83750fe47477651f6a3884ea57ecb8de71c9c84299ba2ec421b554dfef188b
html sha256748dd8f87cf7c9f5496ac24eff2253dfc54d3021940d2bab128b7d1c74595251
proof⛓ timestamped on-chain
txid2acce1afede27353922211b02aec2cbedd30195e96f8754d17d8c82dc23e0418
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 974,061 · 708 confirmations
SPV proof & how to re-verify it yourself
block height974061
block merkle rootdf1cfefb38f60ab659f911c1b7cd75c98e55ad886d8b69482148e174708e9987
tx index569
branch (10)80fbeb8dbf1a517f7325a21cfa71bf373aa16ef2354e3c44c1cba8cf25de4dd3 b339b44c72b8c7acc3d02459c6caaf1dcc1c8ecab210ad502899fd975b39b3a9 c51e15b67d26f0c5f16d99e262eacadecefd786fee9300134ed1af706faa5fdd 61a798bed0abff8a7fbe0517946440646e617243aada8f3d224c36563cf196d2 a53ab3f44b21d1d232241716071b95edaa0799a454b400f052b02e38af7745a0 96c9196053782e0c4af151f3a6ddb2de2a55bd7d232bf71298173788ff6ddc82 51320f9286ac40b19bb509cf35b0ca3a0c10d51545ebd00ace820b7493a4a24c bca6f04b43c3f58f4fa943b3e3701cf066a6ec51d01c7ca81572eb673b79507d a050886bc12a16fc8b3614729fde4d043bc50c9175ee6424d25d6dabeeb3207a 37f78598cde851667021b1de44d0a527fe5a72fd9e557c2fe5098401e3282775

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 974061 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 6a83750fe47477651f6a3884ea57ecb8de71c9c84299ba2ec421b554dfef188b; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / 6a83750fe47477651f6a3884ea57ecb8de71c9c84299ba2ec421b554dfef188b, and the block's timestamp proves the page looked this way at or before that time.

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