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
0de44dc1a54b356522eca99dcc0b2f73b72338ef020051156c576dffc68ce14a
7f81ddbff268265ae1b7caa2ef9feefd23310e74716b0c041ee21f9dc970b331
6b3202c94682b96912324ddd9de9b808e70ba90cd968ffe98314f0c410c55ca9
5131beabd05b1b2ec39ba93141be9583bfb0df2311480f5951f3fa1e6795b4ab
3db06f1e41b723b8b9eceef2d348d4a5593eb96fe2253923bb8e52b8f48364c5
2ede829b2bf44a2bc22d0b73c02fad13006b37a03c3be5f3ba48ea3e4a0dd880
c52e2d7f766396dea00dee3eb8b77622574af8bbd215166d7ff13c4d32e0e42c
100a83bf777b0b8f672c0dd1ba03f875c69ae023ecdf99a7ceaf1d72e7e71cd3
1270eb94fcdea5059c3d6f56cf9bb9a21cb1428b68d39e58b6d991cf034876b4
1daf101705ee0a76f4c511b4cd2e7514dc8d50ca149fc8c2697a1917627a00c4
1870fc078d89eded0f1120bc3bd247d2ebf3ec51bfd518e1a5d07e4124ad9e34
62f50b179b888be65a343ea45556291c68f251fc53f9bd2f1ee05726ed228961Trust 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 967898 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 ee1c8429fad1c4fa1deef1321b1664605e7fe1c2d0a5fc25b050a29286dd798f; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / ee1c8429fad1c4fa1deef1321b1664605e7fe1c2d0a5fc25b050a29286dd798f, and the block's
timestamp proves the page looked this way at or before that time.