Re: [bitcoin-dev] Bitcoin Core to disable Bloom-based Filtering by default

2019-07-22 Thread Peter via bitcoin-dev
Hi, I believe two wallets. Andreas' Android Bitcoin wallet and BRD are significant users of node_bloom. Privacy is a matter of individual choice in the current protocol. Why not let people provide this network service? I don't see why it should be end-of-life if it provides value. I believe

Re: [bitcoin-dev] Bitcoin Core to disable Bloom-based Filtering by default

2019-07-22 Thread Luke Dashjr via bitcoin-dev
On Sunday 21 July 2019 22:56:33 Andreas Schildbach via bitcoin-dev wrote: > An estimated 10+ million wallets depend on that NODE_BLOOM to be > updated. Where do you see this number? I think it would be useful to chart. > So far, I haven't heard of an alternative, except reading all >

Re: [bitcoin-dev] Bitcoin Core to disable Bloom-based Filtering by default

2019-07-22 Thread Luke Dashjr via bitcoin-dev
On Monday 22 July 2019 13:25:25 Jonas Schnelli via bitcoin-dev wrote: > > I also think as long as we don't have an alternative, we should improve > > the current filtering for segwit. E.g. testing the scripts themselves > > and each scriptPubKey spent by any input against the filter would do, > >

Re: [bitcoin-dev] Bitcoin Core to disable Bloom-based Filtering by default

2019-07-22 Thread Justus Ranvier via bitcoin-dev
On 7/22/19 12:01 AM, Matt Corallo via bitcoin-dev wrote: > Finally, regarding alternatives, the filter-generation code for BIP > 157/158 has been in Bitcoin Core for some time, though the P2P serving > side of things appears to have lost any champions working on it. I > presume one of the

Re: [bitcoin-dev] Bitcoin Core to disable Bloom-based Filtering by default

2019-07-22 Thread Dustin Dettmer via bitcoin-dev
Has someone built an analysis of how much extra bandwidth CFB uses over bloom filters? Obviously an active merchant in an impoverished country paying data rates per MB will never be able to afford CFB — so those people are being cut out of Bitcoin entirely. I suppose the plan is they will rely on

Re: [bitcoin-dev] Bitcoin Core to disable Bloom-based Filtering by default

2019-07-22 Thread Tom Harding via bitcoin-dev
On 7/20/19 10:46 AM, Matt Corallo via bitcoin-dev wrote: (less trustful and privacy-violating) alternative over the coming years. The same paper that established the 'privacy-violating' conventional wisdom presented mitigations which have seen little exploration.

Re: [bitcoin-dev] Bitcoin Core to disable Bloom-based Filtering by default

2019-07-22 Thread Jonas Schnelli via bitcoin-dev
Hi Andreas >> well-known DoS vectors > > I asked many people, even some "core developers" at meetings, but nobody > ever was able to explain the DoS vector. I think this is just a myth. No. They are not a myth [1] [2] [3]. > Yes, you can set an overly blurry filter and thus cause useless

Re: [bitcoin-dev] Bitcoin Core to disable Bloom-based Filtering by default

2019-07-22 Thread Peter Todd via bitcoin-dev
On Mon, Jul 22, 2019 at 12:56:33AM +0200, Andreas Schildbach via bitcoin-dev wrote: > An estimated 10+ million wallets depend on that NODE_BLOOM to be > updated. So far, I haven't heard of an alternative, except reading all > transactions and full blocks. Can you specify exactly which wallets

Re: [bitcoin-dev] Bitcoin Core to disable Bloom-based Filtering by default

2019-07-22 Thread Matt Corallo via bitcoin-dev
Hey Andreas, I think maybe some of the comments here were misunderstood - I don't anticipate that most people will change their defaults, indeed, but given the general upgrade cycles we've seen on the network over the entire course of Bitcoin's history, there's little reason to believe that many