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
de7153b94dae093223ce17b665c9321058bdc81e50c41b2a2e56bb0d2e0cbbc7
c2ace72ad93c0d53ed488036497294cc976d863317fb3e9e6d2822d9b28853a6
c553626007d82afa8d40c6274d3d021fae09877d49da20c62247f714711f07ac
eb2eb335165a47d6997190396e4eb0c8e0f4f1110dcf3094ec64091e17a74a18
4239efbc50c99854c0d7c93760f00617dffa9001bc58a7c1071691890ba83245
0e232085875f6f8687072dd47befaa6a3473e284ef003afbe6c34ce46ef97d65
70bb63b49337df35d8d3293cf6a98ff874d749fe9ceec21f4c9f5af384f54c62
1e7a71cf0cbb5dc5d699d91c29f07f4c77ec38971df9f7aac814eb99b76c65c2
b0ea27c1f419da3208ed05e9e12658044b9983dc55575a10493f55822f3321f3
0a9b96cc65e8e953495071719424b24be6dc6a8a62ebec325458e13d472838d4
7926a9152d75f1fd99b364f8d74e87650d48a34d2416f67be70e14ca0a4da3d3
34dcb1a402311815842b33069606cd985112dd2413e6b3139c168bec5e14f5dd
463023df8059fcae136202f026944d3979ff0697425f7ccc7c1798af80d26b27
de7af68ff188ce20a3725ee34d50a26582423b2589de4f0b5383728eccd701d7
01f8eabc60c9e6d0a7c4fa0acb149c9cd3cd9cf7569fe4a8ab0df07312273978
87aa01e8ecbb2d8df2a0deb8c8eef5cf4bdb94c8a0f45ceac70b1af1112a8b0bTrust 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 962900 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 7cbcff16f18929635b7144e8aa27dcddf3fc72c464dc90aeb4acc68c6a4044c4; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 7cbcff16f18929635b7144e8aa27dcddf3fc72c464dc90aeb4acc68c6a4044c4, and the block's
timestamp proves the page looked this way at or before that time.