Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — bsv.cx
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
fdd0b9069bb51ab41b65be52fc20a06ace346198e9c83526160d073a88c0f113
f2eaabab40876ecfeef104d77793ef1d55ac83efe8328cfca785a94d6877bd2e
57bd3cf98b6528e7cc9d8b493dd874672b091c6b34719122bdbd39c159aec85c
3d22571ec98afb25eeea1acc0fe19857832bdb8c0088c378bcd38820e5de1506
8f41c2ebf22bafa8dc0d0968f57ed3e0a1b3a19f33066e1a2ce3d610fe995839
839d050424d84e7013f3f8bd75b2b3fde1af264fb045239d2ec42b36d00a5906
c8c7e54074a98977b543773197de885444d11f5da85bb76cfb0938fa834ac0d8
887df9bc13e168350fdeb86928b64cc8ecc73b9ad1fe7353a80b56a7645cc47d
62cb43b4438039c1273a61771db95d88a19ac1e5b8597d57865d66e809480a36
f6d5c6763894ba14d569167fb2072654be48e9efc90fd893e0eec922820e3c42
6a08101f685ece1b9648a878bd5ad2ee749d3e45f0ab749712ac44159fe38909
6646bb822d038e561e1457308346c9a57af9020c7490cbb8d6c508d60f3456cf
24034d1b3b878121008507dd575f6b1cdea8568c87e13c567feafcab9c8b8919
3d3a2c84ee23e21f4f2efffb8e933864e86a5351a85063e6c13bca974c1849ff
0169917d057a52b5cf7875c9812f837ce089fb9727d52ac4797c09dea9b70518
0ec99cdc0add4c56165fe15884b6a7e0a6c33e7a8c9058b651afa130b039b073
e56c7e1a93c5c4102ad4eacfbaa4cd87003dbd13b0d3f21a7868a18d2cca7e5c
d09319ee848939498ef68c02998a4ae4440155a1a46a80d8058c225ea65c2ad1Trust 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 972415 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).
Save both. The manifest's SHA-256 is the anchored id, and it binds the HTML hash — 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 1cfa9f07634a749047a8a17ea5979389b1c9da3257c87af8258179c8f0c6b71d; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 1cfa9f07634a749047a8a17ea5979389b1c9da3257c87af8258179c8f0c6b71d, and the block's
timestamp proves the page looked this way at or before that time.