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
4faef0f79f8a5fcc0f17739480c79f887e7a3d8e45c65f2fd6504a2d7e081c3e
308693ed158958ec90fc81110b7388c883b098606afc1a19486f5b6890aaab24
fbe7a2744463287bfe33591296cded093c19dff0f7e33489a82f04b8a298ea28
88f943c88e19671e326f1b5bf476d68ceb192d1b5a1df737f16eb247743b54df
a8f1905854725a11175bbf54d901e482ec7d672241551b7a58225bf0bc62472a
bbff45fb5355fdc7eea81fbe122e682b80e6b3f190ab467c381a493b468298d2
988971a0ad6f2f17e663d7c749b95f1532298ec26f9a1ef824a270d0a2fbba49
e1ad640878fd460c827608fe6b7ae7ff78c46fddc1e21f82712be85ceae528d0
4a63387787ebaac18b18e9ba5f3ea367b656c95ea6d1422c52d4faa978f8c537
16fccb3a9c23f792260e1e0aa8e886e376d4d26f5fbc4d5889e795156ed7ab70
74c67dcc1c86a4c30892194812f5aefcd542185ca211ecc5c5fc211c8f042852
9bb5d232881d0d44bbbc670328b014e6aaa40d3b544affca720d6a1727d1ad4aTrust 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 970406 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 503354d828e3558acc5058afcc90cccbf280fa2d7cfef63a22e7beceb3f29d6d; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 503354d828e3558acc5058afcc90cccbf280fa2d7cfef63a22e7beceb3f29d6d, and the block's
timestamp proves the page looked this way at or before that time.