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-08T16:20:05.387Z
manifest sha256375c1e4e91cb1fb4ecd65d3eb119efb76282af836046f5a75cde5f9c5a998400
html sha256af566e402bee34d5252d2811cb3b5f4943580acf7e9bf6003ff34be0b695e13c
proof⛓ timestamped on-chain
txid918dbca31e2f925d1616bb345229d250074da5ceeb622ec06e7ddac31ead71a4
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 965,880 · 8,889 confirmations
SPV proof & how to re-verify it yourself
block height965880
block merkle root362375000e3f932015c2e0bc133aab1c1006e6185f8d94cd61fdec5d94961485
tx index299
branch (9)66967af378ab115e645f6263dc0d30af2ea77430899a4fe3a59b9567f1f19370 6ed3a0e85ac2f108f21bb2ea9d6a611dbb44ef1579ff0088ac9b063e7cc0e081 dc5fd346bc3bffa6a47e01c78809d60f9b0840fa8b3e8354f8af287a1fc204d5 8d0b28d0dbf6ee073e1f4fd7d3563f86fcec9e2913f39fae92d2600f481d0891 1346b3d5167cc40b622189045f394f5adba3aefc65a4fab8db9b66e550c9ba48 8ab68bea5115f6f158d60434fd0af7a26f361cd07422a761034d1847d29ee21b 3bdb43733a2b2df36a20c547b6174571b532ceb73a744abc1c481d93a3b564e6 67bdada673bacb8e4818bd3f0ac4c312f42dddec4cab70a96c5985365600d130 9d38f2a008e18d956a2e1a3ecb04ec6eaaa7659bd4081fb7d9dcda7103703146

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