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
daa47d0aad26bc08a209f2fae184e8ade021650d70ab378971ea4b56bb8755ee
eb2af37ebb5ce7130533ffc99b9c4f838c43f6619a37c5fdc25db24f8065542e
237c7cade8042665d73800c0d171e3f64391af03f0f305b7e7ebaa7d02718074
5f9602d9af2ed3edd9b327bbed39ae6eb1232f224e93e5688069beb2854b5389
f70d9184a723b667d2e43ab272374264fa188a710b41c5990dbaf0157bd0ce02
3f19b7809eb439893d8416741bb2663493ba4e74be11b7d44cab44c135aa946d
353a6a11ce073c89f7cd2b09252f90e1e57fea1e1f5bbd88d4a50f7e3f2f7f2c
d46a321f663b6f676d1e8a8010fa4c3774ca6d33f1502cf003e7b54e6fce7593
3e835493c9d1b61c7193a951854a1e434653ab6b6b3147bb08ba2bf091ca1f87
59d22fd1c06cda4edb3fc31e4a587fe113175f852b85a13d2e71de204edc5ac1
9c2a4f95fc2b0ae4182a3b879856ee9f3fb101e6e35a28a32434ff5d2b2ab9ff
5f300e85fd98fe9ddcb751d6c3aa09cbba850c425f40ce83343714afd482294aTrust 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 970518 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 ab19c4b5dad3861ea0662e95fa124f458b838cb34d54e2887e7f8314d158814a; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / ab19c4b5dad3861ea0662e95fa124f458b838cb34d54e2887e7f8314d158814a, and the block's
timestamp proves the page looked this way at or before that time.