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
8ba8d63ac67f5dd9ce95e9f051bbc010f3307412c0ad7adee7f7a5cd14a4fbdf
22f28187168500c8607d8cd1fcba9ebc13612ce48b8bbbe71e90a4deccb4b7dc
815fa383abad1dd8b0b31437ce4a949e31e470bc1d5b391610cc9b8f917ee65f
4a2f2a346d70a0a1645dbd633796808001021448405db3bcd1dedf0f8840da47
01c6ba68c407b654eddcb858e26dc652f42cf9d07cbe6c5b13d856374db16d98
5487ad0d666b7b5b48a4fd2b367d225b71cd469e018372510da69632a2aca775
43d5edd345e4a0d160c2a7c0df904871fc4453c69a81a778cff4ee0b6f7208de
1eb3620b35fb168a68f3194f108562bc340aa6be774c52ecc538610407ff9bd8
8a51129ab8ef814b9310ce133a28e61e118fece35153e1728940fae0b9f84a80
ef5979e6166e418e03a9bbdcec49534f773b7b0924a41411a177eba68e4d3b03
ddc3d32184150b7815c756bd4de4ed64fec6721bde2535f67528f3b89122d720
ec0826aeabad63e8271d423f0064ed35f5c2c9d0ff85a10344826a0fee949a72
fdb0149df872757048156099e798b0da7b3cf9a299d28ac726e478ebb3dd547a
20d050dfa830d3eb3c1332086792e589cb69b45aedc6f1e0e753ebf82d1e6d97
6b2be6a5107c7a93d15a87ea953f2dc42f5077cbacce5b9f0e92898c1ad3c902
c014cfb56e8e8c0fb14598e63bcd63fc34caef92c59150bb20454186fbbfdca9Trust 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 972230 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 68f22f3c5611a8eaf48d85d85c9a2c344d9819f860ddae64df5ec4c7535dcbda; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 68f22f3c5611a8eaf48d85d85c9a2c344d9819f860ddae64df5ec4c7535dcbda, and the block's
timestamp proves the page looked this way at or before that time.