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
bdae57b79dbf0f528855cfb70454d1e56055cb3c6a542b93cf0d34f95c0bada3
7b1dcd5d7fc49811be8162b30acc976dae78ece713593d414e1c3e715799e14e
cf80b0ba3c35ae0fbd34353a0760a9f9c8421e694382c272c5972bcb8becf6a4
b42576d99109a40775729bf5f330847b2692aa9b7884b5a2b58b962f98edef8a
a036ab17e222ddbc7563a5b79c2beddd6773e669736fc6733c3f0c7eb0727681
d6901c2278884417047fe7e95532ec047aa830478fda3611ee7d978200317d8d
ed9f6fa7c42cb8a00d7f3d5a31806a835734446a045ee90f39db8d52fec0de1b
40b12888494caa73ddbbbc189888a25ceec6bf079490443f30ddbbdc06251cf6
51ad48d5a3bab5111525e1170b38f7abf6f3d14ae39e5df9f20f190329c3cdb7
42a61da20d7a4f2d6ac775e52975ea8a250b49ad2fd5e30ecff100ca4dffd4a2
26f5974bea085917c4590a3f84262d43afee1b523b3c9ec6ed4e57b3f328c18f
67988710ff821ffa63c8d96544d4e6444160459596b5ec53d37310de03368649Trust 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 971272 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 bc388da6c145aac12ba653eb1cb4ba88eca66fb5b244b10a4eb1b1d29b7d95f1; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / bc388da6c145aac12ba653eb1cb4ba88eca66fb5b244b10a4eb1b1d29b7d95f1, and the block's
timestamp proves the page looked this way at or before that time.