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
bd95ec946b9786f34472892968670b0fa2d926c9aac65f54792fe28fdde6ace4
4cd81a5d5f77ced16303b70885eaa10b819a43423a26980f1c4546a716a5f5aa
76be4140be3818ccb6b5eb42186e85114adbba6a457854199f0c900ff7346b24
279c7e77cbb7d15ea4c431d4535c3f4649a110146b2695daca2113258d6712d6
a8d38a3dd35b11146a4d8f7c004183b66aa4f0a2fb42b4f87d06074086bd55a5
2a0fcac94d1a605f25e916275652670b97ee8ad687d7d04c3f5aae9c8000b894
c0b2f3accf5c8be63d689e3453e1bddefe13aa3732e37765bc39dea64f10e31e
37c9a60aee6316cfee1a54a22acb833edc072bea0a089ab1a4613e391c04f28c
4834932dce51109dc5de8390ef7d8acb27f34a398eb236a0046a2d20bb9bbd1e
a7896434f0cc062729bde40cfe3b1f9b359523be6ee0d7b0d425d7a688aeb6f6
b5042c161e3073901268acae5b9fdafc15becbce29bd16bb1c61725d7e3d3efe
22a4cbcd3f1b9b27556180ea25abfbcb71a362d8cf7c1abc58487da6ce90e46c
f7b9f74de86f5fb5873181d7db59f76740887c04d4ea9c86537477f7be782304Trust 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 967392 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 1933ccdcc69cb71f4dff82dac116617480ab8ef0778bcd9e9c9c4bdd5dd89638; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 1933ccdcc69cb71f4dff82dac116617480ab8ef0778bcd9e9c9c4bdd5dd89638, and the block's
timestamp proves the page looked this way at or before that time.