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-10T12:20:05.075Z
manifest sha2567a05797d2f48081897a37157958912789789722414ee7f24f442b6b0329d386b
html sha256af566e402bee34d5252d2811cb3b5f4943580acf7e9bf6003ff34be0b695e13c
proof⛓ timestamped on-chain
txid62ba1e1220862623021cceed24d95d23596440e54899ff3eb7c16d5c0eda4614
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 966,133 · 8,636 confirmations
SPV proof & how to re-verify it yourself
block height966133
block merkle rootecc3b05c748cf6353ae92a63c98f59f8e9e53b8ad4d124263b903e85b97dd4f3
tx index1535
branch (12)8e62232421fdb28955068a7682da9339d2bbbf15902ea2ca99d0c0a03ee08cb3 987d521acd817dedb97b7c749d735d94a2c65e29b9d507ce32fbe7cabb5421d5 d7ecefc72f5997e17abd28ff58b137c72989b9cff2989e79c12d0770077366e5 eee20ffa35c28775dc12e6b27bcbce8faffefd0f1b157fa61e0943e3ca68d7d3 e7184990d4e60ba689240c1a37d54550fd7446ceaf92740ac131b6b797a3f4d4 a310db1cfd1396a6afa891332315806f64fe47ab8b43f0c82abf8df1a5277b01 e4396cfa1bf31edb012d2e5b18838920cc679611c695571ddddf4264e8c110f1 23795567183d8a9eabdb55eb756bd1450208789c229a27b86447d916b115ee60 d006e797073be3bcca117af31b51fafb7e76c4680fb08856e04c44ac8be5d085 d218a1f1e08d32f22e47eac57c7002e3460f7bf6036e649d3eb87268bfccdcb6 070653db6e262c62375dd796890d2ed1dbd98c8064d8dec0a82d1312bfb89f06 c0b2747be1e3b4c533c40ab45665b0d9cdd7234a1928c6c888a8d8da51468b69

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