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-13T00:20:05.134Z
manifest sha2560e559ca3237d42c10841841691274a8ce39361fd9d6a4dd96ec07a07a0531e7b
html sha25659ecad0adb0b827eac64a9bbebde2bfe9181ea0d07e291296b236449b56e6f5b
proof⛓ timestamped on-chain
txidc15772996882855bbc3ffb0c45d51d9138d0383df1c556ac4c70c14f58fce944
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 966,507 · 8,262 confirmations
SPV proof & how to re-verify it yourself
block height966507
block merkle root6e53ec1726e291c762827815cb63dc84f28d07fc0f23d3f18b188691ef23bf41
tx index357
branch (9)7fd4245f2bbf85b9091b2ce70428766aa22b5499f7aaf36495e3180fbc7caec8 44335ac90aeb97bb7d6d990c2f0c45ba0cc711968e680064576034f76c370a68 a730a7c22b4341bd0556fd5781e2af30d6ad0c5dd17a05e150438ea778f7b0a3 7d28aa2f1beea127cff4f8bccc0aa6ee8b827d99e8509e3ccc8d000603710dfa 94b6fa78468d1c11324e9136d8b40f37903e40507e5675749b24d03cc797e023 1ee9c6417a8ff8248244179160294ece72b18c74944f4e94a7aac6d3e8ba3d16 8aae3c220fff6c79bf6d6eb561c8602c0dddef76daf77c6bf7f3ec6a5a93b66c e2442a7803e94972c5af84a23a69788e772a83fe833578381b4e526ae1dca86b daebd2861b3886686b4bc02259f091282dc1418b2fb14e9017e1d1b2c552ffa6

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