From: Yuval Kogman <nothingmuch@woobling.org>
To: Keagan McClelland <keagan.mcclelland@gmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A design for Probabilistic Partial Pruning
Date: Sat, 27 Feb 2021 22:13:29 +0000 [thread overview]
Message-ID: <CAAQdECAgd3XQpLGi6X1eshW6hT+Bt8p41q6j775QBBqeqL4xjQ@mail.gmail.com> (raw)
In-Reply-To: <CAAQdECD=G_UV+GBB7365iVdvLduRYcFe_G1i_eZCbLqCVpaO5w@mail.gmail.com>
On Sat, 27 Feb 2021 at 22:09, Yuval Kogman <nothingmuch@woobling.org> wrote:
> and there is work on fountain codes. There is also some work on
apologies, the first half of this line should have been deleted as it
was worked into the next sentence.
prev parent reply other threads:[~2021-02-27 22:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 18:40 [bitcoin-dev] A design for Probabilistic Partial Pruning Keagan McClelland
2021-02-27 7:10 ` Igor Cota
2021-02-28 3:41 ` Leo Wandersleb
2021-03-01 6:22 ` Craig Raw
2021-03-01 9:37 ` eric
2021-03-01 20:55 ` Keagan McClelland
2021-02-27 19:19 ` David A. Harding
2021-02-27 23:37 ` David A. Harding
2021-02-27 22:09 ` Yuval Kogman
2021-02-27 22:13 ` Yuval Kogman [this message]
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=CAAQdECAgd3XQpLGi6X1eshW6hT+Bt8p41q6j775QBBqeqL4xjQ@mail.gmail.com \
--to=nothingmuch@woobling.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=keagan.mcclelland@gmail.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