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
feeeb9ea3a8550b4c6010ea7371e3f027733b4fc40a46a90b0aaf1219712a427
62209c01db16775a498663611ddcbe020add3e82c75afe36c2112f533aa8188c
e16cdc936070cf7ef3e473bfb6f79df7628dcbdf59d8d6f75fc32011a722118a
565e66f8c204b8a741e331a707b349dd1a6f52497872b2fa3142153d5dc5a595
63b66a2c978203fc9fe0de2ca516c1dd3908c35807ac58018ab2d94988ee961e
4705789fae23f9020f5cd12500bcf2e32e4cd277d57892aed147541a0c3002c9
770fd21a8d33d7d7623ec30513067f1d6dbd3f986d94bf80f2f7c3ee2b295f9c
c42ae319ce0c88cb4d867d0bead6130873c645763342b4e5dbc4a4ad0d099573
05d248e77c4cba0a104e527b1ed37a38c96ba440c4a4a1fe1546ffa56534d289
76e32e771362aac48ba38ab1d523a1aebfb11b806157d5720f42b89dbff7fbf1
a250722d63f6bc4188a3378911aec21e7d4a0f376d1aca9d2e64ba8e611ea5f3
41a0a2fbc89957c3e502e476cca7dd10512c993e47c71aa071dc8c07e7797e86
4aaaadf715c9e6983eb362f1a1a7faddd3e9c853839980a72b621c4c41201e5a
6565e9d0c67a742dc4d50db8cfdec73ccea4889d56ebc1a61d9adaf2ac5028d3
9fa6e87912d34f2b5c3e6dfafc6022f2f2bcac93374d321c8dd330df70bee3da
e0466dce5c46714c5b0d4896512dfe747279f51fda3d44d88f8834df523b35e5Trust 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 965924 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 6d179deae72591b6aeaa96ca15d12f8bd630096b611436cca01a3d31917e88dd; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 6d179deae72591b6aeaa96ca15d12f8bd630096b611436cca01a3d31917e88dd, and the block's
timestamp proves the page looked this way at or before that time.