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
e3d4766ffb8af9871895161285630e1d8fb6e7ae4d09ed5bff8b330fb02e7eb6
cb2a7869bc147b906e5ecb2ed8ee56c1fb23b1e048ba33a4e9768cc7283330bc
90a5371670cc7606762fb6a6fe3203804d3a601a5099c71f2603fbd9abe72dca
4fafe67b91166bfa5dbf1d7d73c9d721de205333d79288d0eeddbe8ebfceaca2
db8c0357d0d87cbd41956549ae2ec6f3cff4c30ef7626caec0c5caaee9b43256Trust 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 963704 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 522398085e42b71ca9d2950ff743189878321cba185a6f94a10fe240d7b6f638; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 522398085e42b71ca9d2950ff743189878321cba185a6f94a10fe240d7b6f638, and the block's
timestamp proves the page looked this way at or before that time.