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
7f0ebf4c7bbea2b486c9a9b01ff132464d9588d94d4ba023c86dc6809d0cbc23
30c21b696a133af46c0b47449abe125fe462cd21101904a02ce124e5ba7988fc
466f25cbf12cef7b97c9cd6ac66aadac508b8d227effc92ad78a3198237d5165
905502aa27f9ec9fa71dce49b279ae67f729d87bb1d33a93310aa8a3d744482e
a88d54dc5b19eed325b5927dfb2c0123af847dc7d6ea20fb4e72b7a333d534b9
2664353788c1657cc0805307e475411397784f52c8210fe7a2fc4d2add452c3b
5e200e09873bb6908a13e5a9e4ac80966198ce48bf3886be2a460e5df0339524
b751bef0e3149d80bf54ac4c3e83eb329612d25876379d57df0c6124cdae81d7
7be74a04e85e985d2cf56fbafa11745f123035819b3129087c0d7c898ff4ca4f
1615cfb901cd184b8ad6ba774451b3ff046e13c4b7884fe313b46f45926ede69
7d61373ded9429c548512014c5f7a60066bd652ffedd514a1d19a415143753ea
7cd77a36b544b6652538db5ef6d4c8ab466cc52e3c10bc9f91a1625512cb194bTrust 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 970638 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 83072616b00e025701c5ad3f1c7675ce5c30a079b8e82ac918229b64321987a9; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 83072616b00e025701c5ad3f1c7675ce5c30a079b8e82ac918229b64321987a9, and the block's
timestamp proves the page looked this way at or before that time.