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
e9c840857e3abd6d60bf177d3d485e33c8898a9d07209e75e7a6f9282287fe1c
3572add3f178480ac0fce8ff7fd3c1d18017f3a332770436ee762cd75a4704ff
6bf1c5aa3968c38802989217fecd6d443aa3fefcab399376ff9e4a4b234751ac
38ce0357ba32bf4dcbc7a4652ca9725ce2dbc39d767d07e2b3c7d344623236fa
0bdedd544c81221a1ee0469175e52355c7a80eddc7cf53ee9228c8cf9ca47a05
3dd10974dcf5c0c4a3f5b60b7794867f1a98ae3a2eb6e80d00749eb2540fd919
40ed019dc40e96f826ab3a72e74fdf263bda765900c4d57c3a0897451487bde5
7e2f327c3b205b524f8994a4133c1e2a97498a8720f23fc35fa2ea9965677855
4d06ab78172bba4ce1852e7e65c1ee63f3f22eb2dd2c3bab99b21d84a59f5869
92d8d8d71b213d8d856d7c67bdcdf4405d43e135aff12f200f4c7ab94ff3af63Trust 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 963507 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 a98b271a0eddfa3a93410c43f26f223fdd758505b51459c20619462c695a43b8; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a98b271a0eddfa3a93410c43f26f223fdd758505b51459c20619462c695a43b8, and the block's
timestamp proves the page looked this way at or before that time.