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
da689d5e92c8bb59c6c433851f7f0bae7906232f8ad4492c06f4ce42243885d2
9fa40144db2d07ee47510719837eef0a81830d4131baee03911f2ae6e3004a53
dd1c0c5ed1c0f455683f8bb139077e08b292ece69c0f2eccf4c9b42cc6b41c2f
0217cf7ecc07f72be9d4772621094a39569e2709829ccedd4654597bf0c3e83c
f8cbce8ec625987ff2d754e08796a84998649069730207696ade676bfff6089d
922c151a817c70e6be063198bcae2fecf5192cf1d84d78b37421b97b5b5a5a49
a92265c09cd6493fbe5edad6e7a2ba4fc923083b7e9fdc8740e99853cf108e6cTrust 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 962424 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 b1f764aacdde2ebadd7c3feac0918e1eb3f0a37404f2a5233a7e3c6aa730ae60; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b1f764aacdde2ebadd7c3feac0918e1eb3f0a37404f2a5233a7e3c6aa730ae60, and the block's
timestamp proves the page looked this way at or before that time.