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
94fc8f3ecd97b68d6c950ea736be6a150fae80255e3c340c69190736eb5a3e70
20afe3ae5fc0264cf41281648debddbfa7317d1ea07a6014e1a5ed69d957c048
abe4f37216227340140fc6b3392cbc6139dd68307426e817c2c8d22935fee720
ded5bc8a6bbfc88070aebfb63c3ebd4ca088ec3eb9362cb56806b7263743e291
e5c97c7178cafca3b0cf3bb6c502e3c4041b7a2e74cb1ec5686ccde637b864be
a0d71b073cdaaf5d4d5039af9d6f887fc85809a313bee3d5b659173d6f0da7f9
cb2b5d1d5461e621a5ea164c51c268ae173cb2c04e34ee39864048a453ffc27e
c7cfa33686828687a5afe8e07e090d724b19c7b8d0d903f0092c2bec7028ec3b
c6dcd2f7545cd8564fbf554346f6bd5038e7ad305677e904f266d10e79f6215d
7ad365fe4f577fe255f3aa06033ddbcc1823499ed8573e590a72a77ec069d78c
0f83926b3c863b6522f3ae904b22079f90a07aae7d9e52120a7842b5dfc51907
9ea6f7b50defafde03864d70042d2054e078e4abdc11dd6350c1eb7833de4ee5Trust 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 969736 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 2c9a64e1e1500bee485921b86749f907f81e1a13a2534bd843b6e8e491ec7716; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 2c9a64e1e1500bee485921b86749f907f81e1a13a2534bd843b6e8e491ec7716, and the block's
timestamp proves the page looked this way at or before that time.