FlyClient is very useful compared to SPV client, especially for blockchains with much more headers per day than Bitcoin. But fortunately, this is one of the few soft forks that we don't actually need, because we can substitute with a STARK proof as you can see here; https://github.com/starkware-bitcoin/raito ... so any energy for gathering consensus for a soft fork, before Bitcoin ossifies forever, is better spent elsewhere.
Seems pretty cool. It looks like it has similar trust assumptions as a standard light client: the light client trusts the merkle root once it is buried under several blocks of proof of work, believing that an attacker is unlikely to do all that work just to fool a light client (especially when they could have been actually mining bitcoin with all that hashrate). A nice property is that, to get started, a fly client does not have to download a variable number of block headers (namely, all of them, however many there are), only a constant number of block headers, and it's a pretty small total number. That property seems to make fly clients more efficient than standard light clients.On Wednesday, April 29, 2026 at 5:03:36 PM UTC-4 Zac Mitton wrote:Hi, Ive been looking into FlyClient first described here. I don't see any BIPs, or previous discussion in this forum about it either.On bitcoin It could allow a light-client to verify the entire work of the heaviest chain with a single ~100KB proof.It can theoretically be done as a soft-fork by injecting a single hash into the coinbase tx (similar to how segwit is committed to).What do you guy's think?