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-09-05T16:20:05.532Z
manifest sha2562dff69c8941beae437d9b1efbace0cb4e294f71e24e52e5a5c6901f587e47a1a
html sha256e80cd75230ba7d9ba7ffa8fc8937317fdd5bf455f2515b9eb458b549cc4db772
proof⛓ timestamped on-chain
txid801f0cda5e7077521e6c951d4beaed536c6d51b00e074d0279cfb29ab94ba338
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,451 · 9,318 confirmations
SPV proof & how to re-verify it yourself
block height965451
block merkle rootfcfee6da1a55d0d4fdd7f1ed52baff1cf69b85596cad996e6223ff4465d036c3
tx index2271
branch (12)8457351d1be13d865b68416f690b3ed9420ea960580e2a85005281d09915c67b d48befdc96d00d0480afe85f2054cee3e7fb5a935ef1987092cb8aaed7482c49 e7bbdf72ca78740b16b6de9b5044fdf233e1acc79e8410991badd32ce64949e3 058bc96f37c976f816a2a909a903c7da9288142af3f381cf67bc0f5242f3808a e8f34b3b74fbdbb02e160eb025cd528fa35c48295561217957aae6f0899f30d2 6c07fb0881a46522609f5fd1005a8a650964c63b5995bc1c441a837d7dfc9515 434f1e00ab5b3e795941a7ba8fc862268fd83647f591e7cdee55182eb4af3a19 939c87cd941c6fb208e6c7c857665f605d8cb0b8bc6a59c251057e518522b164 1b9520b6ff5b31169b200cbf067edf402c8f4b782fbd38bc16f026e0cf58c8e1 4a061f55cbe41cb80b27e41afa7729b93089653c75f6975d097c1255e0fff09b 1767ec421e4b6596380b27b6f279032802bc1b7aceaa2577174fc7f0d2d45cd7 5822fd44abdf0ba9c033398f039c9a849c42b80f65461d807bae1025ccecbf6e

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