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
b0bc20c88d9a2aefd971722a004fd3fa8c7f96e843bf9dcb5e3a9244c3fa2700
858a6e21b0330dc31694549123a42f4333c9be4f96c453929d2d1318931a3d0f
b8c8aec2424dcfcf5f2ee902161a1c1cd76762408f948a97621ede8a12d7d715
1495605c6aa2410e440014b2180cbb119b8a2d610d1228730120a52768dd5251
5d48367686949bab8c0e830b72fad723299d8b4da10e8af90f49da056c37c65e
536a51d02ef99e51fcffce777b6df1b646ad74070633916ad9fd3695cf6deeb7
4147a75bc4bf85e1e5ad9822a3f3381c574fcffee3edded9761e0066b8f8dc58
5fb5ea9bd7df09c6ef5dabe91077e0ae3b8a2891165739b4002c5fd14eabf5da
7c643535783f82c4a937d6186f19971689cf9799d352735913e6917aa11ad242
3cfa6ded0589e263e5c9fa7556a5fbf1f49e0357701eadd5ec5dbdde11f1694f
7996da4770b540fbbfad952005501c6d24c4f014a3ab109806f41202b6ce417e
c7e3507b250e692da17d0b3d9a3bca6238376b9a4b8866a68af42152adee9a39
865a606d71c0e77afb0ff41057671d5097f8e41d3f81deafd68bc5a27a0b2042
d58c068194b8e147ef8607e9b2e71f264d9fe7dc1c10c5f01c52002f995b09e9
6aeb9dae150704f06b1ec5218069bff69a56608c87881b04131880b52a3e9062
6cdbe492ac82b18cea75c67e12ba231956306ce117d98f8753976e7a1331b4ee
7c837088f83f62e08e9e02e2d9f548693e7e843abe9a57ab6e8455b95ca332bbTrust 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 962329 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 f3946edaa7da20d90ef158659bad2018afa2a285951c790f2d011355646049a2; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / f3946edaa7da20d90ef158659bad2018afa2a285951c790f2d011355646049a2, and the block's
timestamp proves the page looked this way at or before that time.