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
fa0eee2e9148a85da31a4661e4a06838e9be2b5bb0717b65185f4a02bdd2e76d
832baf53ece505ce99d1925917fc31b22fa140782930715a2af7d7f3c285f41f
c9914b28d512cf08f577d4d6b16ebbd1bca4bb680a9221c29c6a8ede9fab41b6
05ab5a203db830c75b20feddc0045a238b1a56eda750e872676ccab661477c3a
78bc792d2da9b228cbe2cf747b94a27faa1b99e965d1ce1d74e9f7f3f0fd7d0a
c30b0dcd25029afe0aecebba0b3b3b0c0e4c5dce13440dfb10154731740538e9
45f84083f59129b85d02b2d767a569aaa555c06f91ece2d13be96123571ffe8d
c19e1dc1354028c2564e3ee06780300b6bdffc1aa2b51d76d6462990b9bdbd9b
b79a1130005800051f71e0884f0ed56566afa479a3f7b9ed21cd2a709da10bee
1acfbf9ed9801642fe13442d3537eb8cd0c38ba2f9dcc7460b863a3ec244edd7
11076d79a8255262e30b67b29908d58aa26808a9b1d42d3064bbe3d71f83064a
927f505064be1b19199d931afaf4362bfcc2350ee911c7eaca9c28f59e97027f
a9b611685effd8dd3fcf14982cf111d0ddd37afaba53a8bba97a444b00e487be
d7c4281674da4e3742f7b3e615be7a3ae3693684f0dbb668077df5d4cf7d8d4f
7b9f6eaf352e9105e5e5d4e5187fc37924523c5e66034cc119b5fe8afd0ff9d6
dd0f966842b9da76245d095249a19ce60c3b69844947f9b6f37b5705db7fd38d
772af6dad1a3a0d5d9dfa795c9b07ac0e06a94124d0d9fced3053b55a5290628
8f86898f67c0038d9d215c6790b90a3c672858b5978f220932cf2e5c2ccbc8ba
23f73605be544fce6bfd4ee1b6ef1d882f491d9d77d6677349eeab6085af416bTrust 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 973567 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 017b66261d1a20dc5f52e673df7471a08c130c2810563b7660ef75be99a1d659; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 017b66261d1a20dc5f52e673df7471a08c130c2810563b7660ef75be99a1d659, and the block's
timestamp proves the page looked this way at or before that time.