Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
30a4a66094539f3b35a7c3a5bf5ec8c93f3160924eaf667ded758ad5a43f02f4
c98d0013e65f5d6e93d21805ac019a745d4c81d1a459d10cc75caf081a7d0f44
c87d6b5c2930d89950a7be6c46260209cead30a3ba57875da628860ea1aaac6e
ecbe09898b3809d7628daa2bfd00af5a24d5ffe193cdf7cf8100568124f31c3a
8bc82d3a387a8f89111b649bf70683e95de76c710f18d91c5da6dac66ca47ac4
ab457b053dc9372ab062f8eb2691708e5af3814aef0d1591d58437c0906b7aa7
f116dac309627cad2b19ae712b4ac949ada523b4694f8dcea3536f92afa37acd
3629da03d34b6d2d3312541b77b25ab026e13bf818efc7720ec8fde3b4fa166b
4f02756d1e589b21013fcf01419167df96b02133046e89f7d4a9bb117dca80b3
0792c04e11b4d477f4923bc3156f78fe1bcb96f2f892a79acd14a19ac1809862
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 00c3e93b143c7ffbccc0ec4e3310f5b7dd5c04e26f1d7a0d7993eacbbbe3c66b; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 00c3e93b143c7ffbccc0ec4e3310f5b7dd5c04e26f1d7a0d7993eacbbbe3c66b, and the block's
timestamp proves the page looked this way at or before that time.