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-18T08:20:05.463Z
manifest sha2566ef3fc9b6878f5864f2a323492119f69f91d18c47fe1b895961e738103f48a1c
screenshot sha2562127c77b74c39e78e07ad14f2c4e9e8cf8771d13a37c216693e76c4d72a2264d
html sha25660b93a46ff591f6966a1e326d68a9f962af61beb2e7775674458339d5492034a
proof⛓ timestamped on-chain
txid8e104290c4667d1d4b1b6d54685461d69cebe6556627456f7dc21360953e628d
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,830 · 11,939 confirmations
SPV proof & how to re-verify it yourself
block height962830
block merkle rootfc644c8bbed699d39921e3327136a4646d5a097e57bb189accff3c86bbf24aa5
tx index259
branch (10)a69b32c1fd2c600f7dcbb9c34446694d16c0007d818f4165adb3d80e3578551c 16b7ac0d95a26ad05fe700dc60a9c460d5cfb5d9af5fb86517cb40da48209513 e8b1f737b2e595109ab6afa90eeaebe94be177d32f5ff7c47e23530d042ce0c9 48f2c79e82dd39ff81442a4707cc2a400cce8cf105551ce50ab87becbe71ddad db28f593d2c2d574aea691d10de4b35e0a6fb6bba1822aa1e569230c1b236961 f2bb46a5b2f50737c6023fd515d782c6db70be9b28fc3ad8f94296fe83330e49 80b40ad00a75a6c4126348fcc34718ad347a41c9316abfd8732eec3aac4449e3 8211837a4d41edf6b9206988d7e1b310a91cf4dcef98ef8099546070a5a06316 7b71dcee4672a23fe5b64c2d4e4fd85c7f10105d0dc39c75e066413f60fdce0b 0eb0c239dbae161d7aac577f37863f988820e1a9222f08bce6de1db35284774a

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