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
WhatsOnChain · Banana Blocks
SPV proof & how to re-verify it yourself
6de518ba80b4557b5549205aaa9ad303c7eb486a8b1f10fda4bd17eb722d1240
4fc64cc3581eeea386330b09423772498fb5c4ff3b6a90d57ea6d7c5116d4235
00cead17100aa7060716f784333009d1b27016af8b54266e0686ac7702be3e41
6eba75d7517274b20e368b02e6e6e83644e095e64d04a5cd57b630fdaa833f67
1d3422899dfeab731f0fa5c0b609a94be26477ce73e566e34203bee923426e54
ef71cc3df3e152eefe032734dd90e4837427e20c93595a8258bd2b693dd8d20a
24396977dd884097ad62e951f1b40a1c905bb0c6fed42226995b6927919703ae
f69150231ba35e6d28ad398b8958973a20cf135fa4159d5df73c0e35a63359e1
4a8f587acdb7fc0a8416aa1d046de2ea82bb1d73043bedf589f7a3da51af9e3b
be8e8e295e3a28f4ce748b766c8b6b7ddeb5491dae518955c0389635fd6860b4Trust 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 962800 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).
⬇ 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 df3c0f46b6acea5e115a9e05c49d1addb09c0958b98a0b510500c23b8a98c75f; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / df3c0f46b6acea5e115a9e05c49d1addb09c0958b98a0b510500c23b8a98c75f, and the block's
timestamp proves the page looked this way at or before that time.