Web-page notarized
A tamper-evident timestamp of a page's content. Pay-per-call — bsv.cx
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
ae0dffd062b048691ec38fc1af8b60c8e1708d9af2c21f38586f1e81174e9db3
399cde66cac6270ff9aac23e99832274332bf039356650431d6f00092f7bd6d1
ab452df227258aa1fc41e3658ce770b19c669fa7561b538aa2733692fea6b61f
4d5bf32212e5ee8ea2bc8463bd6b430f0d84546f45b492145827efd998bd8165
94f12102ef0b70d830372f8768dd388e0e1eff94baf2f0a02e82386b2a7443c4
4da1014bb150ea3058701dcc8e6bf349093600d58e664295aeb9f257d73e74a9
e92c161f0e269a857fab3c55bfdcc65903556f132f3c7fd38901da58e33dcdcc
96f5cf197ebdaabfe2f02cd35eb47a3b79c93756d55bbc3241248395d42faebf
30df8f306bafa9e52c71a42ed9ba8e1793f41c731b85536e496d8675c9e47aee
53bcd5f8feaa573f28137e7ad879b3c87a9f7eae8e05b85ee607b24f340ee5e9
63e8c327e0636276d06203df5e6a3499acedb156a9723ffd8e74fd3dbaae72d5
2e65a9390e7c995cccaa2562777d03d061f099ed73c3604d12d221520ecb7e0fTrust 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 970656 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 018c100ba15373c2e266686552036bd8ff8e93e375d4f3bb47f9628d9cc4abba; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 018c100ba15373c2e266686552036bd8ff8e93e375d4f3bb47f9628d9cc4abba, and the block's
timestamp proves the page looked this way at or before that time.