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
6920c71db1859a774263aab9a05adcfe9b27ad9f763da93a5272630f5c18539b
dbb17dd38a47aab96fc5ebe2b55f520b1e2d236464bd69719271b41b8749fd3e
8cdbe0df9693981f7af186f65d859c217f85ac19a504cf250462dedbce432d98
0901d7e0cf7014e7b90da787694e670885c1c8b28bced429a38414181d26d61a
0472b647af1fb880fcd288ffc0ee2bacfa08b747b268cab52b475b567444fc8f
6d712b6278df806952fd63f82306fdc164369aa104dde90bc24fc3de533087a5
a1138231b97184850257877e4408039230b2a3e51aaadcf84c88ba6dbe16498b
4c0112b9fbd4af3e723286cc6e41c347ccf5df8711d28d63ac364277da48ed66
994589e90ccd5c04c763279fb4ef27384235f4dcdcb7341332cb1d6885cd4b8a
7ba4c1e7029a1fcae047e27c76456cd1164f8b87b5a9b7f112cde7cf2b4e5960
3e67560a124774d25dc81c584af9b20971440624204583ea65ca38361fca0db1
8e0aa3b1564499c5683837f8079b1fd6de3b4918e4a639d2f0fb88032bd2d6bdTrust 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 969027 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 bd767799f59012eaa271383adb49f883b75d0e1d1bd1a28d222213d41b56d1a8; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / bd767799f59012eaa271383adb49f883b75d0e1d1bd1a28d222213d41b56d1a8, and the block's
timestamp proves the page looked this way at or before that time.