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
5143ace30d7c651bbab7c12c3438954cc6264007d8825c2e2a5d59af8b0c04f4
4ef1e37337545392b20e820186584e040f1f58f13a1469517a4b061d96f0fb27
ba46b0c65a3718d722acd82332d472f5ff77973252a6dc93df9ded6fc38b5387
9fd34fded04766d8be1ba84d589a44780f0c461917653fced01d5da409996e16
188f1284960268d83497f82d5d616ad34fefd72ec5ff31cc18fe8d28b31af45b
0e794853ddc7183da4ca28d0c969cd106fbcf7def85307faf61719adc1633664
394f91543997f83449479813a26ab28121d07564eb1ce57f3051384a4e70ad8b
3edc45778bff21df957e5540b9463199e1b6a3c9953f05c114be8b7c891932fc
c4fd248412c676583c450582446818249bffcad313174cbc9589199eede0667c
9e0c9943da284d8941d39ca210e2085dac3b6afbcf4324dbab224903143d9fae
72d4a71d8d54bcd3fccaad299b46b257ae002f9e25ab20d89c5884a38f6192ee
498851cab432b340da73c74ac653efb067095aa05019184a8265416ee21e17e0
b2a0ac47c1c63cdb98c153962dcf0a7db1d47180cba94b59e8e1cd20fa1e3b82Trust 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 973822 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 17aaa59b23ec23dea39b2513bcbeae2ebb5414e61e27d90d896d3386567ae9ea; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 17aaa59b23ec23dea39b2513bcbeae2ebb5414e61e27d90d896d3386567ae9ea, and the block's
timestamp proves the page looked this way at or before that time.