From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Fri, 01 May 2026 02:03:54 -0700 Received: from mail-oa1-f55.google.com ([209.85.160.55]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1wIjmr-0001d7-FD for bitcoindev@gnusha.org; Fri, 01 May 2026 02:03:53 -0700 Received: by mail-oa1-f55.google.com with SMTP id 586e51a60fabf-42c07b2f12asf2386532fac.3 for ; Fri, 01 May 2026 02:03:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1777626227; x=1778231027; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:sender:from :to:cc:subject:date:message-id:reply-to; bh=oBkD49HL05xWZqgBaS4BRnp0Jwlg1+xC5W5IzDwwUGw=; b=StMn1MI203yGDkvIeWaDtouXYgqovXfnw7wDt99YuJW6Rrtrktq1JRxVCXtgVM2goG pFb5vFSQFThN3P28yNdp2PpPdXQAKpLx7YLBlG6dCtEAQREcQAGSIUuH0D7UdfoqsFj4 qlei8jocZjFlff/EI0YxnT76NTWVUsMziodGCsLHgj3Cc+X8+ysnWm/NjtaIINcaXIQA 6iacYVrB/DylIy3IVYOsUQFPJmWbOBinjDBlO0ieQ9zDE333qIXCR6itMPCVvun/KH5C J8KH/0CXOy0eBKQomFbcYOtIwCYlwMUYoPBhS/sCuIere5IKQVjrT1GgjPpnZk2h8b9n oOiw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1777626227; x=1778231027; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:from:to:cc :subject:date:message-id:reply-to; bh=oBkD49HL05xWZqgBaS4BRnp0Jwlg1+xC5W5IzDwwUGw=; b=RcnQFUwX1N8dBwlgEppSUZ1uHPQ3sS91PwM+kvBOx7VEcBIqsOnXrfrdy+m3ZcEO6J /V/JfxFl71byS4bYInoji74LqCqojA+YsalKKYESEo3b9hOduvxrtJ90/g16mU8aoj1u Fb9m0sIrQcRjm34gJwHt8gvvopGMaptGfmopcq1eTd5WbqIX0bfwHQz4AiBJu4Q6fLUc 3p4aWq9Ibxcqbp/M/SknqWKqANt63BMtNLz/1ZHJ+Xp/wxp517err3rcFVbz7eT2zOxm 7NMs4vlnJCK1hUErs4GHyWo+86JMOkT7o84L3c3pmS7X+Etk/avmwnpsMqqWgPKMvuez p/VA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1777626227; x=1778231027; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:references:in-reply-to:message-id:to:from:date:x-beenthere :x-gm-message-state:sender:from:to:cc:subject:date:message-id :reply-to; bh=oBkD49HL05xWZqgBaS4BRnp0Jwlg1+xC5W5IzDwwUGw=; b=O+35BmpS5zJrRqGzp+siC7OYl86k319i5ILy+mlwFEu8Vf6dLKD3iKerPDzBAadif9 p+G+QVFdaHkivd9/hLpQN/yoZumn2jMLehWO4j2fELQOy0+KdsJyGQOjYt/lTwcpRQbf hAjZN006+bo98wIYgr/+yFhJWdYBP52nzYTibjI651ot/WpS8CVOWp0ASRX4w4zQe3D/ WHVbvzko9DLGe0ow31rwPQX5j58Lgg14yk1EXV4K5KnYo8+z8/UMyymDlPn4FdooIwUw j/KcNiEkApX0Q26PLp5HrIzEUhukT8FnyIL/IsqJuHSFqoa5kspUpCDEU2happ2epuJL 7Zwg== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AFNElJ+8AUojAd/Ut0Y/HAJQCwpNBzp36JIkL/yQ0ABQqVFTrGiUa1fTaE9vZV7sYqyUmLfx5jj0UaTjBmur@gnusha.org X-Gm-Message-State: AOJu0YzZedGfx6LHFsecFqZCIjgpUAqB+x585wO7pbVk4kRLvhSOtgJo B88yajgcN7nqiO0ih/7PHKhNmY+5vAWr3jV93XXwQU6yeE5ckabgE7UQ X-Received: by 2002:a05:6871:6c09:b0:417:369f:4dee with SMTP id 586e51a60fabf-4343403ff44mr3736410fac.31.1777626226873; Fri, 01 May 2026 02:03:46 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="AUV6zMPdsQPHiDXH9bREqzMIH7k1HYyy8i/9BGZNXqyja1i++g==" Received: by 2002:a05:6871:3a2a:b0:423:2c4e:f14b with SMTP id 586e51a60fabf-4342f9ee4b3ls1362607fac.1.-pod-prod-01-us; Fri, 01 May 2026 02:03:42 -0700 (PDT) X-Received: by 2002:a05:6808:150b:b0:467:da0d:5395 with SMTP id 5614622812f47-47c60fa7afemr3248955b6e.41.1777626222623; Fri, 01 May 2026 02:03:42 -0700 (PDT) Received: by 2002:a05:690c:c3e2:b0:7ba:f1b3:9504 with SMTP id 00721157ae682-7bd6653f53cms7b3; Fri, 1 May 2026 01:42:46 -0700 (PDT) X-Received: by 2002:a05:690c:c4e9:b0:79c:c51c:7f4a with SMTP id 00721157ae682-7bd54a1f9e2mr59155157b3.46.1777624966027; Fri, 01 May 2026 01:42:46 -0700 (PDT) Date: Fri, 1 May 2026 01:42:45 -0700 (PDT) From: "Nuh.dev" To: Bitcoin Development Mailing List Message-Id: <69c7bb7f-5bf5-40f1-a2fd-a985ec88ddd7n@googlegroups.com> In-Reply-To: <1283ada3-6231-4e18-b8a3-056a8f142babn@googlegroups.com> References: <1283ada3-6231-4e18-b8a3-056a8f142babn@googlegroups.com> Subject: [bitcoindev] Re: Fly Client Proposal MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_109860_1542267379.1777624965414" X-Original-Sender: Ar.Nazeh@gmail.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) ------=_Part_109860_1542267379.1777624965414 Content-Type: multipart/alternative; boundary="----=_Part_109861_1034584589.1777624965414" ------=_Part_109861_1034584589.1777624965414 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable FlyClient is very useful compared to SPV client, especially for blockchains= =20 with much more headers per day than Bitcoin. But fortunately, this is one= =20 of the few soft forks that we don't actually need, because we can=20 substitute with a STARK proof as you can see here;=20 https://github.com/starkware-bitcoin/raito ... so any energy for gathering= =20 consensus for a soft fork, before Bitcoin ossifies forever, is better spent= =20 elsewhere. On Thursday, 30 April 2026 at 21:55:05 UTC+3 Super Testnet wrote: > Seems pretty cool. It looks like it has similar trust assumptions as a=20 > standard light client: the light client trusts the merkle root once it is= =20 > buried under several blocks of proof of work, believing that an attacker = is=20 > unlikely to do all that work just to fool a light client (especially when= =20 > they could have been actually mining bitcoin with all that hashrate). A= =20 > nice property is that, to get started, a fly client does not have to=20 > download a variable number of block headers (namely, all of them, however= =20 > many there are), only a constant number of block headers, and it's a pret= ty=20 > small total number. That property seems to make fly clients more efficien= t=20 > than standard light clients. > > On Wednesday, April 29, 2026 at 5:03:36=E2=80=AFPM UTC-4 Zac Mitton wrote= : > >> Hi, Ive been looking into FlyClient first described here=20 >> . I don't see a= ny=20 >> BIPs, or previous discussion in this forum about it either. >> >> On bitcoin It could allow a light-client to verify the entire work of th= e=20 >> heaviest chain with a single ~100KB proof. >> >> It can theoretically be done as a soft-fork by injecting a single hash= =20 >> into the coinbase tx (similar to how segwit is committed to).=20 >> >> What do you guy's think? >> > --=20 You received this message because you are subscribed to the Google Groups "= Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/= 69c7bb7f-5bf5-40f1-a2fd-a985ec88ddd7n%40googlegroups.com. ------=_Part_109861_1034584589.1777624965414 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 substitut= e with a STARK proof as you can see here; https://github.com/starkware-bitc= oin/raito ... so any energy for gathering consensus for a soft fork, before= Bitcoin ossifies forever, is better spent elsewhere.

On Thursday, 30 Apr= il 2026 at 21:55:05 UTC+3 Super Testnet wrote:
Seems pretty cool. It looks like it has = similar trust assumptions as a standard light client: the light client trus= ts 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 cli= ent does not have to download a variable number of block headers (namely, a= ll of them, however many there are), only a constant number of block header= s, and it's a pretty small total number. That property seems to make fl= y clients more efficient than standard light clients.

On Wednesday, April 29,= 2026 at 5:03:36=E2=80=AFPM UTC-4 Zac Mitton wrote:
Hi, Ive been looking into FlyClient first des= cribed 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 (simil= ar to how segwit is committed to).=C2=A0

What do y= ou guy's think?

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoind= ev/69c7bb7f-5bf5-40f1-a2fd-a985ec88ddd7n%40googlegroups.com.
------=_Part_109861_1034584589.1777624965414-- ------=_Part_109860_1542267379.1777624965414--