BIP 35: add mempool message



Summary:

A new BIP (Bitcoin Improvement Proposal) has been suggested for P2P changes, with the aim of making a network node's transaction memory pool accessible via a new "mempool" message. The proposal suggests that by doing so, it would enable several use cases such as SPV clients wanting to obtain zero-confirmation transactions sent or received, miners downloading existing network transactions after a restart, and remote network diagnostics. The specification proposed in the BIP includes that 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. An "inv" message is always returned, even if empty. The typical node behavior in response to an "inv" is "getdata". However, 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 and NODE_NETWORK bit set in nServices.The author of the BIP suggests that older clients remain 100% compatible and interoperable after this change. The implementation details can be found on https://github.com/bitcoin/bitcoin/pull/1641. Feedback has been requested on the proposal.


Updated on: 2023-06-06T06:59:17.251500+00:00