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
5a38b0b670e81ccb23a9d28f82e9c12e637e43597b2766902d74739d5eebd40e
6f3f658c75f0f598ec9c719508407047979c35c79edccc1a2ed4e638e538ea0e
f17c9ffb06be152435c93368d0b690a55b5c6703336c6d3d47c5dce2806c75cd
d3864c1333a5bed9a7ac1311c6c35412722ed64c7d548f83d2fa52f7d6bb2e69
2e65f2ae7bfe7945312796fb5395cace9844d49c3e4841b761737b84e8b14bd7
daf26e89021b6f487f7692506e7091c264f495fde92ba53108c9dd37dbc9dee5
4399e96f5a918b2fa2493f4655cb41daaf2e88285923094f25bdd358d8cff8c8
a02dde21e2181f648b062d32ccb1cc28ad7ac5fb69bda98393054a175e1452a3Trust 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 964299 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 24650c4afd17f5377404fcdfbc00285bc845e461684b53a2bd5bba1f13d07e34; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 24650c4afd17f5377404fcdfbc00285bc845e461684b53a2bd5bba1f13d07e34, and the block's
timestamp proves the page looked this way at or before that time.