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
aa921f88d88b760ac363ebe3ce380a0e9f49c081f3ca3387106bab7b5c5f03a4
67c11f4c80b901a3f8f2c856c7be487fa4cfe06a165cc9fea39c9aadd32d21eb
471fd9c1bcfe5cbac0eb31d518433354039f15be7d18a19660fcda3b2983c113
ea010d1b2241473e41f946a209efeb8444482ab73f3d7b0ba7203b956fdecdd9
8b175871aadb441d368938babf55dc97ed457612d2506b72f671688726e86882
9668f5f15a719fa464f185b0d71f8209fe20fab5ebf5fd87274fafea217fde3d
c33deb41fb2161ecd1f9c6ed910ca3d4ca0274df8ffd0476ca7cf69b9f68f0ce
3079d21bab1c54e86286c2a691ad9cb29a7010b35b253521a8c56893651e311b
a6db8ec4c31477b681ea580873b8b72654568b18046999a345b76641948a947a
181a7d81dc9a8f4413a7c01052c6ff893d2bfe8cfce3e0561cd919c1617ea7e7
64b322417177a598ea7d374b10b6be6ac96f9f3cd0f71cdedf0ba09e5eecb5c7
da28460b6080ace38808f4b7740f25c0e770dea72ea8acc0e06e8f9f848b01fcTrust 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 974111 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 f359d1719f943a0094aaa7487e352a88ca66ef6de71b2be7c366bc02c04cf9c4; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / f359d1719f943a0094aaa7487e352a88ca66ef6de71b2be7c366bc02c04cf9c4, and the block's
timestamp proves the page looked this way at or before that time.