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
60dbd6a3f4525e664a3e57d5bcdc484fbf42e7ff25ef1599b95e71492048c587
f5b9e05ba1fc8b14998d249ca4e0b3c9bb0d24267247ab0c40c4927da3590820
9f33689a3801a9afac1065018d1212c293daa6895b3390dd04827fe354dfc2f8
5b1e8337b42a9f4aa7b6880559db82682cc9a1644c7bfa6a9a1a4041766158e7
6868b51e3e01495a138b3cb569e52ba4d7f4f92d50880adf1e53816e1182d76e
6687ab8f1985b34b06bc8d525ddfb1fac93be2ea587775dcb0350d96e11de81a
8e7a7df5dfe3df991648fec538b6d879721202c96e4e90b4d9c831a0a36a065b
2c31112762b91ef50d2418e8d36f8475c248ff17d4ef660db3d2180a1a1515c3
5e94a5cd059d8a2ace5a02fe1e99e4df8ab9e691436cc3a0a81f7f77a2ec812a
e689b1bdc9128aeb3425ad11d159c9ab6d26668910ebea6db6dcbe8a76e5349f
6a0792ab9974a85e86b4cf8716a7cb7515a2aca9aab01e6fdb34f3e1156b7365
5969d1a4eab43a3d761763d9db55099329e16faed85c054f17e877ed608f2864
e8e47dc60b64807bed5e62a6e188d4240d84efe3f54e3c34458767fc48f9a77cTrust 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 974236 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 70e5b5014a429b82ba129bf14c648d56fb7bf4636a83072b47a2c94472826446; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 70e5b5014a429b82ba129bf14c648d56fb7bf4636a83072b47a2c94472826446, and the block's
timestamp proves the page looked this way at or before that time.