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-14T12:20:04.723Z
manifest sha2560fa1ad749d7adf3563a66bef4543262af3d0b28ee32676b40d6eab85d240b75d
screenshot sha2562127c77b74c39e78e07ad14f2c4e9e8cf8771d13a37c216693e76c4d72a2264d
html sha25660b93a46ff591f6966a1e326d68a9f962af61beb2e7775674458339d5492034a
proof⛓ timestamped on-chain
txidaee618e7a041a58b1a6589f3e4d2a5bcf91ca4bbef5cb09656481a4866a04f3e
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,278 · 12,491 confirmations
SPV proof & how to re-verify it yourself
block height962278
block merkle root2ce7c36d807d629a456569ad6b4d2e9ca411fbe300b00e31ac451d86d2bddbbc
tx index245
branch (9)76ee10d53651d7836de727cd8a4c70229798ba81dbc06d83907a6ade464051ad e35ddc61ba6e4c71fd0cf8d76776af59777a93e0a94c8eef2cea5821208a8460 3a88a1b9dbfc05835f879699078f6323d896a45dbe5f0b27fc1641ce5726458f 9391acf3182c5047b24e95ddec7d058c921c12b503149e5fe449afbbae32a557 5eb25a9f878bfd8c76ac191d54369104c725b0ea3d55c8f2c0a21eaedd0c34e6 992e01476457a1895d8db1146431eb3f9709708a670f006e23ae0a301bef186e d41c20b1825d6957f606ae6fbe92267886aff23b8289adce1490f71049014761 845c3ca17decd44a5dbdfb57867b86f8ae69b04ab444deec2d584018a9660f3e 42e135962772a3232974cb2684234d2b33607ebf8cf51c05330b7b4addfac0db

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 962278 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 0fa1ad749d7adf3563a66bef4543262af3d0b28ee32676b40d6eab85d240b75d; it binds the URL, capture time, and the screenshot + HTML hashes. The linked transaction's OP_RETURN carries bsv.cx / web1 / 0fa1ad749d7adf3563a66bef4543262af3d0b28ee32676b40d6eab85d240b75d, 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