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-15T04:20:05.013Z
manifest sha256f782cce9953aae321de2b707a164182232e3566dabe8809f17e89114e0188157
screenshot sha2562127c77b74c39e78e07ad14f2c4e9e8cf8771d13a37c216693e76c4d72a2264d
html sha25660b93a46ff591f6966a1e326d68a9f962af61beb2e7775674458339d5492034a
proof⛓ timestamped on-chain
txida448f5ef177e4687e1be1650fbe73ff5f8c55ca4e0e91e45051dd3574b17e3ae
WhatsOnChain · Banana Blocks
✓ Independently verified against bsv.cx's own block headers — block 962,383 · 12,386 confirmations
SPV proof & how to re-verify it yourself
block height962383
block merkle rootc66567399d16b979b9ce1d73e9a0f51f21e2265621f8fa0826ebe9ca81376e0d
tx index279
branch (9)057ff0e9d9d4aafefeb3da69ba5c1b9b37ee95780aa50975e9cd8a767aa15209 068affb98cc5f55bae2a4f0c5801ac76168347f5b256b292f0cbbd0883a88a97 5462ea747e8c4cb335047d997b8d470dd6585497358c03be4542e6f3e8d491fd 6d47fdd19a22ae37a7382fef544f8564c7b5a0fa28d0629878ce5bf27fec0b52 40d629e48c4624777988561e9eb11299b2cde88922c0ec22dcd541296c6944c4 a8586e09a1d3855036c6ec6b948e4c3a5e8e669ba8edd764e44557f93575f5fd 3592dbb376ee6c3fa35ae0c88a32c8b5e7f4fc58187bd3c4a69cff72094bebfe f2ce37f2a07f818f0f282008f90631b0ab2b6b8611f2f55a96f61b9a1ef390c4 39500c49ab21677ad04209b69ab4ca3eb2d88241cd30cfce52a42c27b2ce3a1e

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