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
1495f2fcb906d8be80ff66d1aac70dac5400b76af453f87c83cb82b46b91325f
81559212a6091cec33444d035ad4ac716d067872007df15911498c9f41477f13
1882c594659a22a64bb813411277a23ca2458e2ca1635f631aaf1e968df06440
d545e0e1cb55229ff60368f85c232d1ca5f9567734f8fda9b5a72314538ffab0
734b69433a7c60c87471220bda1adf489e81b0975e43d9be73122c14bac491ed
688481ec82c1695c1d0fff8c42e41911f4c01cde6abce3e47d9d3477f224731e
ee8d4fb45048f76c1bb887f5ab24f6611df3ebc4ae969a352d0173f7f69e376a
6d9eb219f4bebea8dffdbcb937b7ae18ae9e1a13692c85fbd62d4f4995445909
d8dcbf8813cc4635f2df1b324f140d4d57a4e22177b51c04a5294c4af428ceeb
d11d487e5f0c826813edec24ee04dd3a23656600470e7388da79981432e2c5c3
32ed7c259eb756f5df78cc8ac0d9226c77314b8f2dc1c99236da4594d7d049bc
a0e523be9802bb1414a2e7e8430119054a56a0838021ef8b1da6785fdb85cc89
4a5f819b698594062bf4062e09939e6705e82997708670bdecd95270c314afd7
64295dde51f09811c56e6564e7dd5a26837a9c14299f77c95a92d6980b64d4f1
60cfbd8c703e648d7bd5a0f7d4c5fd6f679f9f7452270440b9fa14cbc6df829a
710cc3fbe3eaa94701d0cd28b4f078b53b37f0d14d6c6c302d62ee1c05105dc7
428240cccf46203b09f06f2d9085d1a4ddd99af2384c97f653f35eb8b8be77ad
e9b301fd744a0914b15bc33b099a8cd193ab9d97c507610c0138c804176fb50cTrust 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 964873 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 3259983c23435d91817fbf9e5c0a034d17bd3fb193f91638a297c0d27f12b9ba; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 3259983c23435d91817fbf9e5c0a034d17bd3fb193f91638a297c0d27f12b9ba, and the block's
timestamp proves the page looked this way at or before that time.