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
4e9e7dbaa91566f827575d9dfdc303a5bd6afd54f20acef0268a6595c9c0324a
26256d2d1905265373302967769502480a11a58e7f953904b4a7aa9d5170583c
a644484e0c905e74d274da09d58237f87b40066523b342a0cd0ab1199ac0e61a
4e70251d5863380abe8d0babb3267af787cf405278570af5dd05ca2c463cc07a
1cc8fb3a55d7424e1852cea924650d5f9490aff28ed03ac492eaefbb040f355a
6bb0ec555ed94b08e3ba78c46310dd1b9d210bc11cff9aa3f5c05dad285fbad7
0ac201cbef210251b682b64082e93af4d10fe1a16278dbfc8539389757be17d1
2181ebec2a83fa21583827cf72c76e65793d03cde3dbb32959a3f55c6b41c585
cb5b777bbd53927e9e34d9df4ef0ece40d284f4be2c8688787774bbb3622c9b1
9adb16969b64326755d76894105c2ea316e164118c3ce7fe3299f653222d87cd
13fa5c42dc2e0b7cd976e0e1187e2cc127c1d8e33737e2325e2e47d7a37d7e13
f665de52195160fe50b028031fcc750f936f35dd52f897d41e4615beeee2285e
e1663dec8b04c68fd080f71349535eb6b0e92f1a489c82136099500fd54d8678
4d9b6a43c025ec866c90849267b7993bd2aecc66c7f77831f6ce1f8eaedecd12
1aa3648402f3cce88aaae5ad1702e93f71ebf2e6e4f4ba5ef69bc5a97b7b62eaTrust 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 965279 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 48f494b517a7ae7b45c0b408c789cf55aaa03497ecbdd3e48b3a1c8e0e7391aa; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 48f494b517a7ae7b45c0b408c789cf55aaa03497ecbdd3e48b3a1c8e0e7391aa, and the block's
timestamp proves the page looked this way at or before that time.