Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
73ac18b324102f2c34331dec1133de033857a2a34ee2038aa0d2d125b4a9dbcb
5a95bffe552e7451024a8b95055bc7f38483482bd8cf449e8304b8414b26f4f3
2e8878cd2cd624bedc0bf4843d0cc410f89f08e74de9f1e4cf64dedc7b0a9b58
442c24a93a9465a2483c0b89a463f8ba47e6d422e5843008c4f240c282cc58a2
a455bf5a3f0db69d0be23846c0cd9ebef30e0216b27c9c79bb18a26fc988a07e
a81e6b80fb77ef143ac2bc5bc13668fd6922cd04720714711a2b4268bfd2a41f
de2f080b80b5b4f12f00a32271c0fa837865cd46d5cd3d52e8266eacedf00936
eede51462afce6f138994eb41b8482e66a26e16726a3df42eb892046b38185a7
825c93409726804528e9096772fce1f7991e40db6f0d7f5c738f189170337a65
949da8ecfc7c2df976857ae23054102390ce013cc74614b794d16cf9935da176Trust 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 965671 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 d526fc5d032486135c2def6b808dfdd88e3ec1f70eddbd1976b42f8e5bc7586b; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / d526fc5d032486135c2def6b808dfdd88e3ec1f70eddbd1976b42f8e5bc7586b, and the block's
timestamp proves the page looked this way at or before that time.