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
afcfc8e6ee4deb33715bde37382e85ab26708eba6b81fe4f33f21a88e638ae6e
a2825e0ec67ff3d46a763a07312a02a9fce8bd5e3a1af181fa3c41fab62e7b53
600be2891c6644c043422b565243c9d01de3af2d784f14f5db77fcb0436331f1
bc05490ae4415b40cb197ceaf111789a0401f346ebfab81c3a54fde329108980
6c8318dbccea197f9dbbe48d2dc6176b430ef19715ce8fda4f223a33fdf68442
3799ef7300fbb5de32dcd8dbfcd4f2e40429ec87ccdfb4b31cbee026b38c13d3
663595b5a77ae950172c7c00060e70bb1bf26cb82780cc8e0d1e5907a02d77f2
88f99b816ff962338b7382db7876f92f2f4acba5827aa22efca8ee45009b8cf0
1b829561f042b4badd26904e266fac75ee8962121ec1650dddcd15884d33de2d
773e7723eea6fcf21a4791e4ff1e3fe3637bea5ad2ac9bf6cccec056b3d5bfb6
da0722bd73134ce144e267db2c5614c3e8b5f43fb7b23c4efbed0894b9ee131c
b8b7a6bf1cbed02e82787d403d101111b12474233863d2747290bf4f6e8f1420
38ba5996fa0aee3091c3d55bdd5f7a0abc114e48a2bcde38239cffb897148279
f1ea76cc4bfdf674ccac211fe8fad61a1bba4f827e294571d42dacdd62f9acf8Trust 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 963058 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 d9b5596269e8d63e9a4ab9d27c3a0646ddae11de9548da64994bb5aa53ca4edd; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / d9b5596269e8d63e9a4ab9d27c3a0646ddae11de9548da64994bb5aa53ca4edd, and the block's
timestamp proves the page looked this way at or before that time.