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
737ad3ae717b526a670f4dcf0634b9054a21b73c3b68a56fa1923fa4e0067507
16cf665d737e2059b794991ec07776065a307773f7b7db1319f400d36a9b6bf8
0f802796353530c230ac5effe933f832b66daf6b21f0305abde07d558478527c
fbdf4b47159b1394bab9eba5b81d5632805999cd24a2b619ae89e9c80cbb6385
58396033b05d2e0b4c5a29d270e46b45048cd869974ebc03f5ad506684a0863a
2473cde70f9926e4d8167bbd52959e146f3425121aed9eaaf3fa53b00dd60b02
fbad931a547dcf96ba38591e95f2bc25c0159cc5137328faf8434537ae0dabce
8c1f154636bd0ed6859c41109f41bd051e16336c512b45a2e0016d4afc9fba52
2bdbf0f7d73e7f6b89a10c0d520b62fceb13426a4e769970f7ac00bf7a1d6e89
e01c555b7a090097264c178ccdaa0b8bd28bd777b0f445756f141e8ce713ec48
6a48f557d3c80ad1084ed406e6288310f633a9261c96dafa9dad8cb1aab91f44
6c618bca8416178379bc13e67a2dcb8db6eb6d1c43b4c7f0aabd22d656edafd4
c91b3b8177480efa15857eda3322ceec555f85407fd4b25ef0ec14a2646cfba0
da53a9c52eae97cb1f98210cdaf2821ee68a1e8d6138e7b6ade1a867dcde2485
b46514acd6826126d6fd788f44ceb3368bc1a301f3325ae2d350a0d402caa067
11d171091b68a8045484b21bbe24d1bbaa4056d2ac1aa919e6d34c681344c107Trust 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 965995 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 1d46cd4530b437dadf87841effbd8b7846d3cdf8cc8cad052a63c2914910b7ce; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 1d46cd4530b437dadf87841effbd8b7846d3cdf8cc8cad052a63c2914910b7ce, and the block's
timestamp proves the page looked this way at or before that time.