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
f6a3669d3880bb37845c1b40d4ac0ede9b684dd7990d8eca5f01ccae80b7fa27
482c09c12c24dc86e5e3bacecb04a42cfa4fd19b322ebe1a06dd294905c10073
11850812bfcbf4fe526c91fcdf4ae78b410efd9335a0274d6f061b433d1ef666
865a338d6f379645de6bdfba668c6c0823f9f68721528b4e74383b3b05e32bc8
a85bed662afc528414593e5f11c0c2851049698bb3f87e6e8f47102f224834bb
884e9c97836079fcc2baeb186a7e22e2ac8f5cc6ec74041769da8270dc359742
d3e6d79631002ff11b582128a80913421739fcb0ab2622879909febbe6784253
093d89e1feaa3715e117bd2a04fb6909ecbcd3cea82df188ace5c07ecf611867
b6c70efc7d0c110719920dd50d5b3ab65667c9e162d84ed3a04695b6a93535f5Trust 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 963035 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 41c6b27e3434d05a1ce895cf38cc9eea59425ccce42df52b2af966104ec3352a; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 41c6b27e3434d05a1ce895cf38cc9eea59425ccce42df52b2af966104ec3352a, and the block's
timestamp proves the page looked this way at or before that time.