Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
2216eacf5b22bbe9da893aac0ae47fd73126308ba0781f7e88d27a3acc54b7c3
e537a172135bf572a5d1df70470df40258042b4aebde265246be3e356e2272e8
961bebdce6c29c90224e4390682f56494dfa3886001fbf763fc16a24aab7f933
348584934c3ea879e57ddf863ccc739157806d0568c4fdd0c2e8543e83c43d72
efbadca71701e5201982a55ee5a0235c48e593f5c1890bcec556150155724236
d2dde85c2686d4e0ff9142d557d7cd747ac77091bcc56dcf6a0615243d76958b
68a22a34911d572dd24668cc3377cf1946c304a6372127fd287f54347be6783a
ff9faccf6656cd95d63639332dc74a83dcc7838e831912484b3b827ff430581c
67acce222ffa427d43f73ef352a1d29d1e140252a467038cbf586ee586ccfebd
a5d30a1e532240637d4a2c8f1a838e0f5c1e8b47e8261e533789d8b8ceb88593
9e3ef6a3985c83eda84015ebf3f4b8b101baff336c748157ce4795be06de002c
7e4d31b28a7004288fb976e80f0381b986439bf83cbf877e46ba0178bad2f1ad
1a51995b7036ac14342af4687d9d394eb5195b519edbd4a92645d6acb74a5e7d
565317c47445a132824fc2ce1a9963b4571e4b0c6bab328bdb91219c6fd585a3
f814c9d3bb2169af6a793ee6301e177524cc1ec1e30b58d7b194adbb64d39d60
90b8e8f81b3a2f6f3c766cd8170ad35e6c029049fcbcdf42f8bb02f019fbc1d0
0e975da0e80574bea01062cf3f1ae54264d0105ce1603f20b2d8237ba66039cd
09d5d9afb5296d62519bc105682c35cbcfe721fada7aaa3b4b2521b4d4976387
d6d9f27765b680742d3670f6e0091b121612b612a3433abd5e1c6a0b360db6efTrust 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 965732 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 8e355e2b79dec84bce3f5322f496957b8399c32d38e53c330f28adf0a9e3c99e; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 8e355e2b79dec84bce3f5322f496957b8399c32d38e53c330f28adf0a9e3c99e, and the block's
timestamp proves the page looked this way at or before that time.