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
a5d303e74dda9d7eb71727f6b5ffb6250a2fc06100f7c14e37bdee4a190eaa5b
24d64a64a3ce3917731c5c061e38d5302e0753420f1fdd5857451e1e1ac27db2
97147f22cd1da2e1e1f9e0ae884cf9ed48e39c78eff7fe95160ad00203d0f9b5
3c6c37e93715e41ce415d927bf262ea169af811dd64cd552736cfa7a073682fc
d65b3dba8942d158ff3f93a0638024b2c4b156286ee1227d25646abf9c9d0cb8
612c4f14e51bce0d046daf64c8fb50e688a7b73bf2d9858cb13790de94449c27
d98e03f3c26729d02e2076ec6afe92fb5865dd996dfa57f4f1963b2ebff04954
29f2f98023b01b4f248e0723ded34b7f9accfb6e4c2e5e7654e6e3eb3cd2c2e3
55af921ec8cedcb0729cb7b4bbdd1d5c038b0c10de76c6f6c53f5f5a4fa19a13
399794414543921f8d466c836d6a4f7ac42ff3127b08c98478fd03c0fb7149ea
b87b8fd38f6e3043c8315ca0868d9b03e3abcef2f77677b87361f45435de6b1c
850de4610c34b1c92eb1e83bfa332bf34ed24e65e1ad0e14310d77992b9b62ca
b304b2d788c34446dc28b62a5c34dab9480efc284acda77bfc55e453185817f0
2f633fbe1922468a4d5afe943fd659baa3a20ec62ffa9efcfec15cd6beee1f85
e1bfa3113a71e267873b039e0227073f314ab31d09a02cc7514c6f0d2c6398bd
4d4b5ff0c7a9f6680cd2386ff4b3855abdb332df5dd976766fbefb67ce3aebb6Trust 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 968193 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 c326278759f57a3a3c5de62cab9f68edee34c00583e73a75615af2ef77cafe4a; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / c326278759f57a3a3c5de62cab9f68edee34c00583e73a75615af2ef77cafe4a, and the block's
timestamp proves the page looked this way at or before that time.