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-04T16:20:04.817Z
manifest sha256fd0653f111dd457202a0ca72126e18e1215027972a0d337be57fdc20895f797e
html sha256e80cd75230ba7d9ba7ffa8fc8937317fdd5bf455f2515b9eb458b549cc4db772
proof⛓ timestamped on-chain
txidfdce9a5ac285a7754c65aaef9b6724898102e0dc1c65fc18a9545df452c10f77
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,306 · 9,463 confirmations
SPV proof & how to re-verify it yourself
block height965306
block merkle root9c4ca42cdda13d526f8f5725ebf97076fcdd0429c0be03710d2d18fef716b44c
tx index1235
branch (11)6e770a799fd055ce4c9ee9ed8f297948b1534b4c42bb40711359362c3b0fd3c0 177e01f3c3feed5cf6f97674318e1e6b31b6d33aa59769242c351bc25c033271 7e06e3aaa134ec1b2b87ca82d7cdfa2a3a4398add04f08bf8d6ac40639e6776a 809b2d5374d307c526b54758578a28ea442bbcbe5f27f8d347973618103a4c3c 4c2463f66c4fab0ceebdc74578faf8c7ff055c9eece6eee2ead2d5b8d72112ff b313c85dd93bbafed93d4e9eac7c2c621226145c72ab87a49766d05a11c33dcf 6ccf9447267bf1f45edc7386c7bcd63b5b120d04926f7536a855507b3296886b 54dcfcb1f6521902279f7360fc2236cc92e81f58d854918b0dec3fe0c68c0528 9fefb4073e9786443003c53a3073fb1fd0c9ce758bbb4eb964ff28a6170981bd fa790ec0abcaf4e8be8514f1544af58a4369e634b692aafdd3d4f11c2107759f 0272c9c97196a9436171ece3e601ecd021282e1262b94423daae6ac9deb311c8

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