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
6a68110ea92304f03731d32fe16c28ba2a003b02da66baa4f4c735503adf8401
125c2cc04199d2d95e48576b73325886986a760d3a402ecb382448face0a83a9
780034014b9c9aa86621f9bd652344d096277c168a23447133cc6a7aa75b2ad3
c56311a046a06eff338f73385cd0cda8f263030ee708e06b6881f38dd5b06113
514606c4a8f106aa414be2f76cca282c9d6a21264b826ee752e6208aa9161324
592d21e15ade44cef4910650d8480a4e26808326011f7e312136d11edb514c9c
70d825318b87c1b574f19d10c49002d49022b2c78f0a81afbdbab7f3784496ec
5cbade50473e4f4859a808f1296e9c17b9fa800b5a3419520884a1556c2ff2d4
9e1f1586982a0bf78742c2bc528cf957712325022b7d12e7f8c7a59236f69376
4ebfcf1ddc9486ad984b8d5832bdbfeec8e9fb61f5afd6cfc59032c4e32c95b2Trust 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 965962 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).
Save both. The manifest's SHA-256 is the anchored id, and it binds the HTML hash — 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 808629b5a128e305a17816eae44c2514f752ff34e3bed1287902038686d17473; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 808629b5a128e305a17816eae44c2514f752ff34e3bed1287902038686d17473, and the block's
timestamp proves the page looked this way at or before that time.