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
77cf3944d6ea8e9b2e0e1fbf9d925eedbd9eae52e87289e7a190ce1639474a8a
e2f440b336bb33d225a0d5b1a0a6747898b9f1c2312b68a840eaa1c3eff53888
bd96950de3f4630182eb63c7c29de3bf7e95e0501bb6c680f136acecf5132b76
877f33bd12662527fae7abdc91a0726de03104f4eeb5c6519e246d830463e7f9
f59de64dce80acac9612c8385c2f8a8489efd7b399d40d6b8c0a72e7b197fc29
3c371a40cfc8531a23edbfd045b28e7e957457c5395cc249b257f0859f80d439
37639cc89efc8023beae05f94f5267679650e400455119bdf379fe483c52be73
59af09919b898866c310fc7244bc89a6f73230f6ebe4fd9f1ad0f321efd1de96Trust 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 962528 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 49b83b5a654f85625229b4b3d4e79c052fe2f548f929c4817e8ee825549beec9; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 49b83b5a654f85625229b4b3d4e79c052fe2f548f929c4817e8ee825549beec9, and the block's
timestamp proves the page looked this way at or before that time.