Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
3b6963d0c6b16f927dcc56b2417ef8a3ec37b1ea7e1c48b4a9aef8e226099a2b
04a129de7ab269afdd7423520392c54fad6c87c8348822462540156faf99655f
5e2f4388dbdcb4aac898dfcfbd65fdb6e7820315534e3c9ed70a53a71cd30bff
49da972636aca22a8bcd9d535d0e334da5b58005bdc0bc7bbbbdebd583842571
2d86c76320fb1086f82b87b704233cbb3fab96618ebe6d95acee30ce87729cceTrust 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 964804 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 c54f170618a1caaf587b5a2acda8a9c56758c5c87ca865fee13f64b0f6bc8852; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / c54f170618a1caaf587b5a2acda8a9c56758c5c87ca865fee13f64b0f6bc8852, and the block's
timestamp proves the page looked this way at or before that time.