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
892c3c45b62bb7b378e9a1deda85608cedab0831d2bc8bd6cf15b02b9221a124
b5434586dba36805434f3463075a71e481f68f8167ef8767a7d67192a7a4084c
01caaff0f93677155143d341e04f83340ced681f8e5120a9ba261c3d26eaed73
64661912f2f5d52fda4ec939baf1584dfdfdd839d6e774cf0f3dbe4e7bb8efd4
4e7d38292a9a698835b20fc2c00ce0a7968ca6ca42f2c517cc5154fb1f7e2177
96095b3f3ddc1933f6d31e49f66edc390684eb2aaf0d17406d16c0b9dbd14981
43557c435008c44a86e2e1b09d56430a12be06adc1bf8adacf93e208f9c736ff
d99a4ddd808aa71dd85c56e59bfcfcf16e8be77f5835ec493a5ed68571ba4789
1d3bb4981455d63130d948bd89f5458bbd519ec9d7f6a9cde087c8a5ecb92f0d
9338af4ea3716948675207efb7f3ca7cd7694c53f3d137855bf325adcacf112c
453599bd23a6c1f2174e0997873e9125b870a2a565617bd2f0035c6a13c82104
f917b1b73188edcdd3a1506d482e5f0430ad9cb30cd58100fc1b3d35f95f4ff0
2e933c94ee39c41e646b37b3b7e50734963d0f9f0c6432a28888b5dae00b22dc
d74f8a93a98498def605efc057f274bae5c397b8bcbedd8be85668ab2a84c620
a5526893f191fff3002682d69379434c4f4eaeffb8d1fcbf2374d5a2d1584cb7
d7c599bf86edf88c0a89397bb175aed9378c05d5e6bf0c383ca4c16b5ca8118b
fe583e5eb5b14eb2fd2abe38ae6dff58c4c5269ecd80c935c618ab5b682acd4eTrust 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 966888 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 6a8311a59b40cf60dedc72c01de99818ec31e8cbf7a5ace9c99fcf7630e13bca; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 6a8311a59b40cf60dedc72c01de99818ec31e8cbf7a5ace9c99fcf7630e13bca, and the block's
timestamp proves the page looked this way at or before that time.