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
80c73bb895ada5ac965646bf4b87b62fbdc55a2b7b5980626c9175b3ccfa8753
4bc8ea47d22c7f8a90fe137cddc450ec7acabb37e11c77a70092ad4d185a7ad3
7ac1a4298206b55abb9e2e646590d1ac2d5347912c90582fba938d3a796cab0b
b1df06e73da86ece460fe0b2c4952288a9bce0ac44b345c2d5d048c246496a4e
9db3c49c91ede8e317cc09491c760acc7c750e11f08ed7edc838ab4a0a19427d
00860d40d65fd4a876e0c85e883e6d7abc90413cd7aea142d9b6fcee8de9192c
4a6bd552d23bc7c05e60d4910986fe134158b025f8106a3e8a8a59ed18530d1d
57a170188475512db3c053f9ddbdf7c4851a7931957029605a13365c3b14af00
2251206000e0fc23f13328ddedfecb025005139591669cfa1dfcb1bd940b47b4
911e248c5029603682f9a7b81548b574de5949fb94053e4604c1b586cd839efa
74b1b577b34974379d02bfece9b5059b85d140e151f4496c63b22c0445ee8667
2c0ea1aea2895f744cba79b166aed9284e833dd5cd3309bc0cfb900d71228c40
1f887ff68d9b39defc90862a8202f5ab8f9a10925eaf6648534a6acdf42e6f08
a9fab1a63a8c2ad123f5d2f399e81d91455669f21c3ce8773859cbe564571024
37d5d7b7247cd5a67bd2c59e43309c68d8953afc5ec53faf1548f7e851ef2bceTrust 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 972167 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 0400a8e9db8103d2cf3ec1fa1fc4aac966816ec0fac40cd481f6b8100c5d1773; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 0400a8e9db8103d2cf3ec1fa1fc4aac966816ec0fac40cd481f6b8100c5d1773, and the block's
timestamp proves the page looked this way at or before that time.