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
b267b85aac6a8ebd31e5494b66b54bcce6a66db79af32d3dca85e038877c7ef6
b5de394386a03623b6730fa6a353ab44bc3c0e4088bbaf1b5f4a7229e11300aa
3643d21499d9fae140eab609ed2ea976e96edb2ad1c01ee2392504db436197ad
d4695e89fa05c0509c2ab150dcdd7602d1b305e761d30ab4a3ee0d819ab9a83a
ad2b07949ff620d73f6230dc4c28b40bb37682610fee9a59eb8fa9280ffef90c
7771eade04a9027cd2d2ad8ddbe8287b51cda6f44e5527e5b1b694611bce7ac4
bf8770e252bf1e4f8734b77a726fe29a241d829fb1c929e49bb53ad0522fb618
863dea73a04c306514bc7ca031e01491c937adecc577f8879754dea66f38aa6e
6c6aad172fec8bfe9087e927af244a48845c775048916329b0011372cb2b39f4
31f12ee15d45e952a82ce0ba3634314143091d00633677511b62b7e02b1b9322
f76d7947656521d1f6bb560acfadd267c748407fb592b6986af72b6a267130ab
87ec5cb3b60516c5809cb084c64833896b11a140ab8929fc7776b8f75d120e95Trust 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 963187 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 82933ecd34e6a5f18a7e8d1aa38fc8ee032feabff1c64ced70037e075654f408; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 82933ecd34e6a5f18a7e8d1aa38fc8ee032feabff1c64ced70037e075654f408, and the block's
timestamp proves the page looked this way at or before that time.