Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
6510d0e079e217ce6dd0eb4ff4c26d5b123879b6437ebd77b3bee7e8307ac0ec
146113cfa8674f40c2a2333c282b7a3febd3f541e9623110ae8aa3d14231939d
a64bc2bc1360fe7b92278bdec46eb852528c901d70a126f8accf29c02bfa8aae
3b42f0c0ca6025ff6a4902d084b123b3cd8d8bf4384950efdf8c6deb9d72e332
a9e369b5c0a1bdeaffda8372f7340c5174d69b9e191b9c35ee1adae7618786fa
7ea63337dca44cf6f89009c3a7b6868f497a19e537b082aaf5a9ab95d129b18a
55ed048fde6c792454a7d18e2d73cbe359b15b4af1a5a63ab42fe5ab66ca02c1
a2adaaf7cefe46625412a9d01d90df5653efdaf02ff723291777b4ac84c79d67
01845774ebb564194a07e15c3967f8b7c71b6b934a219e43c9189df11ee8a973
9f47a62bc08f9306a57edb88ac5187b8094f05d2e4305addd43940de9499ad7cTrust 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 963772 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 e12588d337751c50cdfbf4732e9c73809681a5bcec79e2d970fce2f5c9a63fe9; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / e12588d337751c50cdfbf4732e9c73809681a5bcec79e2d970fce2f5c9a63fe9, and the block's
timestamp proves the page looked this way at or before that time.