Web-page notarized
A tamper-evident timestamp of a page's content. Pay-per-call — 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
93393a4866532f4f53a66ef952afa76ae95f24879f9b18f3152d3f424df4ed7e
c6f6d8ab554605567994a87a29932ca0298e73d3a7af1fbfb0dcf01967453c84
f39cc602c83437c31aef876e6ddb4f38df7ba1fbd55cc69f66db714bf48bcf0b
0e7070ddc2f109204de4def51bcf05113acc2ea40133b770c544bb3e202d8fab
7ab20e6322dd58a93adb4963f16b77fb29d7453545ded6b39c537520437ba946
27aeb69c95c844054f52c58668c9b82bc803ebf757fc186524a497dc382fcdc1
61f32b76b9a804c79d2f55f631f5382305357cf524e4b979893b1a2bf707338b
c2116807f27e19e1fe5231d3685a0f11d33105325f851ed072ec678ec915ae36Trust 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 961946 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 61e44218fa324aef1f780fbfc28f76d196028b8ff85dce9803d6b6f7855ab495; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 61e44218fa324aef1f780fbfc28f76d196028b8ff85dce9803d6b6f7855ab495, and the block's
timestamp proves the page looked this way at or before that time.