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
edc26cce654b93cfcc8e85a294bee217fd73817f58b5a1710f0833c70ec6b7ec
53b716c9581fcfd88d8ce431f8b8ddae0b390dc3f8fff326c933ff6316df31dd
2db60aef6270fde8f262b6acaf7daae573792cd29df3e38b228e459231dcb5a1
de6029106a04d542d651057364a9cbc5bb576615b42866d42c783d603949c6b7
f9dc6d947f6acd7f2e0ca2e1ca9f0888517840dc088be2fa62fca180fb83c57c
4ccc44513daceee3dc9a82f383def434a4b9d6f6cb54e4870eb838f47731328a
512bfba17fec34434faf31f291c91defdb43ee8dc32d5a6e3925c74cad0b7ebc
f9b64b87ec2277e14c1a4b2fbbac25b6d8cbe5fc5a77105bf0d08f6a09657a84
4b3d336f85c85a94fcb7acb0b054369aa6a5ee737d571ca9fd0fcf6b0d5c79a2
a53e26c9c808a4131dd63fdd41338d4566bf261b30d787c9c484465c3a5d80f4
4c518266d77ab7f684434c84f427879b0689afccec12422ca83451292e52e19d
fd3f658d85d1cea74af4353a405c9cbd7a589441684595610a67a168318aa78eTrust 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 968333 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 4afd4bd2cbc3b5469a63aa7be47a4f2bcbcbe345059fee528340671dce171c2d; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 4afd4bd2cbc3b5469a63aa7be47a4f2bcbcbe345059fee528340671dce171c2d, and the block's
timestamp proves the page looked this way at or before that time.