Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
c1ed358d8b6a1c99041aa5fc3d98924657eab0010da1f4c171cf17fddf906628
5044988ab6dea55515e33e9506ed93a937192052e49728f91a2a407a00c69f03
bc37cfc9d5dd5ec06c289e2ac6b22745dfdbab2d110608a847e91813f2de47db
f9675d290a1179d7898a8a458f397ef85259175383e2766d2c14fb21fb3fda7b
4e72d79096a650f723a1551ba924c2ff0f822ca7cae481de986f6d13f92ea194
7895f2e66a72eff0e56b72c4dddcc7fa1ca74150167a6ff6ffddc1b8f7059463
840074047bf61791df3dbca44ffac15f6977e48be8a2dbfc438fc6f9673c79b8
4db93d14f0fa89dafe352d1033d8b394b9d9b5bab3a225aa02c1939b6c416686
0d94cee8616a6cdd7d555eabec1420edaef5452fc50d3c884676e0aca2d00f6f
0a2c4bdc19c25d15f72a5eb3a16b528508f19134f133109d49a44143561b90d5
0b7e355ab7416881d2177d1254b3476a10ebe997283d135a0c818f09a41a3b66
cc4171a719e7f609e4d4d8e901a5639e506060ee5fb74852ae81bfae0557990aTrust 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 971316 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 0397116c1de2cd24593bf857ac1a3fb0dc4d6caac1d478382f61bb101a5dcb7f; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 0397116c1de2cd24593bf857ac1a3fb0dc4d6caac1d478382f61bb101a5dcb7f, and the block's
timestamp proves the page looked this way at or before that time.