Posted by andrewtoth
Apr 8, 2025/16:43 UTC
In the intricacies of blockchain transactions, particularly concerning Bitcoin's mempool mechanics, the concept of an "extra pool" emerges as a notable aspect. This extra pool is essentially a limited storage area, accommodating merely 100 transactions by default. Its main purpose is to contain transactions that are not immediately relayed across the network, distinguishing itself from the primary mempool where transactions await confirmation by miners.
One key feature of this system is the handling of transactions replaced via the Replace-By-Fee (RBF) protocol. When a transaction is superseded by another with a higher fee, the original transaction is relegated to the extra pool, while the new, replacing transaction continues to be broadcasted normally. This ensures that even though some transactions are put aside in the extra pool, there remains a pathway for updated transactions to be propagated and potentially confirmed by miners.
However, the utility of the extra pool faces challenges due to its reliance on the interconnectedness of peers within the network. Since each peer maintains its own version of the extra pool, differences arise based on the transactions each peer receives and rejects. For instance, if one node receives numerous unwanted transactions from a specific peer, those transactions populate its extra pool, creating a divergence in the contents of extra pools across the network. This variability raises questions about the likelihood of transactions in the extra pool being included in a block by miners, considering these transactions are not actively relayed further than their initial reception.
Moreover, a suggestion to optimize the system involves reevaluating the necessity of placing orphan transactions—those missing a parent transaction in the chain—into the extra pool. Given that the process already includes searching for such orphans, it might be more efficient to exclude them from the extra pool altogether. This adjustment could streamline the operation of the extra pool, focusing its capacity on handling RBF transactions more effectively.
TLDR
We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
We'd love to hear your feedback on this project?
Give Feedback