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
2980335ab5920dcaf2da089c821c1c287dc6c1492bb26e85d6fb9736df7ea65f
ff05946a892e00094723bd7fe3a492300cd555d05e7724502c9fe57090cb9617
fdbfebc9720d798fc199f1206b593b1fa5131a934dfdcf6d37ae0e40b8ba2290
d9bc7192b0259d619322a391299f07074899f4f3a3f4cad228c4a244f387c039
95e4f455f332d2a1c1fb2adce16c84e5b2e4f387ffc4575e2e82519f67e2c23b
139291c22d4e3b11307c6772f2a61d16065783fca6f1f731876d8d7a0cbcda6d
921b075d2fbf5691aafc427b6ab8d950b07b9c091f06f0526fb63aa32a5d40a9
e431cf71642d7a663f99c0a4226624325aef355dcd1bb2bc11e9a1897cd309b4
baca4106b530aa220d978cc9290f728867676de34dd025523e4d97f9a7db7fb7
93bf67a8a4f83e7b329217236796b6f35db0be1e9e6ce719df1b6657f5b5b44d
03902d24e259a99274e29db3040183c69c0e7d8193547d258287f641087c9bc0Trust 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 966793 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 a4cf9becf537a2e47ee8f19ef9704fb24a7876e8a3e0a4a9a6daa2c5d4d9fd35; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a4cf9becf537a2e47ee8f19ef9704fb24a7876e8a3e0a4a9a6daa2c5d4d9fd35, and the block's
timestamp proves the page looked this way at or before that time.