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
bf5af7c2fe5c6843d517090a33af30e8c12a648a36dcf211f36f1d18709de144
fa8ed9288130f09783fa27b4c4b7a83bd4a44b7c920d83246c5382eb3a2ca56c
3467e914b2e93d3cc664c5b3400d60557e703fc916dead3f47e79758840d60f0
5b56e9feb3dc6fcecacdf20b0d6664f7f3ff2ef5ca8f65594058a2aa22f6af37
40625b65095c45857c816c0399f9a3b72aa2f0c46ab4fe3fdca996c7933a4aa4
7cd181e9e85d0cea98decb33966d647d62e47a8d129d7c6c20530a4976a0312c
674e7324fba0161a664d5045c23a1c9e6f63200c919574ba3652ea364610f9c0
a2d8ca60937663d61e0fb0193ff67daedd801f467f567918eeff3f1998e2ec0b
a8fb86a996322d74020c2a3c7d9cea6520fc4df22f5d1cb8cef816640eb70374
e8ed4b78416581309123193967480bfc674bba93a7fd66dc678dec8eccd60834Trust 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 966031 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 ac378f8c43978a10d35695b57250244f27d0e859241b97947b9b88bee041b1f0; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / ac378f8c43978a10d35695b57250244f27d0e859241b97947b9b88bee041b1f0, and the block's
timestamp proves the page looked this way at or before that time.