Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 47192E91 for ; Wed, 14 Aug 2019 15:07:22 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.bluematt.me (mail.bluematt.me [69.59.18.99]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 7357587E for ; Wed, 14 Aug 2019 15:07:21 +0000 (UTC) Received: from [IPv6:2620:6e:a000:1000:6066:6448:93c9:2ea2] (unknown [IPv6:2620:6e:a000:1000:6066:6448:93c9:2ea2]) by mail.bluematt.me (Postfix) with ESMTPSA id A4B7C9988A; Wed, 14 Aug 2019 15:07:19 +0000 (UTC) Content-Type: multipart/alternative; boundary=Apple-Mail-AD753205-B2A6-4770-B13F-01C5E674E100 Mime-Version: 1.0 (1.0) From: Matt Corallo X-Mailer: iPhone Mail (16G77) In-Reply-To: Date: Wed, 14 Aug 2019 11:07:19 -0400 Content-Transfer-Encoding: 7bit Message-Id: References: <59fad2b6-9b15-ffec-116e-91d27ce29f80@mattcorallo.com> To: Will Madden X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE, MIME_QP_LONG_LINE autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Cc: Bitcoin Protocol Discussion Subject: Re: [bitcoin-dev] Bitcoin Core to disable Bloom-based Filtering by default X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Aug 2019 15:07:22 -0000 --Apple-Mail-AD753205-B2A6-4770-B13F-01C5E674E100 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable You very clearly didn't bother to read other mails in this thread. To make i= t easy for you, here's a few links: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2019-July/017147.htm= l https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2019-July/017175.htm= l Matt > On Aug 13, 2019, at 23:05, Will Madden wrote: >=20 > For the record, strong NACK. My understanding is that this breaks several e= stablished SPV implementations (such as early breadwallet for sure and possi= bly current BRD wallets) and I have yet to see quantitative prioritization o= r even a rational justification for this change. >=20 > Requiring SPV wallets to communicate with trusted nodes is centralization,= and breaking functionality and implementations that enable this without a t= horoughly researched rationale is highly suspect. >=20 >> On Jul 20, 2019, at 1:46 PM, Matt Corallo via bitcoin-dev wrote: >>=20 >> Just a quick heads-up for those watching the list who may be using it - >> in the next Bitcoin Core release bloom filter serving will be turned off >> by default. This has been a long time coming, it's been an option for >> many releases and has been a well-known DoS vector for some time. >> As other DoS vectors have slowly been closed, this has become >> increasingly an obvious low-hanging fruit. Those who are using it should >> already have long been filtering for NODE_BLOOM-signaling nodes, and I >> don't anticipate those being gone any time particularly soon. >>=20 >> See-also PR at https://github.com/bitcoin/bitcoin/pull/16152 >>=20 >> The release notes will liekly read: >>=20 >> P2P Changes >> ----------- >> - The default value for the -peerbloomfilters configuration option (and, >> thus, NODE_BLOOM support) has been changed to false. >> This resolves well-known DoS vectors in Bitcoin Core, especially for >> nodes with spinning disks. It is not anticipated that >> this will result in a significant lack of availability of >> NODE_BLOOM-enabled nodes in the coming years, however, clients >> which rely on the availability of NODE_BLOOM-supporting nodes on the >> P2P network should consider the process of migrating >> to a more modern (and less trustful and privacy-violating) alternative >> over the coming years. >>=20 >> Matt >> _______________________________________________ >> bitcoin-dev mailing list >> bitcoin-dev@lists.linuxfoundation.org >> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev --Apple-Mail-AD753205-B2A6-4770-B13F-01C5E674E100 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
You= very clearly didn't bother to read other mails in this thread. To make it e= asy for you, here's a few links:

On Aug 13, 2019, at 23:05, Will= Madden <will.madden@bridge21= .com> wrote:

= For the record, strong NACK. My understanding is that this breaks seve= ral established SPV implementations (such as early breadwallet for sure and p= ossibly current BRD wallets) and I have yet to see quantitative prioritizati= on or even a rational justification for this change.
=
Requiring SPV wallets to communicate with trusted nodes is central= ization, and breaking functionality and implementations that enable this wit= hout a thoroughly researched rationale is highly suspect.

On Jul 20, 2019, at 1:46 PM, Matt C= orallo via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:

Just a quick heads-up for those watching the list who may= be using it -
in the= next Bitcoin Core release bloom filter serving will be turned off
by default. This has been a lo= ng time coming, it's been an option for
many releases and has been a well-known DoS vector for so= me time.
As other DoS= vectors have slowly been closed, this has become
increasingly an obvious low-hanging fruit. Thos= e who are using it should
<= span>already have long been filtering for NODE_BLOOM-signaling nodes, and I<= /span>
don't anticipate thos= e being gone any time particularly soon.

S= ee-also PR at http= s://github.com/bitcoin/bitcoin/pull/16152

<= span>The release notes will liekly read:

P= 2P Changes
----------= -
- The default value= for the -peerbloomfilters configuration option (and,
thus, NODE_BLOOM support) has been changed t= o false.
This resolv= es well-known DoS vectors in Bitcoin Core, especially for
nodes with spinning disks. It is not an= ticipated that
this w= ill result in a significant lack of availability of
<= blockquote type=3D"cite">NODE_BLOOM-enabled nodes in the coming years,= however, clients
wh= ich rely on the availability of NODE_BLOOM-supporting nodes on the
P2P network should consider th= e process of migrating
to a more modern (and less trustful and privacy-violating) alternative
over the coming years.<= /span>

Matt
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfounda= tion.org/mailman/listinfo/bitcoin-dev
= --Apple-Mail-AD753205-B2A6-4770-B13F-01C5E674E100--