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
971811e34c8882d30155d1a09a2ce930f6d89cf9b02fc4e171c7dffa44699279
dc90a22e7c6e40e4b73ff63d909db15e9fff0ec055166289ab6600e8fd60a9d9
e80a4aaf9b38f7dad0ff81346d322c24c4c8061c3315d57d430418c8118ff6ba
90993f95f27af399d70f1342bd7fd9870520a53da3f714e65c546ca198571ede
e79e5bee55b64ce1379f10ada6a8033ab24cb91604120abfc5b0c2a03ddb2e38
aa84fc04cf516b44c1e42ea70fee53b75947004d83d4b87a5a3e911ce1f77e34
021b4c20312658d64a5e0e8a6391673571a93c02822d410be51c2428cd0c739b
0770b7248ed0d1e1fd1efc5d4d9e2edc214b26fcd9475b21a072097c9cd6c30a
432a5225291c1d5c94d92a0d9b076cb4f2da0a7bee1f14277d9631ea5c1dfb82
c7140d48787a28e2a4c250de07c2fd950d30e58a32277246949455ecddfd80fd
530bcc7781904e22330e3b8f664c12dbecf444b0ea9393b1277fdcc5ebdef57f
038dafd11c9770dcdb986358acda5cd4d91758cddff34e6725d0d8ece367b68f
b55e34ce37cadd2c4c32c813c1b40adbb18097bec73175726046265c421a0fec
a0bc99ad5f611e04de09e141061988e374aa63d6a2ffccd5fb9c89298bde90b7
0169917d057a52b5cf7875c9812f837ce089fb9727d52ac4797c09dea9b70518
0ec99cdc0add4c56165fe15884b6a7e0a6c33e7a8c9058b651afa130b039b073
e56c7e1a93c5c4102ad4eacfbaa4cd87003dbd13b0d3f21a7868a18d2cca7e5c
d09319ee848939498ef68c02998a4ae4440155a1a46a80d8058c225ea65c2ad1Trust 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 972415 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 6d62981fbed90cc8ef853e2cf6d2484b9f76eacf0631b0efc34b6f7ee05b4cf3; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 6d62981fbed90cc8ef853e2cf6d2484b9f76eacf0631b0efc34b6f7ee05b4cf3, and the block's
timestamp proves the page looked this way at or before that time.