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
de723b54f033f3f8f8d4d9c6fbf3aa20e38dc8f535dfd0c6ca43918c02a1f20a
633eef92876578e039935127a1f227f322ba31eadaea3f14a66c61435f288e68
c41ff8dc046ad7842bb4be554b1265b1c1ee547d11784437201190de926483b5
b8371c93bfdeb3e3216281717ed7fcbcf155c392b37747c018812a572ae4ab48
c7f96565f37ddfe53234a7f210f389f9fa0e42e0a7384c798696a9066c30b5fa
78e7c25fd991fc75446fadcef2a4f330ff29ed467dfd999f7a47f37608bea1b2
09d296d93a704e56d308e436f44ae163533ec857d9cba11bd1fed786e713def5
a1040147b132c0eab07b06df0490ee960e02ea42eb94ea1f841eb7da557c9473
716f3906eec21579923f4e6dc2d260947051606822a52577bcc876d9706a55f4
14a229629099d3ff0769763e2f45fc66c0aeac68a00c2463470f70bd170df4c0
1703f62b9e2e32cfd6b0a40736bf4ff8c068a386268baf634624b091d416f0e1
04d6f29882b097f67767b134bf3b6f407cf3bb53f95f12bcf3f9a6204e3e1634
847df203022830fecd50b289ed75b9e103b67267c9e422557e38a03e9776e84c
7bd751b7b9eccd5a655bf46d6a3cf118b6be8da368e6f1497c9a1b21303641b3
8518a222ae6dd42a35350739684b0d93633fd0e26540a34c9cac307e9bbd999bTrust 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 965083 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 99b787b0ac7bca781337a6fd0cef30ebc509396a16107b9832f209fdeb66bbf8; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 99b787b0ac7bca781337a6fd0cef30ebc509396a16107b9832f209fdeb66bbf8, and the block's
timestamp proves the page looked this way at or before that time.