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
1be65ab6804a23e8746448ef1f61efe796741d5c93d57d9eb476f73b58dafeb1
435859f708196274f0c8af27dd24685abea02f958ffe2b8dd917a870f19c1bb0
cbf48a7f5ce439d3d9e3f13efd394c7bbfba75e11b43d603ebcc798702965408
9673373669cd07dc91b3251b78f90e00d1996380345a59166da5799536eb95b1
6991890a369f1de76627e116325171a570f0d4f2e4e8a1e2f0de421bd11b2346
204bf028f34bdb8177281eb73a748a5916e3fcf4e6ac7cc7f0c33f46f2c740f8
47a167443e8eea618cb111668d0fc9db0b345b61b2b9bec75b1f8af8ad7830b8
5b4edc83c5b8866b7be328c216f1a1fb01653276793aa9cc1db085380e6468c9
19eeda0f11f9980526856280264a3128972c7d5bc89333d0917d63c9566c4a7c
5d4aefc0b51ce1ce8a1c4ec67f30c3a0750339b2c24dbc5568798c90eec253ac
86dfe8e37db2fe9b382cdfcacece75b97abfed4c79f9e779175721e3eee3821c
df8154129a2b2468dd5b36e0f33782ce27c556127d8cea5b9ff478370709da5b
e02b5dd1c343179dc54a1a509ecb22732131043be32f7869a4a5bb9c3e5fede7
f4f90af7a18e3ccbeec8e9684b3d8b66e66a831794fcd5cdee5819f7d92a24faTrust 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 974404 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 a022110e2bc29b00fc15eae01fdc0e2e68ec637fee0397fd5448df52101ab840; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a022110e2bc29b00fc15eae01fdc0e2e68ec637fee0397fd5448df52101ab840, and the block's
timestamp proves the page looked this way at or before that time.