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
872b83a55584892fa15f588a51eb9c4448652bf646a062e58e9fa9adaa2be0d6
982fdbd16d801ffbc6c0a8d42b7b7559c584340255d0bb4c52ca5f293aa7f58f
0799711da3da2e46cc063951f7cafe477a6b492f49499b3d68d1b685bc622c25
63de1f7e9459899064ad8e2f35d5d96dfc9b206668318d07f850442a80a47fab
d4afc671887d18eedd8c9ad4ee52163d8b80a629fc13bb14f673fabda0255343
68c40c0c99fc9367e35c116e9d8fe9e7069998785c7d8188c8f31c23b0813232
e08e5b6a30f58d507f7e68e5eb22832b63c99e18a944a2361a94e825434ba534
34ba772089223bf800471f5b2b18e299e8a81e8561910badb8224aedb487565a
0f203e0f175031efd95b44369e575526884da0bc012eaa89cefd062a48c80886
0c52d9f911dd737d0897c5f4982851b6b4c76bedf4503a576c62492f324c275dTrust 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 963217 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 7247f4fb49def219efffadf37fc72d8ada395b457f2940a331afb4997e738227; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 7247f4fb49def219efffadf37fc72d8ada395b457f2940a331afb4997e738227, and the block's
timestamp proves the page looked this way at or before that time.