Web-page notarized

A tamper-evident timestamp of a page's content. Gender equality pays off for business – so why are companies pulling back? | UN News

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-11-03T20:41:30.945Z
manifest sha256171a83fb5f704e35fae9b807bdd21568eca524a92ef4703e86c60628484bbf24
html sha25637d42a717e22d09be0e846d58740add27c4252cdecbe59f96b97d99a0ed29686
proof⛓ timestamped on-chain
txid05b13b68652aa4d0bf9eb72475c05128618c2a4008e5ee660e204eb63a24815a
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 973,954 · 815 confirmations
SPV proof & how to re-verify it yourself
block height973954
block merkle root645376b5e3ed828b906bc3dca95f76fd14378bf02e0dc47c8edac8cf4ce4605f
tx index485
branch (11)251a2f58472a5b51d6a8817e0158116bcc5e3d3259f83622f3474feef7d18353 1e1b6e2ec1615ae69213abb0e5ea5c870d05dd78174b4586dc3e0e2c4d582885 7ede45b81ae1bddce4d4d0e2790756e1411175a270d6846c3f5fdabe2971cfc5 6f33e36db6e353669c710ca16b704fbb6f33d0a8470c477fecc3706f0224ba07 0f616be396f677f082b3b76b0966d7649db063dced3aa6a9a3ebbe210fd341d3 8d807cba2b54a8f0ba56fd57df9901805d9f624789fd5254bb2e8da71ace4ce9 86bb08b130787ce2f1a4720d75f4c701c51307d26cc1faf9ae43b96c2a2f5d3c 9978265b9e061db30080025435014da041d954cc587176201b2cffca700e290c 0f38c3673bf47fbf18fe3d4e08668c4b410be9838bd47faff8365d58a207d53f 4805ddd0ac7d379e0cc137caa72c87cc98b503c954ba81736942b9e72a0e9e1c dfe5bf14d5406d658b181d3d69b257793ea4a3f77b26056e71ae968a267c882f

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 973954 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 171a83fb5f704e35fae9b807bdd21568eca524a92ef4703e86c60628484bbf24; it binds the URL, capture time, and the HTML hash. The linked transaction's OP_RETURN carries bsv.cx / web1 / 171a83fb5f704e35fae9b807bdd21568eca524a92ef4703e86c60628484bbf24, and the block's timestamp proves the page looked this way at or before that time.

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