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
480ce80ead1f108a3148204299c155d515462899c5f85a9d0b4adfb050f93c0b
4ee1bb9d5b338bddc45c84071da32938a1eb17766c0d14e6d1c3f05edabbd6ba
512eb9ed414a3f9ba179da2cd847f69d432aa79b0fd3d407951b512e7882521b
d75ca547fb28f020b69a92d525ac47c253d7f1935fa86b0c0c6ea33485288dc2
08778bed08470f65cd0a6c63da79eb3fa94a73bff8e388dfbabdb7c38908d574
d532198311e2c20ca28f52e803ff8abf228bf412f74c8dec2c772eefd7ca76e7
4e8675cc17a6fb982fa7c7062bd02819c9efd6e8f1d7dd468ca7693529712da4
c3a96f88e15870884d727b1acba2c9a8eeea0143ea656845d4b10e35be7a2880
e23acd0dcd58261f942628f1eac629480facf8a01d2d656aabbb1ca3a08a695f
b07bacebfd1a9e6c4f98b14d6874b57af601a575a398572aaf982e9ba730853d
7033c3b4da0ed93bc1de67cabc6ea0e47bb8e4ec37c88389d4cc546683cde324Trust 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 963355 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 5e065d711bf95cf43a48f1b401ff0ace2ec555cacc68ab0224e7c9bd13df1399; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 5e065d711bf95cf43a48f1b401ff0ace2ec555cacc68ab0224e7c9bd13df1399, and the block's
timestamp proves the page looked this way at or before that time.