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
a34be62816c9777ca236133db7f4be61e19f63a63507ce9b538df3ad47cdabc0
a385fc491537555da796a2f9aecb50850fc0da37d348cf52f719cce2972149bd
048e7552638679872f17f2cd3de69c9f9c2422e4a456bef36fd00cbcd8951f78
bec01fd23fde92d839174cfbc377e95ba96d3b5b23290803fc610814a313d9d1
bb28e76cb0542a9cd9441a05278e0982fb9b5ba1729afd70d10bd58b657f2be4
e2cf8b9536a40945cb92e8b0277669b1437cd6dcded097e0c07ca3b0a7e3bb43
2c7f2411729c21d21527e3bc600d2925556f88df6417edd6fa6e1af997b6a586
d876d6c13d61ff7cc4adb9e0cb4fb0c6949718746340f9bbead7009a63a497a5
c10d7d976b214bf8ce43f9072dd2589e6aa1aff2c7eb9cc823841fb03ab00d8b
ac2eed893d3d6445aa48722924f9b1ac6b5ba8a196a66aa8f75764bb2857f249
7926a9152d75f1fd99b364f8d74e87650d48a34d2416f67be70e14ca0a4da3d3
34dcb1a402311815842b33069606cd985112dd2413e6b3139c168bec5e14f5dd
463023df8059fcae136202f026944d3979ff0697425f7ccc7c1798af80d26b27
de7af68ff188ce20a3725ee34d50a26582423b2589de4f0b5383728eccd701d7
01f8eabc60c9e6d0a7c4fa0acb149c9cd3cd9cf7569fe4a8ab0df07312273978
87aa01e8ecbb2d8df2a0deb8c8eef5cf4bdb94c8a0f45ceac70b1af1112a8b0bTrust 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 962900 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 499b144e57c071ba6e1d0a8b32111b314e14c56dbbb654ef0fc2c9d3410c693d; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 499b144e57c071ba6e1d0a8b32111b314e14c56dbbb654ef0fc2c9d3410c693d, and the block's
timestamp proves the page looked this way at or before that time.