Unnamed repository; edit this file 'description' to name the repository.
 help / color / mirror / Atom feed
From: Zac Mitton <zacmitton22@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] Fly Client Proposal
Date: Wed, 29 Apr 2026 14:00:32 -0700 (PDT)	[thread overview]
Message-ID: <edb5d954-37f6-4b57-a3ce-70d92d6a9407n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 849 bytes --]

Hi, Ive been looking into FlyClient first described here 
<https://www.youtube.com/watch?v=BPNs9EVxWrA&t=8386s>. 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?

-- 
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 email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/edb5d954-37f6-4b57-a3ce-70d92d6a9407n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 1209 bytes --]

             reply	other threads:[~2026-04-29 21:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-29 21:00 Zac Mitton [this message]
2026-04-30 18:52 ` [bitcoindev] Re: Fly Client Proposal Super Testnet
2026-05-01  8:42   ` Nuh.dev
2026-05-02 19:23     ` Zac Mitton
2026-05-02 21:24       ` Nuh.dev
2026-05-03 16:56 ` Tom Harding
     [not found]   ` <CAOsDwYbfZXKe_dcNoL_t2DSrWokUXC2OJh33J8=CDHmO=n3AhA@mail.gmail.com>
2026-05-04 16:26     ` Tom Harding
2026-05-04 22:34       ` Zac Mitton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=edb5d954-37f6-4b57-a3ce-70d92d6a9407n@googlegroups.com \
    --to=zacmitton22@gmail.com \
    --cc=bitcoindev@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox