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
8e152326e44df28051c55976d32c9824220dfefe0364eef30eef951f5fe45431
904f303a127f208cc2efdf3c909315abb18ea9e5991943623813c6848b2ae095
ddc5b90203fdec03729e379b92a8999e77d06fab07d30405c347eb25cd98aa04
f0054691ad24e48ed1f678125c4e30e34db9515fec18899e0852d4b144936e55
374cd8977771c84fb944be66d11ec0e9d84a5988953186eadebccdbacfb0be80
92674710e5a7148707f6dd53aab7ec83388c64a9498d297ba65af6dd8cb59ed1
faacdf25d7e78b738e3d3fbb365bbbbb43c2bbd713751af3d3222a432311cd8e
5290c4948664b839b346d3a439f813ee0c53c08398f3f4917ade87a5da0d0c34
e14f363e9cdf979586ae9d92cd870ecff0931f1d5141a6ac25117a756cffc9b5
462f980246288860c94da63a1b15d007bbf95c48c0953b64e602f710c3fc9bde
97958c5539680d120354670994afb24011ee46cd70bb644cc0ffa4c5dde663af
6cf879db4ae1721093fd20f003956c848eabe65143e52f7f5805babdae3bda86Trust 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 967175 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 5c04389ee3e9fb1e8a98324c0036d12be78300ca649f1dfb2eeaae80470a5900; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 5c04389ee3e9fb1e8a98324c0036d12be78300ca649f1dfb2eeaae80470a5900, and the block's
timestamp proves the page looked this way at or before that time.