BIP 35: add mempool message



Summary:

During a discussion about P2P changes in Bitcoin, Jeff Garzik suggested creating a BIP to address these changes. He provided a link to the proposed BIP 0035 and requested feedback. One of the proposed changes was adding the ability to query the memory pool of a node, which would allow nodes to get a memory pool refill at startup. When a "mempool" message is received, the node will respond with an "inv" message containing MSG_TX hashes of all transactions in the node's transaction memory pool. However, there were concerns about the usefulness of the empty "inv" message that would be returned even if there were no transactions in the memory pool.Another change proposed was enabling feature discovery by checking two "version" message attributes: Protocol version >= 60002 and NODE_NETWORK bit set in nServices. While this seems safe, it may force full implementations to also implement this feature. Pieter, who was part of the discussion, suggested allocating an extra service bit for mempool-providing services. This would mean that these services could be discovered before connecting to them, as the service bits are carried around in addr messages. Overall, the discussion centered around making improvements to the Bitcoin P2P protocol.


Updated on: 2023-05-19T04:08:17.404620+00:00