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
67e70a543a63d351afc9d90a886ad5c427a8ac0620888a437ac5016bcf209d0a
5d07a7f586cda2f3144ec7689bc0be31720c48bcc64f1c09750a756d10119f5e
35502f66018be5020e38c5b413f6d1c1b9c1a852dd91124e07259af4991a52b9
7742d9f6e46d27363b8c5158977796da939eceff97f51958fe77e72b2f884861
a20596bb37ecf51af5486c6897b9115174e659effe774383679fb0b92188c638
c93387303dcda4a7c4ff338de300c17ebacb051fbdb1695bc7cef57ea3b94da2
28c8b08535a8a57c174145a47d9f338017cdb186df40849af3f4c67cc3890dda
6ca0dec748604ea0cfcf4c8291a60b841672be67088751d34cf2b680f4c0f959Trust 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 962235 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 5836299a05364bad7f9fa01374d6e813a7a8c9b574f6df3bf4a237536c234092; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 5836299a05364bad7f9fa01374d6e813a7a8c9b574f6df3bf4a237536c234092, and the block's
timestamp proves the page looked this way at or before that time.