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

page snapshot

captured2026-08-22T16:20:05.380Z
manifest sha2568b7bda26279bc6e8bc5a7eefac79cb937b272285ef2b339105cbaa00e474e76d
screenshot sha2567690736f43eed0a92070907fdee2935e239d53f88c9bc371df15ab38672c517d
html sha256b0ff0476379251b5679c888e42cbee84e22b433611fc81ddfef98a8a736716ce
proof⛓ timestamped on-chain
txid3be50cdbdfae96e3556911d28a2537fe31c7ac1a5003e5f7413e71eaede9f7f3
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,432 · 11,337 confirmations
SPV proof & how to re-verify it yourself
block height963432
block merkle root20040ad3c44f02b86432e4644dd031200ddd9c38eb24a2d239b34ed921808c4e
tx index605
branch (11)069dc968b7dd87905590ad8b83091862104c5a611723e300baa113e50e1fa9f9 54eab07597358ad22329fc1744fd96cebd985b282e4c34bcb3fd76abafeb9c67 9f79e5a0263a4c02350894fbd967918f4606840045362b0811a7e443b8170561 3a526adb74a467ecfab0630e9055017852508a5e6d6a162eff9a0b13153dd015 7f404e51a87899badf17f5b010796d1fecb4d78d452c6dab8daada760da5d704 fde6886f5772328a765340f6a9c37ef341910900a7f34df2db8be85b90eae720 7f97436b034c8c06de19e70ddf86b96ae1c227946c477142874ab832ce737780 533f371ba03707010915a72ca3fdd89a9e572bf303679db42d37abd3fa10882f 1e96319bd47df0565df1e733b1f0314837928d939e7a86df5d2fb2b0519d41f4 4fce6117afe3d1aeee4d36aa2b940c7ebf2f8ce79b0c034f982f0ceba5080de5 9be09de385bf53176ab3689b53ad58d6c71e0a6f949f16a840322e7ef689af12

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 963432 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.

⬇ screenshot (PNG) · page HTML · manifest JSON

Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 8b7bda26279bc6e8bc5a7eefac79cb937b272285ef2b339105cbaa00e474e76d; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / 8b7bda26279bc6e8bc5a7eefac79cb937b272285ef2b339105cbaa00e474e76d, 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