Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
43a3a86bf52dcf024935db8c59f53eb44c391b18451caa196ce359cf6389791c
25e0b6d83024af054afa8069dee4dfd30cabd03eef00d6382a87f12ab3be8452
014b3d8f37441921c629f4fba0f38c4f9dca3ffd9ab49f6c84fe3859a85f1285
474de897b3485fa7a197875598d4b3bcc67aeb98112b246bbdeb9f08b25b0098
8b6b15aa042c350cfba33a3dd600204f522ced3f1e9c749d846cb50a9cc0f031
50b6ad795dc593eece11bd8f1ef08cbb4cecbde4dfcc657376136e7a14bc43f9
c705e1eac2a6351f55b6da85f05ffc04dd5c150785e452a800f3fce1b5ae0550
6fcd6d589442c77a72724907248fc7e3922cba56e67ca319499c9de644b9f547
fb79afc3c015cf999d22cb9de7be36a661aff7c2e76179a58ff4fc8419efae71
a57fd56c2df320d0e4f8836b0ed17caffce18744b497229a9ddfcb6fba37d5ea
ad95abed240a15d334012e8b72ead97d34ce25929f462eddfb6d314fe0d37b98
6c5faf26f8a735ed110425d1ea83e494bf05b958056598ee3497db4034a035b8
4a5f819b698594062bf4062e09939e6705e82997708670bdecd95270c314afd7
64295dde51f09811c56e6564e7dd5a26837a9c14299f77c95a92d6980b64d4f1
60cfbd8c703e648d7bd5a0f7d4c5fd6f679f9f7452270440b9fa14cbc6df829a
710cc3fbe3eaa94701d0cd28b4f078b53b37f0d14d6c6c302d62ee1c05105dc7
428240cccf46203b09f06f2d9085d1a4ddd99af2384c97f653f35eb8b8be77ad
e9b301fd744a0914b15bc33b099a8cd193ab9d97c507610c0138c804176fb50cTrust 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 964873 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 e69a47afbe174873e1c39603a339b908bdc3123c7cf6ae7c8edfab9ffad87f02; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / e69a47afbe174873e1c39603a339b908bdc3123c7cf6ae7c8edfab9ffad87f02, and the block's
timestamp proves the page looked this way at or before that time.