Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
1e5ffbc9f4ab0dce1f398b16809967ad2279b9a4d0accda80af9d20bce0e7c0b
a82184d4e474e5e43b22d91fedcc396ba18353ac40f08fcda8b065099a293d1c
581e922ae24b658e7b341e2c0e0b69c730645c2a4766495f116de695c40c2eb9
00b4c96e619a4f178086472f8f9baf9f5ced8968cc590c0ae53cc8ae4dfbbfd1
dd84f4f124cf56c301ca26e9c1a800541e7ff2e52a44c3fc7c3cd637582badab
96b2bc51fd71ed09b1e8aa684d6df8d04e767b481b99d0792fc261bd97331ef4
0228ac5a45e1239f620b7c7ffdaa9399ef4edde00ea24b41da5ccb761d7e9b41
4e6dc47ee8af02b9446991be0c76137b6516698c1816bd84eedc2c032a2e2599
7e897e67841e555eb69bbe59b9c7364ab87f34ebf0285f280de2402a7dc0e1ad
bb7296c6fa28cd0d40dddc60bb84c7bf05db18634adfbc11ec4752945c5c590b
2fd507eac4ee7227d54ee4e948c3c95a54d3bfd7e5b9bd364086f433ff7370f3Trust 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 963199 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 5305b6fcc4d720602b57dd57074316ca396883de54a4e6422480ff476e5e1fa2; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 5305b6fcc4d720602b57dd57074316ca396883de54a4e6422480ff476e5e1fa2, and the block's
timestamp proves the page looked this way at or before that time.