Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
cbcc8b0b787a133b3cc8400d87e7a129b67993bfd5b3533433d5b136bacfb2c0
28fae6382a8e06de87f803bb86d691e79f3d14ed2e6f1f1ab75be60097a7c104
c0732d65ff24ee8ecd5f4113962425782280a4b674de03dd3ba1114de052d03b
6f5a520ed2cb9e063dc63cd0851de1626551ac09158af024e7b1d177162b9177
702ce69d8ca0bdd826a3e8c72be0315bdffd449dcbb3c5e246436a1b109497b6
e9f36d4ac97d23d465c86ef305c4dafc6cb6ef02da23684731c4bd40407404c6
c31391d8afbf06e950e050cedf912315a37b3a15909e5be810009610e82a94e1
84c5fe055a2c6a78965e188533076738a831501b415a22dff2bce7131c2bc4fd
4008553a500c7c39b6bc83cd37210d16cfaf0e6f16c36bda164b112f46f5c703
0ce39ae36e797811ba928d66780b80c6485fb4c839a7938dffc50a2522e383ec
de92bd388b388e35df64a4eb1fe17acb8da3963e10f5af15564fc856abb4fb8d
34aaefad7b49dea03c356abd7e313107143bef27dba4a00fe6f3cbe35a15014f
109f33908ccc428eff8e52e067296b76cc7b42309731216f025e3aa48cd9a5ab
708df32c371bd5b1d2840155a70a1ad3a1460a583e4961f76ae75623571dce2f
710e7fd52630e8fed48d91b0b195ea8059daeaabdcf6cb22e4eb80ba2eabce27
d4a7ef582c3184669e9e45a709b70c56959de773f07f41b7fa3f7bb8ba412051
c9d88eeca45f323cbccdcab1ff830256e7498dd64e117c83e3fe69b044aeded2Trust 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 965067 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 c099fceddfa7612e2778b6f148fef285f3867e5479737121370e09fc29f1cf22; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / c099fceddfa7612e2778b6f148fef285f3867e5479737121370e09fc29f1cf22, and the block's
timestamp proves the page looked this way at or before that time.