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
83cc55d54c38d69f581df1132bb7b8e19de7acbb2a6d266e5ffc0cfc660f428d
543d1200694522b3b4c2f5ad188a9498ee3fd59de396362d6e3865e82504e8b2
e25e658897fbd65b2a150dfbbdc3fb2e267521859bc29fe29f9406c79b1ac316
75a258feecf7406e6b3c3d8cfe312959ead1f0ffe493aef0ddd154ebc74eaabe
fd6ae26b60a47eeb28464781e10ab68cf8f77e21d4e53b321bbc81d82ab7d2ee
6e1ab7d8a3887777eb7154a49eaa2bbc74b2685dc53c4bbdc8a7b44cf328ef9b
2c8eed5e3f8c0b64cdc6156685c44e9ec4698bfdac5f9727738b20696ffdc9ff
1694f5f1f8fb7850dac23a5f596d51ff9ffdf51c414c5d92f3f8abd36d6ea287
146ebaa35772613d81d2e077dc1708415440f3bcb34833bfa15f0f8dcc03d100
0f2fb6a54f02e15284e218aacb349cf6fc0d18ceee44ac57c9762e6b6d357077
183e1a590734e1b50f81b8962d01df65c7c59ce21424a3b5170e41722c8113d0
01c7e4867a57e2e10ccc073d17b449ab8b9fca67c62af1d84f8d577cc84e7994
ef8b6892650afb0f9f37e9ad60fcbd5d5be2d535701979bbd0b443c07166c62b
7626e2af998cd1f3984846e8eb37dff03743f6dfbc3809898cc20972d7d52229
c60e6635d51d2a8258c796962fca59c798196bf0a5f622c8e6ca3c6e50d08230
ef305ac99a5015138342a9d7ee887eb3f77567c864953d8b420e21de5f3f23c5
cf6c6f30ca263953a37db052eb58ad7610cfc4d00673a3f80de850e2d64af0be
9cdbff1dad3b1a8879c47a0f90685c0a766841a4250bc9f55ce7b9faf8d7ff67
f15744125c32dd28fa2ca408419419509260cc8a6c4e477fc7ed2411097fff32Trust 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 972295 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 eb37fb85fe00ef45a571f8bb949a6cb5a865e0f98d2fc4115c7c9036ca9201d3; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / eb37fb85fe00ef45a571f8bb949a6cb5a865e0f98d2fc4115c7c9036ca9201d3, and the block's
timestamp proves the page looked this way at or before that time.