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
1e65dda4bb2fbbecb59fbbcbf44afac36b5a50dd8ef508bf00c43d1f5a82d4bc
4c85d22b280dc563fd85a093b37b0cab999db1d7ab7bdaa7e3955f539e4381a4
175ae3cc0c49592b06127c70d4050fc397ae2e7fe72eddfe52d26bd6f4e0cbcc
de2a41b5e8705bc9670de5f8ca6c05815e5a6dca4b8b0f0a0dfe089fd4beb5b3
acca7f02579456c6481cb11f5be10977d372c99429c5b95b9d65df4692f2b159
2fabd731d923583fdfc2c89d112648de9db3ea20768511b9b563c70366f04e42
df5bc0732f8693c390f376061c5b54e301b831324cd08b0067a14a3fd223d633
395caf75f81f99c0d4328df4c367bad11e65bad56d56d6998fd5d96ea2823c98
8182c855964c56ce2b40a8cb653d3dec89fd35b1763e8d0fea52e70fce034fce
cb072f7488a4f531efc72d72f01024ccac5dff9388176da1c68465839691fcd5
9bac4547a70b733a8c658502d5b48c8c1e95a2a54cc93a5ebec4d6c1dd157444Trust 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 970120 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 4f107875ca5603b2ff9de5c7fbd2fc57adb977850ae2ec65ae53dd1636b92895; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 4f107875ca5603b2ff9de5c7fbd2fc57adb977850ae2ec65ae53dd1636b92895, and the block's
timestamp proves the page looked this way at or before that time.