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
f220b4030a27d42419f4be798191f1fe3cf77365797cd637b2bd049b0a8aa839
dc50cf5d9acadc5af7bcfe98365c162e224d83dee7ad49c028e294142f1f4dd4
9bad8155e7292c5bd0a4973e6e5ba1d30273e78bc8bc71c205d4ef651d417ca4
236e9351ed67a06ca16f47b2214690b8b8d24bf4ad16dd0c46a4348cce8e0388
4d4b3b153fd247295893d35903be94896eafc0c523d88261f273c35f5e90a64f
d00303335f111a32add2a91fb4f762caf4c46a2564d8f81321b6b514ba45612b
ea7eed86f68d867c4f7969fdaa924ee5226701c0f780e9f4be3abd1b0cffb32d
618b1b5bc33e7f39807efe2932f7466d6edc34411e43a6fce8eea63a0d4f2520
cee579665a014a1932eaac6a16ca232f25594a5a8551f4bcb08b5f05b7f085c7
e4fca5e1f2cdc36b6e99cb2c4c508a88e980edd62b5ee68379cbfccb36b1943e
bdb184ea65afcab5d9c6a6369ca1e583b203c5fdbbb2f7dba4ce87fe7e161d30
11283c1171478061e7274267176cdc9a538d461ebcd3f682fd198f8f04ece11cTrust 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 962735 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 a1060558b32980a9c2989f0adb90b217e133c10feb5d9fff536ab4cfef61e66e; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a1060558b32980a9c2989f0adb90b217e133c10feb5d9fff536ab4cfef61e66e, and the block's
timestamp proves the page looked this way at or before that time.