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
42a36929a0eed80416915e11012d7e392ec2433e417cdf98165b1b67ccbdd5e6
0df3c06be78eee9b658dae53dbf1d2eb145f00230fa3a8d46ceff425bd8e869f
41b5e2603fadd9f559006b8b8b35b97f008ef7e8b24e6c0d3c92042b9dd34de7
b226b08c98acd1abcd2350175290e1b06ea534cd076bcb6d4b481ce1530ca7a4
66d561127ef46f3b7462933202d86cb05b35f32602e154f8b53d13337825ba85
12fb9f2bd5d8d56b9aefac2f35ce24fea1de2aee7a551638af8185b5edc6b10a
418654a3f61f23cab18f061454f056810154898aa6026791260870760529e6af
90ba7b8ce0f43c68cbd610b555a2cb9ae332c181a8b1bd776f8f00c9253ce4e0Trust 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 964021 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 a95f2c9a46c7d8479b3e319a026617341e4b599c2ba7abca5c276242f2110f34; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a95f2c9a46c7d8479b3e319a026617341e4b599c2ba7abca5c276242f2110f34, and the block's
timestamp proves the page looked this way at or before that time.