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
b0881b2f336e426cf4d44dc5a8ff6b68e93f230b6c98455b07e38457589d68ba
8e62b242ab3af536cf894197ab28e603ed2265641773a7274ad770e08044c385
1f9b1731a6cfb1a292dbd1d8a018576a75690c007108c0f3a7d04c9cfe3dc39c
e94b714bcb45e49d983cbf140aa45d9beb23cf2d1fad9310b7e34c3dcb297d95
095d01df44af8d3aeae24dfd56b4a1af7a4f0f80b2f7910c36ecc37cabbc9a5d
da0de638c2ddb53239b8284839cf0a5f233b04fa20100d7fde4c5ee47ea73b61
4439c01d8537f835a3a6d02065908150bbb936f2ad23fab06dd463e2d9ad0487
abbed16a23cdf16f7d5abf1e6f4258d3cc275adec53de1ddfc741f933c0d37d8
0dabe169cfb510697c1c66b75d95fa5c80e894128d1a2d61103116eb575e3eea
5482448d5fbb7e9a3443a0a1b14a9a40a3d9488600d7e5dd06554d075154ca3b
547d56037c757efc38f1e5d5a61d15151ad41fcf9d52f3e80bb02b48545c1bdcTrust 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 970602 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 b24b7804e60766c54787074351c938f7fdded51f22deccc50bc201ee9d6a1448; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b24b7804e60766c54787074351c938f7fdded51f22deccc50bc201ee9d6a1448, and the block's
timestamp proves the page looked this way at or before that time.