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
24ef75f16bff0e013802834ada719a47506b6bc7f5a00e8e46e5dba50d905d9d
e06a9f84761718118bf1b9c606bd09786a190a67f194e94cc47de933d2020f02
87277c0d56e78be00f8e346131893897d548976df2d08c6e92c296c287179344
6da71368824f3d4d5666443de213675ce0377215c16e718b9735cb2570e4a3a9
9eae1df189a8cf02c588812144a06c068bea616c19ddf04ca5bb6901b88266eb
8c7497a07b38b88ec4ec5325e96e3f59359d6a3251808543cfac808142cb6a5e
2e4e6ac0d5e119f0d2cb60d8a96cedff37dae4b0ffec4c659826a3780a09369c
9a6bdc01395f3caaf0a6e548fe7408df07ec548958010d7345b711cc9770b9daTrust 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 966096 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 f9a5630ce5f352b05fe96341f328ca67ad47e866e4d48a6e3038d3318a8457d2; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / f9a5630ce5f352b05fe96341f328ca67ad47e866e4d48a6e3038d3318a8457d2, and the block's
timestamp proves the page looked this way at or before that time.