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
e8ff4fb55bfbe2182f6845b0112e140706b78bc457d2d10a00be46ece716c0d5
0a852c1eb21e008de6bcbfc3f1df15ebcd92d013dd92d6494f3679a6e350b15d
b4ba6cdeaff72cdfe5e7736f5a8aea84daa4592ddf29c2de9a50e8b878e51cde
4c88df009a23ac2f86f8ae9949bbd1dca105675dd6d8b317720dd22791043148
c07abea449fc89945e09e162f5a2339ca53d04310efbb63cf893a45374c2fc82
db391dd68164cb13ea966a26c45fbcae82f8da6216e4b292f73793635a5c47de
a67eff07909dd403c050dc11f45ef3133adf66f89882a0d2fbc5952333eb2b43
d876d6c13d61ff7cc4adb9e0cb4fb0c6949718746340f9bbead7009a63a497a5
c10d7d976b214bf8ce43f9072dd2589e6aa1aff2c7eb9cc823841fb03ab00d8b
ac2eed893d3d6445aa48722924f9b1ac6b5ba8a196a66aa8f75764bb2857f249
7926a9152d75f1fd99b364f8d74e87650d48a34d2416f67be70e14ca0a4da3d3
34dcb1a402311815842b33069606cd985112dd2413e6b3139c168bec5e14f5dd
463023df8059fcae136202f026944d3979ff0697425f7ccc7c1798af80d26b27
de7af68ff188ce20a3725ee34d50a26582423b2589de4f0b5383728eccd701d7
01f8eabc60c9e6d0a7c4fa0acb149c9cd3cd9cf7569fe4a8ab0df07312273978
87aa01e8ecbb2d8df2a0deb8c8eef5cf4bdb94c8a0f45ceac70b1af1112a8b0bTrust 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 962900 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 3f669765b7b25c97e789077d54565c80b3ddeac869ffc290a44aa361c92b6908; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 3f669765b7b25c97e789077d54565c80b3ddeac869ffc290a44aa361c92b6908, and the block's
timestamp proves the page looked this way at or before that time.