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
1ee15b5be3d27887174dc46cf4b5c4fca44a35813b093f2ad70bbe90d497b25d
ef202fefa3ef08c5e8ba91b03f69d87a217c3107a23ea2bc3f80e1e2cbafc983
a413269ffb20b323a3d308310723018a9db6a7874cab548fe1fd6d25e78e44b6
0eb078272b7075dc7ede260893796ece59269ffdfe411b1d2a8ffd737c78de06
970d36ed6a336e09a0394b939aa08869cb8c203a9bdd1c3169e00833691abec4
09c54ee94fffbcc62dae301ce01490ec89966969584759abbe6ef36a8b29c188
d3767579c81cc26ebfd71785c7b0ae40a5a8de92697b568b3efc58fd67ece45a
15bc546712d8abaa47bb139ab2e239019cae56ef4e8932a5a9f040d13a7d941f
60962eaefc8980c6c8b9ed17c97310cd8f220165065698a5276cabdc2b08bc31
48a763f939f0098a301594a389d1410cd96a51791db4393dc8a3d54bad2a86eb
48daf0872a190a129a8d4247f4e5f0dca0c9d1511e95d97558348c0f6f1873a4
7a5849f7ac34bf14e51dfca4671620cc85a521743d27f2e3a4c982ae031ef7a0
048bf41479821a4037e871debb5cd03241da96091af09ab7fa78de0e2ad43ff0
93a3737b69d83ddbeee582eb968fb48d4edeceb69a0c3a2c66c9bcc2d41acefc
53372003c5c4e774c3e7f07398c635f60fa1c65480d2b1c9f015a37409bdbbe4
7a19d11084a9fb006e606134a0b25280fde070413cf7aa348cba829fda25abbf
6fa59a529e69ea468529e04cfd4c493c48971b375ef611ff7fe484dcba49b2f8
b4e211017573d2f72e83ac757039d4da4151962a43bc8e4600da74616e9282c4
dae5365495f87dd68eea74b480c449e07c106e9d9593fbb2a3e7afa1599ac0a2Trust 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 968043 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 115eb74cb57a019884f16d87a2bc4d13601948e7917519bed7654940df021b5e; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 115eb74cb57a019884f16d87a2bc4d13601948e7917519bed7654940df021b5e, and the block's
timestamp proves the page looked this way at or before that time.