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
b4173f1d29dda3f8d9fa69ed133ed4c352f94bf16e535fbfaadb21c9cb2cc4fd
6cfc7bbc46f807705b956f7c6ee6f3607440c5b0c17384efaffa33b1a18a97e8
0e9a75e5d65bdc5148365e4ed4f45f5480ecbc8141e5c52ea72026ea50f89a97
6ee4221c2f207fced92cdf173fca6aa23985bca766752cf8585eda9b511c06e9
616d85b8cae762811f6a3f73c3795a29e0055ff9b3241048646238da26da494c
090c2be0e14a0b7665db351168d778e6cae0761587c3138e21cf7baef3543e11
a703f8a11ead64cffe976acf86c9afaf78be6e8b5aff2adac6960d26bc0313f5
5fac29e23238f33c38f9b80261ac04b5e6a78f3ce85961fdb869cbc60cfa409c
9fef3f97b8d863f2703fc80b5f40206ef41bce25e917f017344213e4afe546eb
c0440e29b3ccecd5549c00e377de85c4c97e0ab812ab7a8310706ec575937070
488c4b26ba4fc614cf839a64950f68cfd3e349fe0d7238e4a0b1d287d087c5c0
ec16a2bd688788cd950242b8126dc9495b8093bf9ad990e6a60efd17aa682000
497256861503abe4876fb3bec9c6ac9b977613a198103992c3a7ed4e02e78e7aTrust 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 966263 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 ed848ead0b41ce416272d9988cc56407b88be004ed39c71376af3e426423713a; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / ed848ead0b41ce416272d9988cc56407b88be004ed39c71376af3e426423713a, and the block's
timestamp proves the page looked this way at or before that time.