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
d388b8a12b0c8f5ab7d9d459ca129ea9b70e5dd5823390ed84c44d94f3ec44c5
58e1b822b9d9e39f2e9bafec4e680ca4f7b2c6d0c62a94d5247b11f3d3104776
db4fe84ddc6e958be9f59c501adfd50e2b92ca06c3b6adc6f7d0018f22859783
d1ac50216bfe007aad7065d2aa0ed89f15da16d719c22db833283103b82edd18
545c22b2048c69f0b852263ddef1519cecb5a2c97ed91b904b185e8f7ebdf86e
b2d8d376cb40e5ddb5f4587541aceb41c453cc6e410de867a0f90bda8738fe0a
1502b047f6417fc79ebb8a7ef7bd392bb0def19a394af8ac63434b6cbb08dc63
c50f74db3a14107d4bb3a8ca1b1f6735eb8f0a720ecccffe6ad303392a23cf42
007ba4f346700d25908cbf7b697c5d5f0445c4e54a32781c866a126313286cf7
d82237ba01d7be3b1b418c00fbc1c4057bc4fc174eb1bf47bd18614450681792
472649446b07d232865d25d7bb1f0050495811fa1a48c7f84fb04403710ab382
30f33369b0ac10a94167c2bb866b4875c5408a2e1a4e16cd8a256c29df0b6d5a
6b377a865af62b1fe4c39e21d0676ce6591ee17c7462c0701f8ec2a20447c074
11df74df3a0a6c802fda031b2ce479b781cbbce991719722e52e9135fe30714b
8d19c35f84f6566b753b0aee3c6e50aecdf83601acdf205be317948c8fba2942
6c17713340299fe3872f1ca0118c6a5c92bbb07ee9d1255100bc470fe251c995Trust 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 972651 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 201895d6b31dd5f674bf95c931d49ca3000c8942616ab53287411a0db3156447; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 201895d6b31dd5f674bf95c931d49ca3000c8942616ab53287411a0db3156447, and the block's
timestamp proves the page looked this way at or before that time.