Web-page notarized
A tamper-evident timestamp of a page's content. Pay-per-call — 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
6a2ce419f953eafec98b37f0962d2c6445eb144c619d97bc36410b526a7135f6
f0f90a817961e2d1656743bfeed80f0a3ee9352c73932e85673efa06144ed335
faa9399e805a4e9526f2c1a5b0b7918fabf66bf545ad450376fcf8118a5c93f4
69a858e783c25d02024db9d505d2e974a0d51528fea40cb4c08abcc69599e29e
dc50bc0c61759bcd8d9bf49106726370c8a041d9794b6b2f892cf6d8594da89e
cc42c286e1e04e34f72246154508813afa0b30b5672364472f5bb1eb4a1df923
d5bcdb4629a61c5127b255b1e29457ffe5de42cc83a74ec0fa6afcc79db48f46
735d01e1ea26b6b03a72812b8a8377b4ba5b0c1260a24fa1c2255247b0623951
274d9911089a0931a5190ad0c5bc0a574753173980b0e7f7ca72e2b9b7b3d8ee
23dc6cae31bdbc567cb2ab7d51a34390cc9bceb3218c4fb6fffc27b17c507ac8
ca40355e4b3dcad6456bc1bc5387a165c927253c730cd6ddbc44eb9f9ec3b6aa
dcbbfa958c2468f221dc14945a04e3f2913c1ad1f276684b6c67edaf507c78bd
f4ead9faa16ae9ed89a4ceba14c612665f18569750dd147aa019f6b01571ecd6
c3289b0fc578eac365b901c511c9bc81c4c04f1a921b3edb430d3e6721e9ab02Trust 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 971653 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 3f0fd0b5def072a646772cb018cf8b9c36cd47cdde1bd460b4ac28bb8aa5892b; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 3f0fd0b5def072a646772cb018cf8b9c36cd47cdde1bd460b4ac28bb8aa5892b, and the block's
timestamp proves the page looked this way at or before that time.