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
3d6477d6338046597bd92321a553ea0f034355908a49021d56aaeda762fc513e
c8ee5ed65de404d96b2bfc792afae38543f40761403ad4f6b9c821b43f657b71
e444973c592ff985f10d49f2245deea7626a7d9156e0eb8d7b1012747e2516c3
ab0528d5d4499c32664ef5f1d05da867ab21d00ed0d68d5073b451c3630a5f98
af8171b316cca2883c34bbcf56c24628e6d786619f0bb42968c61e2ca44feaed
8ba50f80b8c13454097649407abdec46870776f72bcab96a5d7525de806acff0
fa0c7c5d6b256ac0934f783f962ab2e281c0b254f14ee1710651f7efc015d5e4
069b0a9ce51faa81d7a01f982c3585c53a6c107f0a2822ba4867a6eeebff8cfa
5e56dbde6ebe1660123ee0d34f8b168baad911d58e3f2e9a7d761c81636f2271
418a0107b15f84f6dd930c32f9a73e115ff67dd877638333412116a1914543f5
45e31b003c9239f3e6b3f2dacd4a5f5d3fa91e335ef1e366bbcf992f43af8fb4
c73a945c822df18ba2c946e0d65efec61c9cac19525c5c840313db915b34b37e
4e3a9fdedef772a7060517b7d6391523687097e88989437e7e724b1f991119f7
90c7f13ad2d71b0f96d142351780c08a9c09cf48609ae0c6f430d713509221b2
5544f92448886f52825b0a8702bb2e266dd0c5b7eeb18dca470edb18959a8cfa
6ffadaf424c23398c9402ddce133be2361866d92e15b1376f8f9d2b79599013b
ee7d166427e2ae449552e06d86057395a99ed1f529ec9df315c010852cf07b18
36fc96e5cf58792e728557588ad25f76e4c91feda03ed7a94c19e18f671de866Trust 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 972523 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 814bb674af2d31be0b7c48ee0b3090778baa7db0a8aca16048a863e03855ecc5; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 814bb674af2d31be0b7c48ee0b3090778baa7db0a8aca16048a863e03855ecc5, and the block's
timestamp proves the page looked this way at or before that time.