Web-page notarized

A tamper-evident timestamp of a page's content. Pay-per-call — bsv.cx

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-21T04:20:13.007Z
manifest sha256f7774be2acdfb4eea757dc6395674e6d5c60539d8c046a492b977f1012f2b3f2
html sha256eae8586403773fdf9bc627b36642da1fb397500070adadcf40420e0f122f2bb5
proof⛓ timestamped on-chain
txid0aa948c899ca41213cb28c30889021a603cc4443feae255a49f5aecd7c66cf13
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 971,978 · 2,791 confirmations
SPV proof & how to re-verify it yourself
block height971978
block merkle root95397c09d9063ec62e8ff06d7ffb657756007eadbd92b2cb52f48290b7e22fef
tx index42
branch (10)7063e1d146794b5c5b7c4cc17c41e34dcfc4c89ae30dd9f0fd0d9019581ecf79 a4adc48c2f48d12a8ac69cd0c7b1709edf58b7db6d8bf71aae71e4331d4112a6 1e15d6c006799f4fcbc6ffa18d048568499375e563c67af3425619f7b40cce89 b904b439745e6cf520df35bef66c04b3ae8db3358a57f074d9e516db0f3bd17e 77aa6ac09249b1a74b0330b8cd9746473e0c57197a6749ae40a9b34137144840 301e840e04b8bc471ae1a39486772860886d0c9798d370b8b16ce1459080e5a5 fd575490b0c9e87cb7a36b32513fdf8d8f0d62cdef9823804ce4f5d8d125512c ace4a0f7ff9bf1f5baf61bc417fb8da1e257fe8a9b4ab331406598ea02efcdf4 9d94f93a668a3b45e7a82e24e7447cf8f4a14fef05181f95e0cc3545de432983 730803fb217e15f361a2567cd3c68dbb090a4f567f045083181225055e3d38e4

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

Other captures of this URL (600)

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