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
0d17dccce1ddb15208800ff8006bb6346f517678b882f1a5c960efdcda64c201
4438bd47e27dd64c105fd2726210d5e867ec8a45993aeb81164c9abdf7c9899f
6cb0f06742104e1454eda47392776bb12c97f878c42bf5d895be21ef01972e09
cf5b6f214be0183bf047949701c061c64337f7f620f191d8de04cd4cf5c83345
df5a48702e8540cbbc6200ff2c5cc6b6e555131785ff9f15513a8bd15a073a84
9243c3bf6a6fde51fef4ab9d0661b831a08c9bba7f39eabb3c91741688edd174
4ce95c01ff92deec58f5025935698a9e17506258b7e87e1a0d7d6a11277b97c3
4ba95923213191e9ff79f95cb8d60397231d732dfcabebb27020ce598a8de072
fdaeda53f9a17d30b1c232e6ec0d25d07bcce6eca7a8e1dba4afe67cb5fb8e4e
b9dab46137e803ab0efa765a0affa7a891f0ad4a18d3d8481f5910cc16538950Trust 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 963163 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 89b34e08808e80941efbc1963f48c01ae011a2ca2e54de584352d8dbe5de3524; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 89b34e08808e80941efbc1963f48c01ae011a2ca2e54de584352d8dbe5de3524, and the block's
timestamp proves the page looked this way at or before that time.