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-19T16:20:07.335Z
manifest sha256c4fba3692168b97c7d029cf04589cf47c4746cd55fb8152feb3e12171af07d4f
screenshot sha2562127c77b74c39e78e07ad14f2c4e9e8cf8771d13a37c216693e76c4d72a2264d
html sha256eb81f4a853f44042c661e01024febc475c0114cbba3994784f5599e164d28ef3
proof⛓ timestamped on-chain
txidf3ba21bf11a7e3195cd1b21840dbae4c62327b89642113a68098a0254fcfd461
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,015 · 11,754 confirmations
SPV proof & how to re-verify it yourself
block height963015
block merkle root2c32e0a8eabe6bd55ad1e2f047ed69a42d543e7e7491bfe8403d576c3a8482eb
tx index179
branch (8)3e65b1c2686605ec739b83b8fea33dbe0c321d0fa9983ec390c1966dbad2dd01 5300c04c0713685e391293f6658e6425892931bba919cdb98caeaf74e4362af3 a4cc94c13c3309bc1174ad2bebf5a70189cd1fc9b7ed4eb0e79ffa2878d6d55f 6d94cdc80efc9338470789d712eb08cdbb4cff41c7a8a81c57350df345d037d2 25ca335ced1544acc414126e8e5a97859afe2671874c4c400a50e042bd83a61a 5fc1595f96d1808e51023d1c7e837427792196b23e3593bc1566b20b4026308d 22488b7ca1dbb337abe6788728c3c8b777c4830e4335c5ace5fa2698848e34a2 91ec6d71bf2d87997fd06b201b1e4633365d952838ad37436dbcb6468cc14d61

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 963015 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 c4fba3692168b97c7d029cf04589cf47c4746cd55fb8152feb3e12171af07d4f; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / c4fba3692168b97c7d029cf04589cf47c4746cd55fb8152feb3e12171af07d4f, 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