BIP 37 (2012) let light wallets ask full nodes for matching transactions using bloom filters. In 2019 Matt Corallo proposed turning that service off by default in Bitcoin Core.
Switch it off · Matt Corallo and most reviewers
BIP 37 filtering is a known denial-of-service target and leaks privacy. Older nodes would keep serving it for years, and newer wallets were expected to move on.
Light-wallet users and developers
Bloom filters were how light wallets worked without trusting a central server. Nicolas Dorier wanted them kept at least for peers you whitelist on your own node.
It decided whether ordinary nodes keep serving phone wallets, which pitted node resources against light-client independence. One commenter called it sabotage.
Merged for Bitcoin Core 0.19.0: peerbloomfilters now defaults to false, but operators can switch it back on. In the thread, compact block filters (BIP 157) were raised as the alternative.
- 2012BIP 37 is proposed. [1]
- Jun 2019PR #16152 opened; NACKs and ACKs follow. [1]
- 2019Bitcoin Core 0.19.0 ships with bloom filtering off by default. [1]
“BIP 37 bloom filters have been well-known to be a significant DoS target for some time.”
GitHub, PR #16152 · Jun 2019 · source
“bloom filter should always be enabled for white listed peers, as this is the most effective way to sync a lightweight client from your own full node without the need of additional middleware like electrum.”
GitHub, PR #16152 · Jun 2019 · source
“It won't break. People will continue to use old versions for years into the future.”
GitHub, PR #16152 · Jul 2019 · source
“Bloom filters are the way that lightweight wallets operate without centralized servers. There is no evidence of a significant DoS issue. This is a clear effort to sabotage Bitcoin.”
GitHub, PR #16152 · Jul 2019 · source