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
f0f4210e771fca0a3e6209b59e4f4572df2e734983a5399bf2422cfb2bd0ac41
8decd521d29e8bbf90279e44485f3e4f431b890251880a435406d49948e79086
7fd82bd6f89e14f4eb494faa17f609b980f3941c60127b37078a0a258db70bd9
d26405e8ae87e1489e10513a77e8a2d71f009e71954465d4297adae63a3609c5
d33b06ae7fdeeee4cf84b2213f8db313ade89ed193466f33dc29dafebc961ad8
cc912333fd5e51c96fcf286877be2e5c71ea89c99600483c979b17da2bdbf227
60d80ea0e87bf99dd7be2b90e309109de707e8194f38240f5e88079fc2c93fba
0c0821de66823b432e0e0a254d57ac10134e929dc25f5d9c1ae3533409e7ddfa
78bcdf2c78ae49173699275bf1ca59c39bec32d455743423464b9f49ed5d0b69
deba00d0641e9ed47182aa193627e64ee1beea0133c3512476a7a73d273ab305
f978ec8dd7d985ecb3ec523aea708d780cfbd0c65e3de4fa36b8168a1c357297
f2cbc8fc46535bb981db47fb21f0ef204432141e562f223b2f21680486c82acb
e3679e7d27e37de9ef24803ea00bf5f7e52b40f90808dd52c0b77e3772abaac7
910f872d2eaea45b1944b8cb56718555101a5934a071f900026448cec649d241
8e21accfaa99f67cd8fa4e805691090d9e4615da0ad99352f40db7731827ec4c
ec9e6ea42cd5cb9304e95c700cf8a3b5118f36eb3759cec2c04394d67e914e41Trust 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 973365 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 37e01756dcf56bcd5b828525bbc484207d3a6321b908f8105e14d380c095376d; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 37e01756dcf56bcd5b828525bbc484207d3a6321b908f8105e14d380c095376d, and the block's
timestamp proves the page looked this way at or before that time.