Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
af98ac9d45a164134e472bb8a90a2bfe66c04e0746292d9c2a6eaa5c6bc8a5b3
f04352b6e3d5c62e071109095eb38acd433a8e3bf70e8012edabb5f7a5d0daaa
78cc8b9ef446f93ce4135451afc60b468f53a77b48ccf36bfc2128577546fb23
eac81f88b126a4e12f01e1e3aea5a82500cb292451e611dc948be0e75d987fa5
99ca8772101d5cc0fc1113def108d1568ba11a3d399d52856494c15bdaea35f8
080db72d0f70b467aeeb0bdad76a1c3fbbc861cf97227b5a4ffcd58b7e1efc5e
4ce95c01ff92deec58f5025935698a9e17506258b7e87e1a0d7d6a11277b97c3
4ba95923213191e9ff79f95cb8d60397231d732dfcabebb27020ce598a8de072
fdaeda53f9a17d30b1c232e6ec0d25d07bcce6eca7a8e1dba4afe67cb5fb8e4e
b9dab46137e803ab0efa765a0affa7a891f0ad4a18d3d8481f5910cc16538950Trust 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 963163 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 b6045fb0118cf22566069220939894dd680af54e9d026ea390e916848822ebcc; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b6045fb0118cf22566069220939894dd680af54e9d026ea390e916848822ebcc, and the block's
timestamp proves the page looked this way at or before that time.