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
7dbf8c9abf8832ff7dd07b8acbf1e81a5f60ee68fa990f3a79584df84603934f
34943590fb023ef317a2d1d672b81d796beeb457cada284c32e527c2f71d5f7a
a490a830316cf661be8d19d8ad1d3186d96961311d5fbf43b348291cb9fb3db9
10ea7e3474b9034c80d31c988308dbc6b963c1f008ddb79bbe944aca0fadebc6
e5342fd96956517056f0b2d9e955a9b482a7ddc53652b53ac30efecfb641682b
8d4f4b98ccd19f23fdda9e743cfd09412d43626636d31d7ea63f66b59fb61743
ffd7881d6d182854de589b7dbf7739465f1600fe1bd21804119cdd75814fce59
e49da16f678b4e68e4e9de0113efdf48b2960517f2aec581a3da3d15fa139c27
9625f61fe3e53add6fd3413d55b9c136eb3e7d41112ff64eb38a5046e91cf2c3
2ef44eee468bda03ba448f05ba4bd9f49587d766993aec1365af2a69cb9c0bb6
cbcb6f909d55bf8f9e02c2c812e7fd242795f9fd02d448759813950259f6cd54
289998018e90a4bd1794eb81e5e3050c8a5f23af3d34a1e3606867622d676cdf
6ee0a91c6953d36098114d31de0b08359af7c4bba72a792527b131d338964906
0abd23a50170d896925392bb0a949f0d900a02a5a3bde5ec03f32c8f16b733ff
69c62681b92b67694f99a7759a0e1ca0f505c97d74c1525137a95641f1f3d88d
a5dfde41a04223dc23b6e3a0866cf5a88ce0b518837b8d0fef3f8ebcc9781bd4Trust 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 972267 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 a37ae6d0cfb0bbff84f99bfff8730d6936eb067ff1d208199b52583891f29c11; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a37ae6d0cfb0bbff84f99bfff8730d6936eb067ff1d208199b52583891f29c11, and the block's
timestamp proves the page looked this way at or before that time.