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
b18247ec9fe0eb70c0a2e7c81bf673ed94c588f8e3ea4d1cf71f8ab5981933f9
74fd767810bff7ab58b1b62c3ba848c3cfe397ee3eb481404eed860a207a6b77
14eb25cb59ccabe892a048bb2430cfee0c15ca38309c1744ae0eead29815be4d
65df7b1e590f2f36988c31417d362902f8cc7c600ccc1ac79659152351d25d82
89a097f297ba36a6841125c9097d447fc64f5f53a6cbaad1e78f7c4ab2343dba
448bfed71d5b3c0e7afffb47397e3edbb4beddfc6753b19d037f64d80c342c2d
0b57bbcbc1d62d4a148f3a914b904755532e049378d148fbf2bdb16a02fa4afe
2a7ae85a1fea15e0209ddc6f0506c606e5d49e522425cbd56ea1470396ca2320
e14a8f7443d88c85761082229ad39a9045c0d0e6bdb2ae959cee8cc41f897d68
f1770ab8f7a9ce192c4c54a83e821f6e36e858dfe3ea9257444a49ba5f6fff82Trust 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 972680 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 c10f03bdd4a3282514f1388acd01ad910e34f17389922d80938bd37937155232; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / c10f03bdd4a3282514f1388acd01ad910e34f17389922d80938bd37937155232, and the block's
timestamp proves the page looked this way at or before that time.