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
3b5e7a20f0d8fea72e12ecc2779f4113accc210cdb730cd42983690759f58614
4b1308385c42c0112bc317be8733a4dd365fcd91b7867976350d79c2b4d6db09
1d3238446ed5b1bef603d2b4ea30769fcfcfb63bfff31fd1d98886e15505104d
cf95a56de8f557e70847b332c7a5ead84c7eb41e9e55106c4fab45889719f008
5c9ec3e9af2e71e83240965fbda06accd4529722b5b758c3528fc2c4594f52a0
2145cbd3a49b694d2ab77f694628dce47957922cd1f602563e2e2055fdb249db
c663074e6c333bd1f11d7fb67accf5c1b9db860988d64a076481a66259848c81Trust 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 963120 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 88992cd71d2c02ce5d6deabb1593dc2d33c1dee5556a899fd23f3e9f2f809552; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 88992cd71d2c02ce5d6deabb1593dc2d33c1dee5556a899fd23f3e9f2f809552, and the block's
timestamp proves the page looked this way at or before that time.