← GlossaryCoins & networks
What Is a Bloom Filter? How Light Wallets Filter Transactions
A Bloom filter is a compact probabilistic data structure for testing whether an item is in a set, which can give false positives but never false negatives, and which BIP-37 used to let light clients request only relevant transactions.
Key takeaways
- It answers 'possibly in the set' or 'definitely not in the set'.
- False positives are possible; false negatives are not.
- BIP-37 let light wallets set a filter so peers send only matching transactions.
- A higher false-positive rate improves privacy but uses more bandwidth.
What it is
A Bloom filter is a space-efficient way to test whether an element belongs to a set. It uses a bit array and several hash functions. Adding an item sets certain bits; checking an item looks at those bits. If any is unset, the item is definitely not in the set. If all are set, the item is probably in it. So the filter can wrongly say yes, a false positive, but it never wrongly says no.
Why Bitcoin used it
Light clients do not want to download every transaction. BIP-37 added a way for a client to send a Bloom filter built from its addresses and keys to a peer. The peer then forwards only transactions that match. The BIP explains the motivation: SPV clients otherwise download the full contents of blocks and all broadcast transactions, only to discard most of them, which wastes bandwidth and memory, especially on metered phones.
The privacy trade-off
The BIP's design rationale points out that because filters are probabilistic, the client chooses the false-positive rate. A high rate means the peer cannot tell which transactions are really yours, but the client receives more data. A low rate saves bandwidth but lets the peer correlate transactions with your wallet and IP address. In practice, researchers found the privacy protection weak, and many modern wallets and nodes use other approaches.
What it means for users
You will not configure a Bloom filter yourself. It matters because it shows how light wallets balance bandwidth against privacy, and why using a wallet that queries third-party servers or nodes always reveals something about your addresses. If privacy matters to you, run your own node or use wallets with stronger privacy designs.
Example
A light wallet builds a filter from its 100 addresses with a 1% false-positive rate. The peer sends it all matching transactions plus about 1% extra unrelated ones, so the wallet gets what it needs without downloading every transaction.
Put it into practice
Treat wallet queries as visible
Any wallet that asks a server about your addresses reveals some of your activity. Use Scrypt Wallet with that in mind and keep large balances behind careful habits.
Create a free wallet Get Scrypt for AndroidSources and verification
Last reviewed 2026-10-02 by the Scrypt Wallet team. The factual claims on this page, and where each comes from:
- BIP-37 lets peers set a Bloom filter on a connection to reduce the transaction data they are sent. [1]
- A Bloom filter can have false positives but not false negatives. [1] [2]
- The BIP notes the client chooses the false-positive rate, trading privacy against bandwidth. [1]
Sources
- BIP-37: Connection Bloom filtering · bitcoin/bips on GitHub · primary source
- Bloom filter · Wikipedia · secondary source
Primary sources are protocol papers, specifications, source code or a project's own documentation; secondary sources are wikis and explainers. We checked each claim against the source text on the review date. Found an error? Tell us and we will correct it.
Frequently asked questions
Can a Bloom filter miss my transactions?
No. It has no false negatives, so everything that matches is sent.
Is it private?
Only partly. A low false-positive rate leaks which transactions belong to you.
Is BIP-37 still used?
Support has declined in many nodes because of privacy and load concerns, so check each wallet and server.
Written by the Scrypt Wallet team · Updated 2026-10-02. General education, not financial, tax or legal advice.