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-06T20:20:04.618Z
manifest sha256b94a1a832ee76ae18ec401c558ac7de774533897aef25f93db203f268df73836
html sha256e80cd75230ba7d9ba7ffa8fc8937317fdd5bf455f2515b9eb458b549cc4db772
proof⛓ timestamped on-chain
txid72a49df9d4666aa3949e053495f88f0f8ac66a0f1eed2ff9ad12b7cdc33eeb9a
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,621 · 9,148 confirmations
SPV proof & how to re-verify it yourself
block height965621
block merkle rootda00151407880247ac7aa4672741732cfc31ad04555a3fe6a963d1e6ff204c73
tx index60
branch (11)e0e86333442af33d481dcaa1b46b79672d3377bd8aaaa332d1cfbc5895f5bc67 3d2c42475e7f8b54cb88b9beec1a5be0530e8cc1a89d18a9a72ba22eeef72772 866aef5835f41b12f1a3c531095260d6ab0a5651efcec07bd854277e1d1f274f 415d841f51a43e6770b210d49391d3a60b0daf06b5acca27c1f68e29c2fd5933 3aed1a978d0f82f9b3f7afe13698fc8253130d857cdf5a7bb515a8cd5d7c2839 7d8187152ac195003b74dc5e3411adeeaff9c20dcf6dbbb62b66b9a445982f2c ad0f776ee0e5a551a8291b2aa378e982980c06e80396cb217da786c91c3d4323 fa35d491d3a3e9161540ca3e192e10082b71159c7e7e7574b23a05d5be87784c 48d6973d9ac4bac9fc172825ae1bcde9dbbe81050f2919dd1094ef86fdfb3650 95b96b14d259be2d4283ff00b37e4219eec9a14b4427aa94a098fb5dc1bc3004 48dd32eb9b69260e63aed01b4f56321d19df9595c1710210f17f264a14af4e2a

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