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-06T16:20:04.761Z
manifest sha256c294aa67554605e903ddaed85713a16b946f03831bd324b1e96e8d51986e57c7
html sha256e80cd75230ba7d9ba7ffa8fc8937317fdd5bf455f2515b9eb458b549cc4db772
proof⛓ timestamped on-chain
txid30f7ddb338dcd41d6322bced288f7cd7b90cab65f42f5b3d60cbb4bf3a584dc4
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,596 · 9,173 confirmations
SPV proof & how to re-verify it yourself
block height965596
block merkle rootb72b6eeab5f54d216ad3484214520550e998e638a28c3e6b05690879d00a9baa
tx index755
branch (10)36d9575e68c4f08484b93bd45b06c09a1c32d9a3e5b30c7c8a82cd92cdc853ab ecbdc57d27a26b04998dbf47d74db3ae1aad8b3af9023a4ba55375cf427c6b5f f8f8a9977137c04ae3acf35e3e51e865518513ceb3790949db7ae0f88717277a 65d873904efef71e064eaa6b97d5c1185d3497b3f39444ca10189298d279b1f6 8500302b775395787f71912f6154ee3003a48edc1d88232d1ac06134dadbb668 0190412e17cb10e3aaabe8f9c1fcfc9e3236cede07057d2678011ae9a6aea663 6cad454b2dc8368f22afd977d833f2f2f433025f497943ca44e1ddb712052c68 9e581de638a7c1b8a2a9631bb9b836e9b8b49bc5dabb4db0ace9d09a7b209b1a 3c4290b556d60fb0678e6456cd55f1bda2aadfc1d08525619af6a9a8ed22f170 a03a5883f6dc885caa64f6a0bed2ac1c2f9063f66c1ba546b315bbced88152f8

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