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
14dd59bb38a477108e1709f2829e6cb988137ec3422aa4242552c98b3a21a12c
d5095097f68d40866058767e9823ae14ab803d8061462330f2aa05262d4cb52c
4a3931cecdaa3a3ed4dde113e460fc50ca189981d104bdb74aacee519c26750f
31dd9db8daf27492318bf805bf2dec33cf6d68db503fc0a1f1d85cd96cf5a349
ba7bf08a92976e6ca89c83fc8384740d8f33e13b7e7cf7422af452d2eeac7bd1
cddf425a151164fce4bf8cd5d1a7c61ac88f4eb0780a764814f6edfd75c92962
8a4ad6c72f79fbfd23065676c3f6cddfbf0a2b5f5c9960aaa7ed66923a9e060f
3e2d8956f830ab58759495a2de6fa50d625b6a6ad66dbcaa12ecb4bd1daa502e
aa7c868761fb11a8cec1601bb524d53e7dd053e203eeb240b572144a8f2e572a
a862f35a94c963dcf44d042da9cb5440f175f25aced48e6165cfdea7f95b2c5bTrust 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 972622 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 9e772be9c5de3734ea49c6fc353c1cc774612276d995fb6d39360abf14bfa9ab; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 9e772be9c5de3734ea49c6fc353c1cc774612276d995fb6d39360abf14bfa9ab, and the block's
timestamp proves the page looked this way at or before that time.