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
8aad84fe5bd3e3cb3e5f82412a6042429a16fddc9a1c1024b84a35cbb6884c2a
6fdc51ab6b32aa0a38747a91af50fa4b511b0373bc98829121b2f89bbd08b349
75ca7726a6e01ef409309fe49624d7600133721668b740f7ae90358d3df3e156
9df584a0f041b834964619441cd62261002e10dea542e5b8635e6a1cdf1aab33
1d219fed87dc4cc7b383fd7935064dcadf112d84a53ac15fbbaefeeecea664cb
e0bef6a4cb02fd32ef35c5ab3392bf6fffb20c742ce574a9dfb779d9206a2986
2b0352c4334015dbb75d98d003cd7c20b126ff8b5cfdbe09076d0055bd9d9f68
92f29ae184d43f5fafe872f5cd612406d51982c1b6073bae55f23822e3b67ee2
150c59c9e4354346791d6c801d0a7c340db0867e0f71a2173e1ddd9265591e14
6fcd4b81008f0a32c73f7f978ce24626edd0d99a10a5faef1d5ed589c600c5b4
226fa12338f41015f9a04c6771b7b2aefd7425a5d5dfdb5193f8eedb28b32498
7e4d31b28a7004288fb976e80f0381b986439bf83cbf877e46ba0178bad2f1ad
1a51995b7036ac14342af4687d9d394eb5195b519edbd4a92645d6acb74a5e7d
565317c47445a132824fc2ce1a9963b4571e4b0c6bab328bdb91219c6fd585a3
f814c9d3bb2169af6a793ee6301e177524cc1ec1e30b58d7b194adbb64d39d60
90b8e8f81b3a2f6f3c766cd8170ad35e6c029049fcbcdf42f8bb02f019fbc1d0
0e975da0e80574bea01062cf3f1ae54264d0105ce1603f20b2d8237ba66039cd
09d5d9afb5296d62519bc105682c35cbcfe721fada7aaa3b4b2521b4d4976387
d6d9f27765b680742d3670f6e0091b121612b612a3433abd5e1c6a0b360db6efTrust 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 965732 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 a3d92b4a873c0cb40893a0d7a93946b58aa14c2afd7ea792918ac0892f5cc544; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a3d92b4a873c0cb40893a0d7a93946b58aa14c2afd7ea792918ac0892f5cc544, and the block's
timestamp proves the page looked this way at or before that time.