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
a1e49fe6578cf55468068cddf557be98600b4dcb2f91d74bbcd73747f4191057
52a02524d5a19c0e33b4cb8409956c3c2f20e436e56d028f2e2c3a13e6126ad7
2d3431cffbe08f1619a1199b087418eaec6c1a81e18652ba8af1000d0aeb2722
89d3b6d2fab35d5368c5df557df04e23fbd85447519ec8dce5b904eb30364ec0
b1d9b72c93bc29910500eaa0bf92b0d22dd0a22fa125e858bb51e549e7826d0e
8e7f7a8e4e07bc24f8d60bb77a4be4a619519c59bfee48b358437904406fc9fb
2f186a36a7fa10531d7c4767a1e8866cc2b12377d49aa07f0eca787d8919f932
e5615e2ce1b95a00d70d7dd847b5a3a316a69aec08a3a7c4e74662597091ef0a
f58faae6cbc5bf60c79624f76e016c5369653ab8653328024eaf7f4ae9d57a71
da584fdc0df1eb9c9427306d493b0ae34e8b8fbc8e1e286c244f866159e20ce3
5d4c0a8e59b3cdf2cc42c86d3db30b6256bbb48077dd322375e53367f2854fac
a94a26e70276723d1b9fd9a641187a790819d801c9509688e48cf9d515348188
f79cbf67ddb0a289f7e153afc01cc312e845d7eab4ebd8659ec53726b76f6640
bf472df82711aecb315ce4c98cc3c8c18fb3a0c6235c446f1d1f780dd3db2854
5699395498af4c813079911466a91da6d8972a339b6726aaa6eba4e3fc7341d9
42fabfd835f5d03a9ca0c2ac37310df1c079d42aae0ce39cfe274cef0f067141Trust 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 968219 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 7c51a191312bc3e32c23f562d84de41e77c977840692cd79c083a9d2ff140fa7; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 7c51a191312bc3e32c23f562d84de41e77c977840692cd79c083a9d2ff140fa7, and the block's
timestamp proves the page looked this way at or before that time.