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
a74481de255323967a25dfad432298128acf77b0c80df742f396897e1de15600
a1154a5769e3141f9d704cabc8e157fd770ef5245143b7fccaf5e086558be597
a3194750a0729247c8c17b1daf226167b65243acc8ec7aeaf1c3672ff20f46ce
0a956d693879db56bb8b4e0f76756ddafa2c34650f16ce2c51dc7b07db97befc
866c3a57bd038a97928b571cda7451643f1e576b9faa1b14c14e5811e934a211
52712fabe3e46a955eb9cf5ee3643113a258925385965694b0b5bb2974d29daa
6e84f9608a6d415e20daf28f6658dad22888de6dc5ab32a2e1db63c556520491
d685c4e37155998f7422b6b429beec9c7c1f9a6c91a610d1b43b92da7789571e
0b911ff9a41fbb81503d9aa1722ac8ea4ded075e17c81fb676788cba0dad0361
*
*
4b3ffefe39935f84db0ccd049fdf32cb04555cccf0587e756baf2b3db634c1e5Trust 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 970433 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 3fb83df6f6332d26933a1f7d5f3f33df25f9f25d30eb8d00fa57b0f84d50b7be; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 3fb83df6f6332d26933a1f7d5f3f33df25f9f25d30eb8d00fa57b0f84d50b7be, and the block's
timestamp proves the page looked this way at or before that time.