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
aabf6fc44d8fde483e3d9132150d29b140d0446a2bd9d2a50366783cb307b903
2ef4073dc3c33d60ac7ca83d0a16104923ecca70ca1853aebecb9e166f2c4f4f
693850f856c8286bbb2cc13593b26c0aa1ad087f6583566ed50dbe957dbb0e7d
d6f5e64ca19361a93d3325df1b21322ebc320321bd1d51d730ddabeadb5b8350
57a8bf50332faddf606b9674c87e2676b96c41aa4eebd313beb1bbffb96909fa
da7bbd407bb5b743430e1e7b12364abfbe69da8dc26eb0a809195d0a8eac35f3
7d23bfe4916ebf3ad38ec58bd82b20ae8b89d492dd56e0bea4d19753242d0e8e
486399961a2af00e832fd59f317f99a9c9fd01fde49c8ba72d9422b4d99d19ac
724b127e1808833abeac23775e0f1b4764411dcb8c20ba66366bc2744f88606a
67faecbe4bb8a7f9c5bbad1ed7fb47f72c642ffb11c1873e323a173962510180
d0f8ab88170a2795798b45e2af57665bc4ac400481f545c86b67e9a660f0c7b6
1ffbe888a8f4be1119911f1e7af72f7638d782b52fc71313bed459b4f1392abf
b924549b58a133c9d2fa206306146be612548b15fa9b16cf81340f8c131793b7
818b84aa64d8de6e3981dd2bdc4bcb80142a0663dfc6e946b71a80f87ed96266
a44f0e91e341e956c2866e2307a645ab0ec66a3f5fa11930b7da5aabf96c2e6c
0f9d6debbd5b4408f8764ef0560f0bdcf002000731ddad37287c62e95607668f
3a446b9129dc63d89146e78d884d34f4be7a472448bdc4282beead8b9a20fa4c
72df84db0f98004d48b2362bfccdfdc92dd8fa5206a1c7ee838656d00a39fb6e
411f750d3757fb2da5bd8d50a62141c99d3c00d64899ddbd1fdb7dd4c3f55edeTrust 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 965016 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 ac51c7965b2ec49958e074e04a32006db3ccd532b1c3ce9741615d6b9aef40d9; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / ac51c7965b2ec49958e074e04a32006db3ccd532b1c3ce9741615d6b9aef40d9, and the block's
timestamp proves the page looked this way at or before that time.