BIP 35: mempool message
Also known as: BIP35, BIP-0035.
In plain English: Adds a "mempool" message that lets a node ask a peer for the unconfirmed transactions it is holding. This helps lightweight wallets and freshly started nodes learn quickly about payments still waiting to be confirmed.
- Status
- Deployed
- Type
- Specification
- Layer
- Peer Services
- Authors
- Jeff Garzik
- Assigned
- Last changed
- Topics
- Network, Mempool
- Source
- bip-0035.mediawiki on GitHub · Markdown
Full specification
Abstract
Make a network node's transaction memory pool accessible via a new "mempool" message. Extend the existing "getdata" message behavior to permit accessing the transaction memory pool.
Motivation
Several use cases make it desirable to expose a network node's transaction memory pool:
- SPV clients, wishing to obtain zero-confirmation transactions sent or received.
- Miners, to avoid missing lucrative fees, downloading existing network transactions after a restart.
- Remote network diagnostics.
Specification
- The mempool message is defined as an empty message where pchCommand == "mempool"
- Upon receipt of a "mempool" message, the node will respond with an "inv" message containing MSG_TX hashes of all the transactions in the node's transaction memory pool, if any.
- The typical node behavior in response to an "inv" is "getdata". However, the reference Satoshi implementation ignores requests for transaction hashes outside that which is recently relayed. To support "mempool", an implementation must extend its "getdata" message support to querying the memory pool.
-
Feature discovery is enabled by checking two "version" message attributes:
- Protocol version >= 60002
- NODE_NETWORK bit set in nServices
Note that existing implementations drop "inv" messages with a vector size > 50000.
Backward compatibility
Older clients remain 100% compatible and interoperable after this change.