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
fe819e6e7298f0e2899134baf363d333e78d9fc5f08c7e9a9e3c5f4dec0cdf98
d5b05bc24d37bc9e104673730975ab5acdd8c66c3dfff1934c4805556244d666
c527a33c44de000c91e8f892db685932020231e487a073575a8c35a1c8368057
d0b88b1774ec16fdae3184c3ddcec1b2eff47549d771995dc7c0047469d9c583
633e69e350d9072af9a9ac00c812af1ab2d6d94415a38c5a1729063024761251
51a1b3c72e74906c33bc3946287d4f292ade18abee9d97de9079a408adbfd426
2bf4325499ad5a66d367acc331cf07b13ab301b7e39f711db57e886569c3466b
2311eb68ba4d84f1ec9104a9f60295ce6e86ef860cd85b156cdc6201f8e9e816
f1f57766304cd63d38be6187a9b7a1b134106488cceac2c3ecd780550d7b1c84Trust 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 963562 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 95bc2feec64cc2ec0a9824a833b0916f188da1de98af06621702ab2233fe5d6f; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 95bc2feec64cc2ec0a9824a833b0916f188da1de98af06621702ab2233fe5d6f, and the block's
timestamp proves the page looked this way at or before that time.