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
88e8ec232a339010de6e8b7aeb65ea1f21c1d8405776a897039131ebc09f4f88
bef8d7b6198884ce40538325ae71d97f6d7b04707838d0a6db800742a8201b35
dfc85076ef619e1fdf83e77b728fd0e9c4be080c65d49009d088e86f11397d07
13998ec18d11d681b4b6137caca23f51a924a5ae1c21489365d305f2c408c550
837732d1aab1446ef322be43d7da3c3e3e3e43fdcc3d75a32b1ecbebae0e3d12
9ab6e7067e803dba446238c8c0dc12354fb32e1864e51418f2391471ed9d3dcb
ddd0f050750b8cfc5e2f116730e4f38e32b39bdf585a49ee0b9a02b4adb79697Trust 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 964748 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 5cc1cf077f264243c693c61f14ea369d6918db14f44eaa197b95fb51b75fde0f; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 5cc1cf077f264243c693c61f14ea369d6918db14f44eaa197b95fb51b75fde0f, and the block's
timestamp proves the page looked this way at or before that time.