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

page snapshot

captured2026-08-19T20:20:05.819Z
manifest sha25605cdb6f66a68db7a3ed990ed62bda7ad6a7ebd713a6e08be1ea48aca3cf7f595
screenshot sha2562127c77b74c39e78e07ad14f2c4e9e8cf8771d13a37c216693e76c4d72a2264d
html sha256eb81f4a853f44042c661e01024febc475c0114cbba3994784f5599e164d28ef3
proof⛓ timestamped on-chain
txidbfd0d1885c9b2d279ba5c4e15309792cf635932db0ba6aa4a25ca50efb4fe3f7
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 963,035 · 11,734 confirmations
SPV proof & how to re-verify it yourself
block height963035
block merkle root66262b8df553387e5c18882b5667450c5a8d94e6106a145d226548c7300570a0
tx index420
branch (9)3e86873579df26f724e20b1268b9bdad5cfa919bcd06af50c9a820380b071dce 827d868603672bd6634062c31da7048303e61ae77b878af6a3614f5c0c332f44 11850812bfcbf4fe526c91fcdf4ae78b410efd9335a0274d6f061b433d1ef666 865a338d6f379645de6bdfba668c6c0823f9f68721528b4e74383b3b05e32bc8 a85bed662afc528414593e5f11c0c2851049698bb3f87e6e8f47102f224834bb 884e9c97836079fcc2baeb186a7e22e2ac8f5cc6ec74041769da8270dc359742 d3e6d79631002ff11b582128a80913421739fcb0ab2622879909febbe6784253 093d89e1feaa3715e117bd2a04fb6909ecbcd3cea82df188ace5c07ecf611867 b6c70efc7d0c110719920dd50d5b3ab65667c9e162d84ed3a04695b6a93535f5

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 963035 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.

⬇ screenshot (PNG) · page HTML · manifest JSON

Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 05cdb6f66a68db7a3ed990ed62bda7ad6a7ebd713a6e08be1ea48aca3cf7f595; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / 05cdb6f66a68db7a3ed990ed62bda7ad6a7ebd713a6e08be1ea48aca3cf7f595, 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