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
07827b29b382a59bceea174c4217bfddac6651fb2c9c9f8db94434f57ede6923
afd8cecdf2d62673c903bdea1338451d7b0ac1fef68e4ef7d28868c2f59e74d2
f26a45a30b56a6ec64e764126978bd2a9822f195eada737d9ffd700e3bf440c2
e3734776a6c300c5cc9add0ceef76a27b4847b2b9e1af007a49f3edaf00b002e
3e1eb40feaabff98d7da32daff0d5a28250a4864318790c165a7191373d1663f
88923239d71f4948c039af922422ff50aae4d895a0b85eee3f8d0dd7e8fa17bd
c20c73a30a423a12849852f14cd06682013d23af49b3e8832fb32076ac4710b1
9d19deb216d8d168731e27c44e16dd8b7e0d357a22fe19927ef16ed36470303c
ad010087912c6cf9553405d2ef9482f3128f7c0448624ba17724142716623fcf
c1e231a9f56c1fb9fb96d12556af1f108fa7e74635599cded5f56988ca3e9368
130159e8c7d0b60fb45cb02de8d13a6a866ebf4db6bed8370b1a392f034d8aa4
6c5faf26f8a735ed110425d1ea83e494bf05b958056598ee3497db4034a035b8
4a5f819b698594062bf4062e09939e6705e82997708670bdecd95270c314afd7
64295dde51f09811c56e6564e7dd5a26837a9c14299f77c95a92d6980b64d4f1
60cfbd8c703e648d7bd5a0f7d4c5fd6f679f9f7452270440b9fa14cbc6df829a
710cc3fbe3eaa94701d0cd28b4f078b53b37f0d14d6c6c302d62ee1c05105dc7
428240cccf46203b09f06f2d9085d1a4ddd99af2384c97f653f35eb8b8be77ad
e9b301fd744a0914b15bc33b099a8cd193ab9d97c507610c0138c804176fb50cTrust 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 964873 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 5ed32459b172a104a88ac6bced67735adc2db01c001904a6a669445dc2e91584; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 5ed32459b172a104a88ac6bced67735adc2db01c001904a6a669445dc2e91584, and the block's
timestamp proves the page looked this way at or before that time.