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
e8e5380e9b64ebd5703bb044b5cd2469673692d41f357f352e627144fe597c1a
f507baa7026a5bc491af352e144dd0580e114a440fc0e85fbebd9827191c5c37
c85f32134570009ea13aa7bc444a46b5cc5a38d0f5c775bd7113a69911646a48
c6e4bb7957b8bf0fe02c81d7d1371911e236531adc32d11bc19c797e85deeb96
4920f3fd42d809f2f5ebd6abeea83a1483d4e88f3653980863c08425d8043904
d3057b90ce92215f142c67543ba8caaf12803e5fffb0ce704f91317dfe95f597
4e633d9daf5057c811d614bf1ade5f0548ae39c53d92dac36e27161a94e51be1
8c8617e08bcfbba52dd276051e8f697c11bd27aeb6d8625010849d922583fa1b
7c7538ae6976b338fb2e7ad9d8523b224199931e516edae235cf0a4e7d859815
756a72eaa775920d00f74449e3d41d8b8422ec801be477531da75cf58d44bb65
321cd9a5cabbb6f6acd8e58f992b355f5fc84db3d48332735ed6e52bbd563f5c
1a275c9de96e883649ad005b365cfcee25cefb900e021ff500f9ec4c68588877
d1293786a795db4d08f94250620db122640ed7c8bd4353f9ac5dfeb7665d8cb5Trust 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 969931 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 a65802541d1d103da4f12039ad5a5a5abfda65678c7ff7f3c71cf9a8f2b48742; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a65802541d1d103da4f12039ad5a5a5abfda65678c7ff7f3c71cf9a8f2b48742, and the block's
timestamp proves the page looked this way at or before that time.