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-07T00:20:05.103Z
manifest sha256eeda0b45a0fe5783026ed00f09234aeca2f1f259c6d569a4c1fb6349212fd36c
html sha256e80cd75230ba7d9ba7ffa8fc8937317fdd5bf455f2515b9eb458b549cc4db772
proof⛓ timestamped on-chain
txid6db3fba2abce1a02230c3da37472e580082d1da5caa08f5eb9bdf458e5dd65e0
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,641 · 9,128 confirmations
SPV proof & how to re-verify it yourself
block height965641
block merkle rootb0ae4819e65cdc2bebf8ccdb1557eee133d9e633a8a5791fe7c25548b665b838
tx index249
branch (9)f897012532272c530f27a29cd8e9ce84dde7450cf5efae9e3339c97e0d0e13ad 50ac8baf6c713eec99c0fbaff67768ae72a7b200a0dddb7ae068dfb10a4c17cf be2c61b3088e7b70d2b191504e1e2dd4ef604f0dbd481cfe23a7530663b87028 2b5031f9efaa526d12bbbb3562968c50cae9c4d88b39e2f95107b2344b11abbf d1ba7eee4c4f11390e9964b045270dd99deb316a734ebed59ee716418bf23621 9bdea34d488fcaec3bc920c6db06fd884a464358a8ee3f35a36d731eb60fcaca cc4cae7819e2a01e6e8d76eed5c6e69230524a4ee69fa0c4ab08b799f8010163 c3f66bc542e7721f89ef10770457002418a7d9ec103808ce717822c3d1af61fd 355a2f30b64ba0f6664abe35973131b3522f61abad1e4c55a955683c04c98dc2

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