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
e13f6e7a51b78cefa0516c76de5e2ae27ba2b93d8029a4b9be6c80e388b462af
1ff39f83de85a5f897b479ef165bcc64b90abb98812ef018848bc0e02137d387
4d0dad2be2fc0dc5f22e405ed5ade7f5dd701d51db5219d2c6d88bbb9f315895
422f74c563126b185f1808fe1c22d9a670a80e0b9631ca22dad2b10ab6fa18c5
1d0667525b193119d52900c5a5e44dfa5457cefe2a0237b9f5bb4a3762d7b13d
eab0a07d4494025b2feb1784b98d25b7f7cc6c9c4b59ed6d887a7c3b1d57936b
0f7cb91e7f3b4eae3e86b7724d4e85871fd93a0d179b63dc9230bd81dbff7e6c
b084dbf0c6b747ee73763275bbc5c264cf46701da6d1c488598764edd9820b5d
0919ce98408136bc02b84ae439dd98814806cfc1f851430c9d0763624cdae399
22cace69966ec1fb748a6a94abefb6952369b25daab2bada7f9244bb3b662026
b22909a5131c66cbd47300dd736492557454fd08d317df42df014d0f6cc46f32
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 33fad404f561361165ff8d0d0dc1c5ee1ab677c867d7598b4edf28330f00f52e; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 33fad404f561361165ff8d0d0dc1c5ee1ab677c867d7598b4edf28330f00f52e, and the block's
timestamp proves the page looked this way at or before that time.