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
483fab6cf4aba193e49d6be17d0dcf007a6a6c955125116ecb1cb78fb9de9f15
7a081d95a1a7d579ea3de054d980c4b7ba075543d6e60c17bd2b92de9502032c
942ae2605ff18f9b03e06f001ad430937b5c306fcf095d8577a258a0ff4f56c8
95c75981fbbc56978b23d761c05261e6fd6ec9e76935d789bc61a081043ecefd
e4b4736712ee9120bb5ecd7bb82e7b9c43c64d88ce45aeeff851a7ad670cdc26
1444242e1d99c2544e780276a926458225a117a02bc3292039d8fcf1794d9dac
11b16a0c04ab13e9192e20263288faa41b61a5d12624f06c2b4c48cb48da3b86
7ba7c2e0275db089aadbc738e61b98a75656efd605905733a50e0fc66316c362
d6823200bc10b0cc477f799ff93ca4bd590badeeba8add1bac766992e5e731aa
b57e4719502decb4cd593e11787f00c1f403c5eb8d4117d4a76c3c0ca4db05f6
226fa12338f41015f9a04c6771b7b2aefd7425a5d5dfdb5193f8eedb28b32498
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 11bb6260f1ce48aac3d551fadd41b86448e0396d0ead35bc3e35eaa06bdb508f; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 11bb6260f1ce48aac3d551fadd41b86448e0396d0ead35bc3e35eaa06bdb508f, and the block's
timestamp proves the page looked this way at or before that time.