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
0bdbf51da2df93088ab58e9a59412a754642a0f5222555fe4bdfd21c5eeeb82d
c58b1a0161b2f23206353be52654781263be2fbe2623d514e6bb8497deed55fd
d4d45b8c43fd611ce948614321b92509ae5ea4b61f12c839fb0c155b0dfb421d
f0fc6ee07fb268a2e77df7f91abb5110d20e93b5564daa17be705c871d3cd0e7
07419b80a278140abbde099e4f63b4d19a10d8d1377f15d25bc37615bac544e4
53ebff80f18f9e5608aced5890731bfb79aac6edffa2a91988892dc56d580828
cd7f9fcfafddf1a6d2011c61d97af06947b5bdaab19a33f53738981b1473b1ad
8a3d8f65cf75a463d040ecd8bafd3b683adcde82924255f0a9fb60ef6bd74b58
48cc28106dee56a6c1449ce96e0755cdd997e6ed51ba8ccf17b913c70aa15b1aTrust 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 963869 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 2ac2efdafcccbcc7e17a81e462751462f70c052b5f3fc45d2e6132edb25a8640; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 2ac2efdafcccbcc7e17a81e462751462f70c052b5f3fc45d2e6132edb25a8640, and the block's
timestamp proves the page looked this way at or before that time.