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
1671d9120d47c9994f7623e8d701a38bd79948265663cd11b9a7048762e687ff
8311c781c99010d604fd2a26734e32dfa3f2ec084bd6d3756de69faa5ca50ea2
22dbbd644c86c34d8c4ede0a6c41b913b7519d56389062c1e96430709f63220e
02183046de3e7906cf937d7480b4d24a18ab9fde37ba3a1f739cdc26cdd3b371
5efc2af9428c73b261f1d1dbb5ed34b39ed3d6b3430c5006763eef8c58103030
9d3234f6ab419eec5d8d1a105f39a464dee0aec5f2182a7d9313872c7d535ecf
6aa43828759bb44cab5726e88591be1d5ff672ec8e9f83fab7fef227bcde19ac
699e62508b3df402812fde09e87f854abb9c63f9db96dc63d6de8195514027b1
697b209e3ff7f1de1ee8d7616b94a8a03d51edef5bb0b0346c6984e03d96efe8
f3e62b788758d98c37f40b35d3f6d16103e12bfaca2d7c3e19452ab90a431173
6c6b36f576628fdfd2f38f6ffdaf5fe983314e9022a03c63dc5ca2e17a760fd4
27fe6569f22af44664dc28dfe94cf394b71ccb02ba1505f3b0e92f4a7338134d
3792bf27be84fb169463b791ca17925412256e7e4e16279711417a9d03213395
dfad1fb327f7991cc6fc1ac4ea52b9cb2a7c249451f7595765b8203c498f2656
725f0cf027b82dbf56e25a3e2917e96fcfeadfd0a4ff26d08de1a3a9660a631eTrust 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 965106 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 4d1946d97bdde868a9cd47d0c2d315b044a77f016459e674de336f89075651aa; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 4d1946d97bdde868a9cd47d0c2d315b044a77f016459e674de336f89075651aa, and the block's
timestamp proves the page looked this way at or before that time.