Client Side Block Filtering

The five-minute read

One action, walked through

1. Open BIP 157 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: A new light client protocol in Bitcoin that improves upon currently available options.
3. Name the object that changes: P2P.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing BIP 157 at the status the text itself states: Deployed.
• The object that has to change is P2P. A neighbouring document with a similar name is not this one.
• Constants in the text can be superseded by a later fork. Cite the EIP number and the fork you mean.

What happened after the paper

The source marks this deployed. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What does Client Side Block Filtering charge, reject, or redefine on the first touch versus a later one?
• Does a reverted subcall roll the change back?
• Can you point at the object in a client: P2P?

Terms

BIP 157

The public text titled Client Side Block Filtering.

Deployed

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

An underpriced or ambiguous EVM rule is not a feature. It is a block that takes longer than the gas limit claimed, or a client that disagrees about the result.

What the design proposes

• A new light client protocol in Bitcoin that improves upon currently available options.
• The standard light client protocol in use today, defined in BIP 37 https://github.com/bitcoin/bips/blob/master/bip-0037.mediawiki , has known flaws that weaken the security and privacy of clients and allow denial-of-service attack vectors on full nodes https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-May/012636.html .
• The new protocol overcomes these issues by allowing light clients to obtain compact probabilistic filters of block content from full nodes and download full blocks if the filter matches relevant data.

How the mechanism is specified

• Taken from the specification, the next constraint is: The standard light client protocol in use today, defined in BIP 37 https://github.com/bitcoin/bips/blob/master/bip-0037.mediawiki , has known flaws that weaken the security and privacy of clients and allow denial-of-service attack vectors on full nodes https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-May/012636.html .
• Locate P2P in BIP 157 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• A gas or opcode change is not a throughput benchmark. It is a relative price and a validity rule.
• Constants in the text can be superseded by a later fork. Cite the EIP number and the fork you mean.
• The source marks this deployed. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use BIP 157 when a pitch says 'Client Side Block Filtering' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.