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
98da6ebfd90064d2e594013436c7f6ce1a9521cf3c624fb8fd76714ddd4ecc91
be28e70472cbdd633a91104b9e7d64286336a99d22d3347566d71f3ec53e4a44
146ad7b161c8958ec512a4d406e951dd656eb46fdd99b8e908b2ec9ad0d884ca
92841ea9c51a3f0f86a5b3f72caf63abc2e09e4d927503ea7a01f106e7fdc025
ed176d5169c5acf23a79fff9f2978a1b3c724c5328685877bdaf0fcedba776c4
e7840299772da84c03b62eba7dc44d632c534185a608445ac14b6cd65fd03f15
b7fc1c64e617d8879d9dad81bf486c8d4dbb0541ca1d75d6abac137d5caba4e9
cedff7fed9f62a8944e703d967c1180b28fc3503cf290f8384e1b6bf7b1f650a
f24854e42536d18e99781694bdb8b0bb2de9bf91fa8e8848695ac6b71f655d43
24b86c4c83b8a0de80434454397dfd6710af239404097af11960a3b91a6f4b3c
1a979d10d22596b6bb5f4e8c584bb5f9afd77b7193497d3e7d25bd387354686e
b453434098884c0c20431d30b0a0cb64be176e7ea00dc67fded012b0048bbd81
a3cb593136fac906b8e5bdaa1ca0d140c67d029a38e961a2d7432449fdd8cc21
354d4ad82ea3f68e99351886daaee31de47018c7997a538a941f523647f4ba94
362d07c0ee0618f453505799b00b7fed4bde092c41454665f25ace4b3f5df369
2efd78b7497875aa1fb076f758e6f811e3dddee421ab3089bb0c3d59c8b255bc
d75ccd26a397d2be3a50b916be07abb06ada53b43fd45a611cebda429898574a
d6564ca9a67a7f73a867033f405dafad849826cb01a63941e2af1564a2e678e4
756eacdf3ee3aa1d7551ea5208b2dceffb66f01afac12f0772c76b448c1e6acc
a6eaaf0f88fdb7edde432f9fdf3ca4410a874d2bf19cdac78101f824dc68d565Trust 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 967515 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 00566b1f973d08a75111bbbdf2a7f254f72fa9ba10a126b92cadc4d72736b224; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 00566b1f973d08a75111bbbdf2a7f254f72fa9ba10a126b92cadc4d72736b224, and the block's
timestamp proves the page looked this way at or before that time.