From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Thu, 30 Apr 2026 11:55:11 -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 1wIWXX-0005aX-If for bitcoindev@gnusha.org; Thu, 30 Apr 2026 11:55:11 -0700 Received: by mail-oa1-f55.google.com with SMTP id 586e51a60fabf-43013bffd49sf5349359fac.0 for ; Thu, 30 Apr 2026 11:55:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20251104; t=1777575305; x=1778180105; 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=5N00olWT0njyjtJ+FlXt0VNeO+bVkNM4EezgwAiVw9w=; b=XnjFbimyfCAMmtDT279HlXuixkxSsmaI4tJPB5BRwtZer3pYlmlXF90ejaDN3MZfqs StjDMV5fPh5ZZZ6fIUxX4V8l/iiCquqQW2vprphFIEpJuSZLyp6EspBID0MdWeEnJ6Io G3Y4YWHiGZ7ltHYBmfhfTiGBl2Mbxlpx8CKSSanSCs9s371zR4JhcpBztZmF24qw3Ip2 xdm1qBnWtuOzcC/UDgdtpd+d2VZtf2gvcPjSbPTSpgMplamCugCCmkruiexylebhbMwI t807il9gW/Zu3PcKnOdJxcQBsCWWlZZnOzxpNWzkfONhcCP9t8tciiCTY97sRRQZ4ddG Q/Hg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20251104; t=1777575305; x=1778180105; 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=5N00olWT0njyjtJ+FlXt0VNeO+bVkNM4EezgwAiVw9w=; b=BdbIYk+CdeqzMYcdKnPZMmcGbuFHD0uyIXEFoZArWmsxWDniehU+YlQINRH+yio1DA q8r6DPoPYgrvd9PTwKEt6a8qb1neU/nvjtl5IYFb7qRHF6e1BzuzkzdWIK1cayYOcWHq +OFl/Y3oP6Int/1M4236owSacq64Bg/vZchlWuD/l4UufjoQCgnJy5RS92bfQxrD9YbK 3EqSvVL/6jJXDIhwDA19BtYTjbd47Q0C5WCxXjfpk0srQOKE7aLv2JmvzU/3F8Txd2vY kD0P1cThRNLD6tBT85gt2F0zeca6gCWUG75V2nJPeuoeOkU9CbFaGmhHYvp+VSFCYzUD xkIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1777575305; x=1778180105; 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=5N00olWT0njyjtJ+FlXt0VNeO+bVkNM4EezgwAiVw9w=; b=m03SpcSS85SAiYdWuUfajnwZm2OmlvvI2nH037dOV2EiKso69F3/FVWI9808flpt6Z ynCZwz16XRATJYVYBi4PwnKd1/XCd0ok1fxYcoa7vr8PbFfmJcLuaABbvMXqngjCsYpp svMVD/+ozghfO+Oo7mBV+3vK2gM+7lxDf59zYN7uP13zOfXYUVZ4X7KX8Cpq/tJVDG1n AnmZZA1qGHnMVA+LYb+4eUVq6kgJtXvnMev5AI7BkTyP8zQ2PYk6XPDj47cQ1RjOEU70 4OGHKNrdf1qSU3TEpa4xBBh+QMp4QvWZPXxxd+hjOFMI7dlGFENo4EacR0hEVEhhwuFH I3+A== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AFNElJ/Pvtl6aoE6YZZVIEQ6KjIj/054694MYOZoPPSaa97ruZ9s7r54Kk3bqZYYRfkelg5sOroYkH1fKnHe@gnusha.org X-Gm-Message-State: AOJu0Yx/VZuCXvffskpq3fqo2Y4zDwegeFHom2aJqlkFCLALG2URx3Qf BedKXN3pdib8g+mwX5HISSE5W0vWHC4KTSHCbGseeShDCs+g5xlNgZq/ X-Received: by 2002:a05:6870:d0ce:b0:41c:af81:2e7f with SMTP id 586e51a60fabf-43438bdf529mr1709703fac.20.1777575305031; Thu, 30 Apr 2026 11:55:05 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h="AUV6zMNSMHS/ZfvUMSD/G5Az9AgVp4VDbQ37J4Ta4gKP8a01Bw==" Received: by 2002:a05:6870:3b89:b0:430:279e:462b with SMTP id 586e51a60fabf-4342f16e36als651975fac.0.-pod-prod-06-us; Thu, 30 Apr 2026 11:55:00 -0700 (PDT) X-Received: by 2002:a05:6808:e8c3:20b0:47c:6cc8:a798 with SMTP id 5614622812f47-47c6cc8a8d4mr801884b6e.41.1777575300011; Thu, 30 Apr 2026 11:55:00 -0700 (PDT) Received: by 2002:a05:690c:a1c9:b0:7ba:f5aa:4ab8 with SMTP id 00721157ae682-7bd65c2dbc2ms7b3; Thu, 30 Apr 2026 11:52:52 -0700 (PDT) X-Received: by 2002:a05:690c:60c7:b0:7b1:d1af:4ba6 with SMTP id 00721157ae682-7bd52ad47e0mr46579077b3.43.1777575172061; Thu, 30 Apr 2026 11:52:52 -0700 (PDT) Date: Thu, 30 Apr 2026 11:52:51 -0700 (PDT) From: Super Testnet To: Bitcoin Development Mailing List Message-Id: <1283ada3-6231-4e18-b8a3-056a8f142babn@googlegroups.com> In-Reply-To: References: Subject: [bitcoindev] Re: Fly Client Proposal MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_9000_118362370.1777575171597" X-Original-Sender: supertestnet@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_9000_118362370.1777575171597 Content-Type: multipart/alternative; boundary="----=_Part_9001_369593094.1777575171597" ------=_Part_9001_369593094.1777575171597 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 pretty= =20 small total number. That property seems to make fly clients more efficient= =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 an= y=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 the= =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/= 1283ada3-6231-4e18-b8a3-056a8f142babn%40googlegroups.com. ------=_Part_9001_369593094.1777575171597 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Seems pretty cool. It looks like it has similar trust assumptions as a stan= dard light client: the light client trusts the merkle root once it is burie= d under several blocks of proof of work, believing that an attacker is unli= kely 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 pro= perty is that, to get started, a fly client does not have to download a var= iable 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 nu= mber. That property seems to make fly clients more efficient than standard = light clients.

On Wednesday, April 29, 2026 at 5:03:36=E2=80=AFPM UTC-4 Z= ac Mitton wrote:
Hi, Ive been looking into FlyClient first described here. I don't see any BIPs, or previous discussion in this forum a= bout 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 inj= ecting a single hash into the coinbase tx (similar to how segwit is committ= ed to).=C2=A0

What do you 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/1283ada3-6231-4e18-b8a3-056a8f142babn%40googlegroups.com.
------=_Part_9001_369593094.1777575171597-- ------=_Part_9000_118362370.1777575171597--