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
b669ab85d57be2fac417b6764183431e598debd2ef0ec9ed4a620e0f032a7f3c
17ce7f756cd62750ce5b98c0332fdb1b83a310d731e71ee8d72aed9bb2c22277
14beb6d61751c352f5a3bbe138e4d5296a03ad9a9e2554219e17df69e2a68563
642cd58a65c94dc7db0fa6865eece937639a73f3f9b42bf0076123aa90816b76
2687d50ece247b874db02cfdfccfc15262b7325a405ca19fcbccc9e4089785f4
e20303cceab7d6cac4d247881a0c8094e662f410624d93289058d0a6f4636ec4
a98507f12040e1063b60d9ac092b2b1332f0ef864b2fd37f7f0b42006bbe2051
6cfdf9c8d087cb6fb9f9ebe714da9fb98da1bf7b07e9fecccd1ff45b4aa3ea88
2e9ea077c6ed108d1cb214f1efc39c9a9d8c7642e386286c674b792104e92bdb
b0fb8a73d116e9d6e8962b8546fd8290930905f1802bfe5dd9b9282a2fb77575
58e474e168f6744a0ad311f854d9adb635c6b93b69b7c5a725e052689b741badTrust 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 966217 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 bb47238fbc3dd4db0fac6b571916032036338b47be6d74f71c407281b069a998; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / bb47238fbc3dd4db0fac6b571916032036338b47be6d74f71c407281b069a998, and the block's
timestamp proves the page looked this way at or before that time.