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
c90961eeabeb9cc594685d1b8809f50050f79369b01a507705cd4ef9469bd865
a573352918ea4dd9e6700d7a05270eb2f401b4ce5c5bf454bf948720af49de2c
e0791211d3b8180893a40fa183f4e856b0ffe9ee02df9e1ab7e2328e3c666062
b95ade4901edb1682ab3f0a59cad9c107c0282deb796e7c12351c38cd14d2128
f1512a6140f9a22ff9bd3ca3dc16fd241715b0ae6a6cf903cf827d7fdaa04ab5
77a41f1a5b91197824ff8432faab472d74bd1790b16763a0b5e739e452b64dd4
8529c4b40dd6091d100b48c3c3b754b7355c7ea9ab717b700c0c285edb75c043
5a942514c3e0eeb938438710ffab5c8b345d3d5054960d7b1300ae814f35dbc8
8850d5494810d01e0e76e704d55e77dd701f9c6e2047e7fbf63fd72a3c336bd0
e8f2522680cbd5cf8825dc81c8aa1ee1fd35cbadae33d583cdf1ee86e6e915fbTrust 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 963969 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 ac40c170e00748fe41726f70d9b8f5859f49fb23fb1fd6702680aaf6bcfef194; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / ac40c170e00748fe41726f70d9b8f5859f49fb23fb1fd6702680aaf6bcfef194, and the block's
timestamp proves the page looked this way at or before that time.