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
ae0473d7e62edd06f2f96d0c14de34f2cd7bbce20242bfc699d910202da20614
0ef439dd1d67549beae7b00e396dd7786ed5e7e192e72ab1e01c8aee8fff00b9
bde2e83714ee126183b0971ccac8e372f38b4538535e41c1a2fb52b64f9e37af
cf74cc17dea01cd4cfd42af91c7a52b54e976889b5562007dba22d8c8b2a53c1
94678f1e2a0564301cf590b5706e0ecf3036bcf22ace53331966e3b2a35e4f0a
47e232b3632d1f6744a4a66d183285fe3c1e6e3fd24f2029a0cf8d0c80e1d4dc
0a5600449ffeaa01ed0c985853b2ee74d42b805f8559f093a47d7e7b2c88994d
aefe4f46fb8934414ff2802b0a8ed4e576f519f685a417f66f9bab0ed5692c84Trust 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 962402 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 f3154554a4e5e528de5fa8009d1d8125a6d363d0a99f7e5c53efd4f6ccc905b8; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / f3154554a4e5e528de5fa8009d1d8125a6d363d0a99f7e5c53efd4f6ccc905b8, and the block's
timestamp proves the page looked this way at or before that time.