Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
550e77b3a8ed1c93a5595de1997d899db8185aac8c892a4d931eb21390e1ec0d
925f0ed8e7792c4bda710615fa5d491f3298394e9cb9aeed98f275cc0f7e0ece
a7db062a4a572872b37d791dac9370a8f7e1df9033bbdc5f9f19c80c439d3419
449bf2cae63458399fa477d27f193fabd6e0d40527b9386577e561de0c659d02
ef5a2b43a9f21a342b8fd196663044a65a37a8d71952ea3626a6b7a81f9cffbe
bb45fe6694c55a2b5a67d1430d52ed619eff1e2be2013d6b4dd695a8691ad09a
4623ca290142bcaac5dbea0e63a810947046377221972ae0fec2d2359d46ff5e
ab2d07461fccf0d7c74e8468e8157b3d6bc493b5799e4a95fe8461c466a04d7a
7fcf65188bad7354c3afb48c5cf0402e8b0a7bd096d2e918080070aad474320f
4a75dbf3f9d8751e89325165e235b2d4d2c40e34f888ea56f81fc9c32e54ba07
3a103d04fae4686144dc8b7d36d9023c66b236ac42f7e788ed563daabc3c46dc
b4f0773a4200669c5737e353141c96eac734c105d2c3e11548cc104a44bd13fc
7cd40929c654c8c6b4700c7b9b33ce0e540ea84649cfc9d49d8921129f19fb24
e6a6afd1595ac3db4108466fba483d638ff6bcf24011c4b312ab2d84e9b52a57
b4a7f1308bf3774b061fe39b050db5f7f28565fca0bf340b1e2cea93d184e6e9
7819d2a6247bcb07fd6f0f27f6c19ca311e27340bb660812e70fd88a33d874d0
755ec26d0698e5793ace24f7e63ab67655fbc44cf3a17651d4fce082117a276b
12a5b9c6d37d136ead52f0b6af83ffa2a74379ba49c84e14d2b150aba4393e9dTrust 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 964330 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 a7632f3fd92ae8a84e9da94fca427af2f2edef827b084bc2265c761184eeee1f; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a7632f3fd92ae8a84e9da94fca427af2f2edef827b084bc2265c761184eeee1f, and the block's
timestamp proves the page looked this way at or before that time.