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-06T00:20:05.104Z
manifest sha256c5536e909178a5534d185d81c3c6b7fdcf51ee4e9dbba3d8335c62d077ca5ce4
html sha256e80cd75230ba7d9ba7ffa8fc8937317fdd5bf455f2515b9eb458b549cc4db772
proof⛓ timestamped on-chain
txide01502f11954a1f9c5a372b9e00fd878793d73afb106bff66e4dcff4aa7fb9e1
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,503 · 9,266 confirmations
SPV proof & how to re-verify it yourself
block height965503
block merkle rootb985a4b80431b0193b6137169985dcf74b88bba8d6cee5fb502cad50e34b32a1
tx index730
branch (11)c6b289eb3243de7becfd68122850c4a2ecd552beddbcbdecf7b7d9593b959a59 1075eefda8cc7b52b393abd7c0ecfe95ce7313d5753805b8c490ee6fcc892eba cd4eea58866542217b1fad47120fd896988d575def283d2276da9c1e9e33dabd 1b22c1b772e2e62f621c492faf9c0e3bbf9250322010c97855ca7e091af26274 99f425c2e5a3cb8da1d8cbaa6987b03d5adf7aceb6d84995c7bfbd112d570fbc 5dafc811fee5654b671b0392d7e9b8deba003087bac371db7761ede9f7cfca7e d1e64bad5bb3d4930130348afa41ff315c8e917f6026c17c525e505db514220e f5344038e70d999b897c3831ff7054303f0e42383b7d86bd75449070803df3d7 7f8ba7b85ee48038ea0d5680e57ce24de01720186144c1a2bc193074939ab522 754a68b785dc92ee11cb9b27192192e66580ab80bda38fe47e0258f803f51977 0a8cff1a3d50979fe2711e220ddff3bef367813d78603af6fd31f0adcb0924f2

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