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
27d2e2fc8d8453e411a77e320d65b07fd25f415643fb9507c527be78048a7031
26bb56c748d46b1e40b0cc711693bc6006b1ebd54c3f25402bcf1a42472b2daa
2a7b486479313dcd11fe9239c3011be9203b28bc90e070a273b89ea6cdb80406
65ac1322b5a92ee7da0154beab9b9448e83d86ab6d23cfef230fec3e3a8adc92
ebffb402d3bd2cfd47f2ab62bb96ed0da7c1475539b7fa3dfceffbcbc6109192
1e5e2898ff3c8bba7c02b8d043f7987766678e4c944a71cddfc4926a6e2a0f3f
908481b045fae81ee4168778d133449fe529f85a342de33b0b04cd50a38e8094
10954b1a69137a1ed5ff29f6587f983094ee312cf186ee731d2aacc549c19f54
6c0944770ce6452136bf82f9a7b36287b9e4c802f7e0f88f59222d139ff3fc1b
de6fe92ccc1cd0795d939bbb0b5f3ed9786bc683af5e03fa3d1e5ca39486861d
3d6bdd7f9ba8cc49fcbdd4dac3ef5ba84be3dbf9ceaac4621db81236be91e804
6646bb822d038e561e1457308346c9a57af9020c7490cbb8d6c508d60f3456cf
24034d1b3b878121008507dd575f6b1cdea8568c87e13c567feafcab9c8b8919
3d3a2c84ee23e21f4f2efffb8e933864e86a5351a85063e6c13bca974c1849ff
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 7522244754ebdc8eaf59227efc6d8b6ce82956b6d83d44a3492150c991f90c8e; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 7522244754ebdc8eaf59227efc6d8b6ce82956b6d83d44a3492150c991f90c8e, and the block's
timestamp proves the page looked this way at or before that time.