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
4f43a53b7e6bb918a453ae07c9cdc1222a23f23d552465eadd000f5eeeaeb383
719e853e352d659fb8dde5e8a557cd4e1542d8886526660ba8b7b393cc6c22a4
5495f709ca002705d70d9f2a61529d113fdf80b5419c8c6f01743489901a2e33
606777b66084fb67db4a58928c0ed288524560f463993983c7bfcc5e211bfc0a
0337b8f728300b01e01bd3018ff08c89ac1cf931917b3fbefc63b2ebf6660ebd
80e37d1fc828c5203d8ad9880fbda0e675d91c25c3be1a88e84a83483a8fddee
581818487148453f5649071ec8500a433351eccbdbf569a4e5ca7629387e3acf
c8a37fa4cd5e2dc33154d8a248c2fc95fcff5c867bfd84cb96a9d1b7c79e8c84
19a6e07b39c3872f12aae551c10a01bc851f32ef3e9423d816ce964fafa913e3
639bd04ac6b6a871e3172903548661070444b44e0ffe1da7fa6da0530d36bfb6
a11d895f0cfaa25a99f581719317492472a99f754e41be6ec7a60b317ce79131Trust 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 973711 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 d26a5634526dd247028096e8757b0859ad4955f12145f812ffaa4db0d844840a; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / d26a5634526dd247028096e8757b0859ad4955f12145f812ffaa4db0d844840a, and the block's
timestamp proves the page looked this way at or before that time.