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
6b534c9c31262210d7ea2b8dde52473d9f7c3f53e3ba4a4090581b7ec1bca3cf
13e745d7aec634cc5e71df4c4e028596ed53b242b4bd30362e197a1ffb6cc2e7
4df21c4b22996740aa6cba73fa9e6dff5b6c10e1bfe96876048c2b6028aebf13
0e06ff83de924e7918e0be5801bec68aace6ec1eb97106e60edf2cb46bd30f2a
a1f03dcba42d6624f542c53204b34719161030b30ecc9cf59650650a072e5076
0eeaed90af556703277ec57dc86ca77ba15a1833356f1f58116e14d3ae1c2ea4
434f1e00ab5b3e795941a7ba8fc862268fd83647f591e7cdee55182eb4af3a19
939c87cd941c6fb208e6c7c857665f605d8cb0b8bc6a59c251057e518522b164
1b9520b6ff5b31169b200cbf067edf402c8f4b782fbd38bc16f026e0cf58c8e1
4a061f55cbe41cb80b27e41afa7729b93089653c75f6975d097c1255e0fff09b
1767ec421e4b6596380b27b6f279032802bc1b7aceaa2577174fc7f0d2d45cd7
5822fd44abdf0ba9c033398f039c9a849c42b80f65461d807bae1025ccecbf6eTrust 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 965451 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 2f2edf42941cd11549f17c5552d6d566e8c626320a062de56b1bf6c9e7e5416d; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 2f2edf42941cd11549f17c5552d6d566e8c626320a062de56b1bf6c9e7e5416d, and the block's
timestamp proves the page looked this way at or before that time.