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
71bd8bb3061aaa4b6839ffa688ccb2ad2757720e3ab637043b51e53d81caf9f7
f462327ff6bfe6cb809bc256790a5f1f235dff89afcf5f4c8786993d50342392
c22cc6e7cf468fae9ebcd27025ece6a538a0ba79bbcec72467936c2b77ddfdc5
6dfb2bb1daae133ff60417c9f576889cc42efc5e1c4409239e2fa303e40f5a7a
e257c935b4c035864e3e2695f913c2ecc56e485a2097d1cd4086aa9af536666f
03ce766a9b466fc5a8da544f452328d5c639194042a85eddec7f2e22404292f3
1ae85379e7b089fe207f6cffc3a26ffb42afd2e8266445404bab787e331f3f3c
389b130e3d476488a10c0a37a261b2c0cf070dfd8c15aa13a4aab0608648bfdf
8da9ad5aa7635718446ef4932460f5dace5c87b6b40f68e8eef8ba03a71673ff
6c12d530f195afd16b95cfba5e25b3a2d1246cb9a1d954e8b1a278e140883d9a
8cfccaa8670e8fe54cb5de1162923c3d40276146aabfc820bdcfecd2495ad64b
d7b02c396c8ca5c860aad434de2f438106def756524b3f3e189fbe1d7b9aeb41
a72116b57dd536a8edc01cccfc18e645c0988a03757156c7d1dddf8fd95f0687Trust 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 966361 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 141334d34f7d363de42be4f233e8ad5958f4b2d2445c292d684e6789d28992d6; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 141334d34f7d363de42be4f233e8ad5958f4b2d2445c292d684e6789d28992d6, and the block's
timestamp proves the page looked this way at or before that time.