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
0ea2e8a99bc6c234231fcb5f388bb6e1e77ac7bb9693e2f36002d9aa67347c22
a4c4f2d901e7d2608fd60977081a54265e607177d7922ca7b7cc2bf0ccab11f1
a2e70593763a6ae1a0457afd590e49a889fde9ee564d5f73695482d2d2288cb9
db2f0312e3dc5e04cfbef5df9a475be91ccac0d4221fa91cffd97f9971e4cb7f
d565b5227ade3fc90d2f7dafd23f276efd98c38e2709dbab46f4474e06fc84e7
cca610129a2351b835de237837d747e0a8a97cfd4630ec1d46d8b6fcb5e87a98
550207d283af1cfd9c19c9a2603faef85b3746793c4f82378b4d0687070cc006
fa25fd18395ea0434fbcf933ed77c96c87d456440fd4a8459a253361e88aecbb
95ad96b27d5c24987fe43b0da106964bf3db6ff5a3731c8b622ae356b041efab
b1b135847a1af5258c2aa71a6438f09d8060eecdbd3f6a86e01fa3441b9d9f7a
7eccaba60e50a3e88d150cc74a1bdeb7ee2a4756dae238ef28ce38f8dbe19288
9cd868cfb84bb6b560c9c73fe78a8277746024fff461827b020ec59310a36eb2Trust 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 971549 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 af8317446ebd91846e77a3b8a03e440feee3733ee20bd4d782f0dfd3c77e1722; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / af8317446ebd91846e77a3b8a03e440feee3733ee20bd4d782f0dfd3c77e1722, and the block's
timestamp proves the page looked this way at or before that time.