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
75f56166d98c0a262953e06f8d2f4891d1b89fb699ceeb8c75b6f1e016428a0c
c6be6c0b98d4ab0b2a9063027756b6ab70e2a60d319fecb1f8ac45def6676a09
b7d077f46a311327830108be80d5a9291e52c58c2981f2ce1606ef21a2465b17
419a8af9b5e8f76850a7c64891ef68528037abbd4b39e8006404286d5e2d7ac6
6d9d36cb42ca45f4c3a3211bd126f9747ae6ad2372efe7c5509fe05f8e78013c
ca294ef935b3bd35d9391be00c6ecba00b65098a458afe671451026c778d0a9b
a3ec90af42a5cc75f56e78debfc67e2d73697945a0e957cbb7e2a8f1ebe43a1a
fc1f0d1565dfde1252f904a359383a991b7c0d06c08b8509d35c96b719751f62
9d1aba3b07dd8587102445f940aeb690c5d03b1c0bb4d0679362ea649691b34b
76413d8eadacbaf1aa9831ff1992443eff7900cf6fcd660ccbb979614b221ea7
d47e5df3f1213974e93d692681e0ca8073797bffdd9ff406f77dfe6e5d05733c
7dd4173450c70a9e41f200de305dfeea646f185a2d321da7d58520c087aabc0a
5324f20ab9273968691218957fca3a595ab5438d7bda264e73bbb23e5870995c
e0c5df05f368a69e7fccbb884df3fc8c7039c721a9a6db0af945619decb425d3
cdd15691de809d02d75a3af319c3efa5c107aab40ef40f3b8db480dfd99d8435
f7a481dbcdd3d8216d10d1185f6c435a9c3f3bded08ec87aad40a9f2c076af53
8e58f2c2df93c2fe7b4128fe52b3b4aaa288487b12e990b9ecd1c31b2ff69c41
854a8c638afb33c391fe179e657d84d6c736e9d67f0f7c4ecce7e667f4c26f15Trust 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 964647 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 af5bd0da41e23e13cd07178df114e756f222440a5cad357e2cd19e69aa05d058; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / af5bd0da41e23e13cd07178df114e756f222440a5cad357e2cd19e69aa05d058, and the block's
timestamp proves the page looked this way at or before that time.