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
ba169884ca6508f0aa7be876eb903ca086e03e757853ec1051667ca5b56d6edf
877a63c04ca4d52f4b7e59d709c2983686445d7557a5eb6d8f0c0eaad099347c
d75a436b52bb64756e6ae4b87bf0dfa8d0ab51d28c8bc5edc41a6b3e54a0fd2f
f1e4eb993f5d6a7ddb61d9fad426dbc39ddc4fb24be7d8e5a8b093f6e8c89f43
b4e4ece60fc94346472f4946d001248485ac4cd4ffd33ee03678243e93c1e385
a154d7666388cee053569347fc2d42651bcf85d2e0d94b37115abbc27ee1c050
08e0f2e644caf5df2c5d7ae3d7f6a99e017d2ccfee5e9f3d9450aa6a65b82b6e
a28a2b31a6d4a37bb0143042137a0f7fee79dc8fc1f9d825ab134f91a61e0ab3
ed5ebb630d445a40239ddd836faaff8e6ca197856f6bee730e6627a867f1a549
f96e68237339293836feef95a22397fc041f280ce65f24912c65f51525bf4b7f
a63bb4ea934e927e16d290bb4b25e11cf6009bde30088e18b297684541b79426Trust 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 964127 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 76a63761cf3a2c782b98ca0eeb07f0b8461744b3d445b3e5ae76aed387e378df; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 76a63761cf3a2c782b98ca0eeb07f0b8461744b3d445b3e5ae76aed387e378df, and the block's
timestamp proves the page looked this way at or before that time.