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
b7491d8b8fd0b46f68bca6bb38ccd351a44aca1b3cbc3bc36139e8fe7cd65ce6
aee5a345bf9aaba264ea0a6c5b761497b9cf7cb16f9b42d42446d8abf18711ad
143fc03dc54510f74bded9e9bbbc12e4c412c3a62d9fa7ca66f77f7f007d274a
60919f5588ba1d76dcfad939f8b187939093dc9c570addb213f3f9bca56360a2
81eccfbc7867c22b102422e046d45966fb9f25978bc2aecdf6284abe783c62b2
96a619004eb0db59f4c4b718939d81b6ece85185c4574891c25c83f701ff67d6
5626f6923decaab68c58879fa5ffc48602a666e3093e78e0dd1fb0ce29c346ca
d07679c788a69c763f2ae80ffa3788776c178bd03d69a52b180721c917e333e0
5b05a1dadce894724c8e7cd21881a10632aab24d08254e153f3774d682de7e3d
3a83c9853b093a6832e6b62d0b7d94c3668df7b0c33b0f39d8c480f361f8300a
831f6ee9c655f1e29eea92961e823f9c35719e78661e1be1b70f88f77b35f3d3
a58427c09d5dc5c2939cfff2b482e6a9452fb117bbcc83e0d3f6bcf693bf24c9Trust 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 962771 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 3ec3e93175211c731ceeed471a99a73f33caa8b0ca6882acb66d03eda333cc34; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 3ec3e93175211c731ceeed471a99a73f33caa8b0ca6882acb66d03eda333cc34, and the block's
timestamp proves the page looked this way at or before that time.