Timechain
Search Donate
Sponsors
Cake Wallet, private Bitcoin and Monero walletSideShift.ai, no-signup crypto exchangeOrangeRock, non-custodial bitcoin spot and perps tradingBraiins Hashpower, buy and sell Bitcoin hashrateLayer Two Labs, drivechains for Bitcoin
BIP 37

Connection Bloom filtering

Deployed In Bitcoin Core Peer Services Specification Assigned 2012-10-24

Bloom filters for light wallets: a phone wallet asks a node only for transactions matching a filter. Disabled by default in Bitcoin Core since v0.19.

Plain-English summary by Bitcoin Takeover, based on the BIP text.
From the BIP’s abstract

This BIP adds new support to the peer-to-peer protocol that allows peers to reduce the amount of transaction data they are sent. Peers have the option of setting filters on each connection they make after the version handshake has completed. A filter is defined as a Bloom filter on data derived from transactions. A Bloom filter is a probabilistic data structure which allows for testing set membership - they can have false positives but not false negatives. This document will not go into the details of how Bloom filters work and the reader is referred to Wikipedia for an introduction to the topic.

Read BIP 37 on GitHubFind in explorer

In Bitcoin Core

The bloom filtering for transaction relaying, partial Merkle trees for blocks, and the protocol version bump to 70001 (enabling low-bandwidth SPV clients) has been implemented since v0.8.0. Disabled by default since v0.19.0, can be enabled by the -peerbloomfilters option.

Drama

Bloom filters (BIP 37) switched off by default — It decided whether ordinary nodes keep serving phone wallets, which pitted node resources against light-client independence. One commenter called it sabotage.

0:000:00