From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id AD5FDFDA for ; Sat, 20 Jul 2019 17:46:57 +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 37A39E6 for ; Sat, 20 Jul 2019 17:46:57 +0000 (UTC) Received: from [IPv6:2620:6e:a000:233::100] (unknown [IPv6:2620:6e:a000:233::100]) by mail.bluematt.me (Postfix) with ESMTPSA id 468A6185C6E for ; Sat, 20 Jul 2019 17:46:55 +0000 (UTC) From: Matt Corallo To: Bitcoin Protocol Discussion Openpgp: preference=signencrypt Message-ID: <59fad2b6-9b15-ffec-116e-91d27ce29f80@mattcorallo.com> Date: Sat, 20 Jul 2019 17:46:52 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Sun, 21 Jul 2019 12:00:04 +0000 Subject: [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: Sat, 20 Jul 2019 17:46:57 -0000 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. See-also PR at https://github.com/bitcoin/bitcoin/pull/16152 The release notes will liekly read: 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. Matt