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
f4a971f023d9287e65759bae57277ba7dad497cfb42c7475fcdbb45d728d1c0a
d1a8c124fb2bc2d9b835e1dee98f3dcf68c4601ee30f09b3d931abe1425dc14e
b3a95772ade9ffb91872f2b07c87a6a21caba4691a921f94eb34872629426fd6
ac93afd932c7a65d1fe985993e1464d40dd6b6bb3f4f22e3ced5a87a732c982d
850464f84cb2f29aefd2a79754cfcbcaa0e7182f99c67ebcdf701b02583da54b
f47792076e4b5fadf9ba11636202471854dd41c861217ed978d6990b2d5a08c9
cf0779f70c3d5112fdf65784391c1015b83ac5a1b3a7f4e638d0c3cb610010ac
f1d15f3c838e1494fea8a4b9db1aceab6394a93842268a2fb18a12f3dfb4cc5a
8b671149eeb3fab3a48f381a7e289ad0783e0e1a964531d6346a2be0d9880896
2e2108bff0b08de6d864a40c2d90190e23c282fdb4287c7c20b2e01c6b49040f
6725b59392b8d5786858ba4e882f8f4fc53134421eec315586586002ff8a14ed
ed3794d0fdff93e821320b6f36b2b2492417c9e6b3be8866b1f461cb655fce07Trust 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 963371 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 97d3b5e84b94b56c0c32aa497166d16a1926cc95f8f80ee6d5fd01926d01f64c; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 97d3b5e84b94b56c0c32aa497166d16a1926cc95f8f80ee6d5fd01926d01f64c, and the block's
timestamp proves the page looked this way at or before that time.