Web-page notarized

A tamper-evident timestamp of a page's content. Verify any proof — bsv.cx

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:08.929Z
manifest sha25668b4c7a40360ffd3c4fb048ee2bcd2739f6ee1688c1f522415e7208202f9d4ea
html sha256c4578212f432b9c4eb9c8a987986027e141677993071211e0f9a874240ac5118
proof⛓ timestamped on-chain
txidae7f88bedae63499995d3b213d385843b97fbcd00dfaa6613794a5cac47a40fc
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 index1537
branch (12)f6894f004211371d22b967e8d0a691f390ed894306d8834148da4b94e22230ae 72dd8dde5cdd9a3b085eb7cacf78bfe77a64caf800dcd611de4c897a7cfefce5 12c74e6b3f6e77c5e76fb0a79937d0da419c19cc83c586bc4db222bef4732f09 b8c2df17ac3988d6aceed2f0c756110f9f4d52d1ac7a4904c373e3840164f84c 60816d56a719017d4096bc327beccc415605ef05c299f9420ba2634764968a8c bc7b7e51c077a102f088e17fe7204fd19ee3601e3a0536bf72f3dd251acfbe03 c30c222791668adbd9a03dd4dd16f4bf3d765fc17b0c9514a24ba9e9e2905476 db383fa74c4d1f6dc9fcdda99238fa2b2bceca2602832e6b5fc199a4aa527618 a599e9995477a1837016236c00211341bb9c8b5a5e1b9240e4acc0e55617b41b 3bbee21aa267f3f1ef0505b5eb1072ec2039c31cc59bd65f40d44a17654b5a89 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 68b4c7a40360ffd3c4fb048ee2bcd2739f6ee1688c1f522415e7208202f9d4ea; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / 68b4c7a40360ffd3c4fb048ee2bcd2739f6ee1688c1f522415e7208202f9d4ea, and the block's timestamp proves the page looked this way at or before that time.

Other captures of this URL (179)

← back to bsv.cx · JSON · saved HTML · ⚠ Report