How Does a Node Manage Its Mempool Size?

Nodes typically have a configurable limit on the total size of their mempool (in MB or number of transactions). When the limit is reached, nodes use a policy, usually based on the lowest fee-per-byte, to evict transactions to make room for new, higher-fee ones.

This ensures the mempool remains manageable.

How Does a Zero-Fee Transaction Affect a Bitcoin Block’s Overall Profitability?
What Is the Economic Argument for Keeping the Block Size Limit Small?
How Do Layer 2 Solutions Affect the Cryptocurrency Fee Market?
Why Might a Stop-Limit Order Fail to Execute Completely?
How Does the Size of the Mempool Relate to the Risk of Front-Running?
What Is the Difference between a Node’s Mempool and the Global Set of Unconfirmed Transactions?
What Is the Significance of Transaction Size in Bytes?
How Does a “Stop-Limit Order” Combine the Features of a Stop Order and a Limit Order?

Glossar