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
5f4544ef0e38e847f53e3162761f1d7e638a1b7845f381b9c1b2fb2158e91694
3473b9de348aa78d5f6fd2aa76f4154b66c2b375e2ec72c95cc2d42156bb09c4
1c81bf3e76af3c609a3cc3152d36e92bb2d440bc871ae07c2d9ad2d68f016896
eba32ea67593918ca9960624d813ea6eb8f806ba1e979be8b9f581a31d189ccc
23657dca179d0767b2189672a33279a64d00414f2d411f3b4e7e82067a4002c5
d9c84512ee276237f5087603eb3ffaa6d7f5a2cfe6944ca6b8d2a4f87954aa60
d3b80bfa7cd10637d11b237a2797d5bd169ae349f68246a29209d49806808bba
a615c1b34037b7a1273d75a827c0b1ab5dae8595e055ef768940e88a198e068b
b2be36aac4c58bb56e79dcb2035c1c220540831b9faef912af6d9f0914f36315
c15767867483ab3903c678848896fa812c50577b9a70f4e5fb455ae76df28ede
3713d9ab3a032756ed38692ddf13c0d902d6cfacfe8d7a522768506020bcfa81Trust 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 962651 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 b7dc44990c89573d5f85674e36c56275bbe64e0e6d8f8555ea817828f206578a; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b7dc44990c89573d5f85674e36c56275bbe64e0e6d8f8555ea817828f206578a, and the block's
timestamp proves the page looked this way at or before that time.