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
fc0747f846de51440de00e86dfde99ffa43598f6ccd9f6024aa6be94f91ced7f
35332c677dd1d176819bc1c5c670aab20fdbb2c18b3f124e758370bc08728287
b76e9196ee48ddc81a4d37c91c58d114e4ba82f4a93303ca47a7d32b474aa8aa
8ff46378a2e369ab92f6ae3c941498fcac7490eb36b2ad5713010790cd385be7
78a13815fb0167565f312403b0e1ee088618d12bc3a9aa60674711afa23a7594
545c94503ae69fb8e26c6a2e55a53e85e14a582897b09ddb7475c83502d94156
3f2336660969565bd10c115c6e5cabdc37923037a606c5be2f648df464c28a3f
c8c10275f887257c176a01efc8c144c940971c874f429224a7614a61944fc241
e9f40d4beb1bfd79a2b4a336bc7bc3853f137f5e9449e2e6bcf0dea973cea068
1b365e2f04a6d01c9b57d846d11723087954094ba2f6058aa18584f3d92bb778
cc125cc1f85f5d7224ab3a25a99e01578cf78a2c37d1699ff750d392f944c2e5
2c4e1db712343d97c15c3b7ff9ac2653302a42ed1fd062ac50d8b57155f56dce
ef211415107232a24a3d941dddbfa1bb4b2d3d72b422b113e5ac600d0549bafa
76422ff4ea179e9778284380941a6b38e612efb63a440a6005acd7895211bca3
6174f7a7ef95aed1b37773d64bc9185be4627aa9798e62b6599dd658f97ae40a
bd747a4a53240db39270fc789e1fe6ef81a40e7793b22ca9027a0128f96900b2Trust 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 965137 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 325987e98dea1a9f9cd4bf37f599d2829abe2ae39e6f271d2db648f013be0113; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 325987e98dea1a9f9cd4bf37f599d2829abe2ae39e6f271d2db648f013be0113, and the block's
timestamp proves the page looked this way at or before that time.