Connection Bloom filtering

The five-minute read

One action, walked through

1. Open BIP 37 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: New support to the peer-to-peer protocol that allows peers to reduce the amount of transaction data they are sent.
3. Name the object that changes: SPV.
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 37 at the status the text itself states: Deployed.
• The object that has to change is SPV. 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 Connection Bloom 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: SPV?

Terms

BIP 37

The public text titled Connection Bloom 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

• 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 [http://en.wikipedia.org/wiki/Bloom_filter Bloom filter] on data derived from transactions.

How the mechanism is specified

• Taken from the specification, the next constraint is: Peers have the option of setting ''filters'' on each connection they make after the version handshake has completed.
• Locate SPV in BIP 37 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 37 when a pitch says 'Connection Bloom filtering' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.