From: Gregory Maxwell <greg@xiph.org>
To: Tamas Blummer <tamas.blummer@gmail.com>
Cc: Jim Posen <jimpo@coinbase.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Interrogating a BIP157 server, BIP158 change proposal
Date: Wed, 6 Feb 2019 18:17:11 +0000 [thread overview]
Message-ID: <CAAS2fgRY-EaPMORjipJuysi-z61VUMivOKmSeO1Rv7vXOPeLKQ@mail.gmail.com> (raw)
In-Reply-To: <5A850549-B6C9-4590-BA9B-0D69BBE531F9@gmail.com>
On Wed, Feb 6, 2019 at 8:10 AM Tamas Blummer <tamas.blummer@gmail.com> wrote:
> I am skeptical that commitment of any filter will come into Core soon. [...] A committed filter makes light clients much more reliable and attractive, for some taste too much more.
You keep repeating this smear. Please stop.
If you would actually bother reading the threads where this was
discussed previously you will see that there was significant interest
from bitcoin developers to eventually commit an output filter, and a
significant investment of effort in improving the proposal to that
end. It is really disheartening to see you continue to repeat your
negative assumptions about other people's wishes when you haven't even
invested the time required to read their words.
next prev parent reply other threads:[~2019-02-06 18:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 11:41 [bitcoin-dev] Interrogating a BIP157 server, BIP158 change proposal Tamas Blummer
2019-02-04 20:18 ` Jim Posen
2019-02-04 20:59 ` Tamas Blummer
2019-02-05 1:42 ` Olaoluwa Osuntokun
2019-02-05 12:21 ` Matt Corallo
2019-02-06 0:05 ` Olaoluwa Osuntokun
2019-02-05 20:10 ` Tamas Blummer
2019-02-06 0:17 ` Olaoluwa Osuntokun
2019-02-06 8:09 ` Tamas Blummer
2019-02-06 18:17 ` Gregory Maxwell [this message]
2019-02-06 19:48 ` Tamas Blummer
[not found] ` <CAAS2fgQX_02_Uwu0hCu91N_11N4C4Scm2FbAXQ-0YibroeqMYg@mail.gmail.com>
2019-02-06 21:17 ` Tamas Blummer
2019-02-07 20:36 ` Pieter Wuille
2021-10-03 9:53 ` Dustin Dettmer
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=CAAS2fgRY-EaPMORjipJuysi-z61VUMivOKmSeO1Rv7vXOPeLKQ@mail.gmail.com \
--to=greg@xiph.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=jimpo@coinbase.com \
--cc=tamas.blummer@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