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-11-01T16:20:06.375Z
manifest sha256815f88c7691a8b931afa9652c92eb744a5e3b9656f78a97c409a80cddee6b0de
html sha2568f62dbad824f9157874005572058f82f268052b30ca6725f9e9762879948e1f3
proof⛓ timestamped on-chain
txidbd0f02fe87c9e423370eb7602be24416ed2f8df39a88923e86e051a438262422
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 973,632 · 1,137 confirmations
SPV proof & how to re-verify it yourself
block height973632
block merkle root08a67830c8d36f560f38ef39e18a3532f3f85f8b1ca1a14ef1a2a8a12f718463
tx index1223
branch (11)7499525ab355fd9d9074cfd1ced4cdd53de3a0150d1ff44a3fe09415303973d8 7c1524244b3951e9477579b1352150c826f18b204758bdaa77e317dd4579036f e83c972e598b4508dfaa4e9931661bc23fdc67dabe967424478b43a3c5ce8154 3c2df27daaa97669690ccab4900e3f8b5d87daf5f7b1e235a6e382f89e4502aa 6a9f053a515035437cc80d12baf157ada4ea6c9189280170484e361b1595dcfe ed9ee054f24aa93345712bc1f16363209297d61db97714e1da7c35493020ab48 48f2d7a0f8a3d81dd31969727fccf2d0d271eb52a5b09b5d01273c9d30c8829c a046cc8ac751894b116acbcb3f90286cf36eedb9533e340b95c3c89f95f6eb0f 7fb41b2e06a214d79af7a393a6d5d1d7d454fe0043843b286b0909e3ec619705 * 798d3241f65caa8128eef09372f7d93371b1d0a7580f508fa082c24ce2e4a7e0

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