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-05T12:20:05.648Z
manifest sha256a09b205486ad5414bd8f70df6303a42b4713af1204ba500810033757e1ce0361
html sha256e80cd75230ba7d9ba7ffa8fc8937317fdd5bf455f2515b9eb458b549cc4db772
proof⛓ timestamped on-chain
txid714aeae09e61c149aa3c09c330df7f15c2ec69a4b63b4a34b2198a8322afac75
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,421 · 9,348 confirmations
SPV proof & how to re-verify it yourself
block height965421
block merkle root88c26153c3d909a3abd478b8c2e99da46e0d4b71cde73cbc615dd3a1e34d0a45
tx index28
branch (11)f360bea523878cd4f823a4a5fe1209da2f1b2854e3efef337e53eb950484c435 1acd08df005ee16898dca36e3823e75a76002ee75a6e23fe03d2719e5f51fdec f8146d4afde2b03e87debee636f6dc683aa50d69c1f2845eca3f821d5c2e8bd6 18b5435e06cf03e19af6ff4188d1022d8c28a8cb432e51a622c6299a80f7d0f4 979f8bf717d92221c80db0a8ecb2a2360076a5c5bfc9b08610a797d57e25b330 3b2f27d702a847376bdc808b97d3872e16f62dfa8a6e61755951d25e3891b9e8 be71340e5f379603b6a2a240a49e94439fdf2cd3b75e97049c21694ac9d5475a 3df83a5524bfad33532ba78fa493eb7099264da179740dbf611c73b9af90f70c 654a66cbd7c81c294f5e2fc58f518e702f7fe77ebb65dc2dbbe674c1909af2bb 7b541023112696817ec46649d5e9aa5b3ca26e04aadd312793ae3f47f229195e 85fb1acf66bd186d3239ac2c1d83f71ee51d4f50121aa8ef71d5a11677680f26

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