A compact home server with storage, Ethernet and a laptop at a coastal workspace, editorial illustration
BIP 157 / NETWORK

Let a light wallet check locally.

Client-side block filtering lets a wallet download compact filters and decide locally which blocks may interest it.

Read the explanation
← All standards

Why it exists

BIP 157 lets a lightweight wallet decide locally which blocks may concern it. Instead of sending its own address filter to a server, it downloads compact filters created from blocks and checks them on the device. This improves a specific part of the wallet’s privacy model.

How it works

The protocol defines messages for requesting filter checkpoints, headers and filters. A chain of filter headers commits each filter to its predecessor. A wallet can compare responses from multiple peers and investigate disagreements by fetching the associated block and reconstructing the filter.

After checking a filter against scripts it is watching, the wallet retrieves matching blocks and examines their real transactions. BIP 158 defines the filter contents and compression; BIP 157 defines how peers deliver them. The filter-header chain is not itself a consensus commitment in Bitcoin block headers.

PUT IT IN CONTEXT

A practical example

A mobile wallet following 100 receiving scripts downloads the same filters as other clients. It tests its scripts locally and requests a full block when one matches. The server has not received that list of 100 scripts, although the pattern of requested blocks can still reveal interests.

What to keep in mind

An isolated wallet can be misled by dishonest peers. Block requests and IP addresses also leak information unless the client mitigates them. Matching a filter does not replace checking transactions, and a lightweight client still does not perform all validation done by a full node.

Status & implementation

BIP 157 is Deployed. Bitcoin Core 0.21.0 added serving compact filters over the peer-to-peer network when configured with the block-filter index and serving option. Availability therefore depends on peer configuration, not just software version.

Specification status: Deployed · Sources checked 13 November 2026

Read the sources

Put the standard in context.

Explore the practical guide

Find your next answer.

Search the complete field guide · Esc to close