What is Mempool in Blockchain, Purpose, and Implications

What is Mempool in Blockchain

Ethereum and Bitcoin use mempools, which stand for “memory” and “pool”. A waiting room or interim storage space for unconfirmed transactions broadcast to the network but not yet included in a block. It is a queue of pending transactions rather than a storage device.

Definition and Purpose

• Definition: A mempool is a distributed queue or in-memory buffer that blockchain nodes keep to store broadcast but unconfirmed transactions. Every network node keeps an autonomous mempool. This implies that there isn’t a single universal pool that all nodes share; instead, propagation delays and different node rules may cause some tiny variations in the pool’s precise contents.
• Purpose: A mempool basically stores unconfirmed transactions. It buffers users and miners/validators during large transaction flow, preventing blockchain saturation. Ensuring transactions are processed and confirmed prevents double-spending and maintains blockchain integrity.

You can also read Segregated Witness Blockchain: How SegWit Works & Impact

How a Transaction Moves Through the Mempool

The journey of a transaction through the mempool involves several stages:

• Transaction Creation and Broadcast: When a user initiates a cryptocurrency transaction, it is signed by their wallet and broadcast to the nearest nodes they are connected to on the network.
• Node Reception and Validation: Upon receiving a new transaction, a node performs a series of preliminary validation checks before adding it to its mempool. These checks typically include:
  • Verifying that signatures are correct and the transaction is syntactically formatted correctly.
  • Ensuring the sender has sufficient funds (UTXO availability) and that outputs do not exceed inputs.
  • Checking for no double-spending, meaning the inputs have not already been spent in another unconfirmed transaction within that node’s mempool.
  • Adhering to transaction size limits.
  • For Ethereum, checking the nonce value (transaction count) to ensure transaction order and prevent replay attacks.
• Entry into Mempool and Propagation: The node adds the transaction to its local mempool if it passes these first tests. This newly received and validated transaction is broadcast to other nodes in the network by the node.
• Waiting for Inclusion (Miner/Validator Selection): The transaction waits in the mempool for a miner (in Bitcoin) or validator (in Ethereum). The fee rate (fee per unit of transaction size) motivates miners and validators to prioritize transactions, with greater costs attracting faster inclusion. This generates a “fee market” where users bid for verification speed.
• Inclusion in a Block and Removal: When a miner successfully creates a new block, they include a selection of transactions from their mempool (prioritizing by fee rate, up to the block’s size limit). Once a transaction is successfully included in a new block and that block is added to the blockchain and validated by other nodes, all nodes on the network remove that transaction from their respective mempools. It has now moved from temporary storage to the permanent ledger.
• Expiration/Dropping: “Mempool expiry” rules may eventually cause a transaction to be removed from a node’s mempool if it stays there for an extended period of time without being included in a block (for example, because of a very low fee during periods of high network congestion, or because it was an invalid transaction that wasn’t detected right away). For instance, Bitcoin transactions usually expire after two weeks. If dropped, the transaction essentially “disappears” from the network and must be rebroadcast by the sender’s wallet, maybe at a greater cost. Unconfirmed transactions never result in money loss; even if they are dropped, the money stays in the wallet.

You can also read Pay to Public Key Hash (P2PKH) in Blockchain & How It Works

Mempool Congestion and Implications

• Congestion: The mempool can become congested when network activity is high, meaning there are more transactions waiting than can fit into the immediate blocks. This is typical in the Bitcoin mempool, where it can be congested for a significant portion of the time.
• Delays and Costs: Congestion inevitably leads to delays in transaction commit times, with some transactions potentially waiting for extended periods (e.g., hours or even days). It also results in increased transaction costs, as users may need to pay higher fees to incentivize miners for faster inclusion.
• Stuck Transactions: Transactions with very low fees might get “stuck” in the mempool for extended periods or even be dropped. Reasons for transactions getting stuck include network congestion, setting the gas fee too low, or a drop in the hash rate (for Bitcoin).

Managing Stuck Transactions

You cannot directly withdraw Bitcoin from the mempool as it is not a storage area but a queue. However, there are a few options if your transaction is stuck:

• Cancel the Transaction: Some blockchains allow you to cancel transactions, often by sending a new transaction with the same nonce and a higher fee to overwrite the original, though this will incur another transaction fee.
• Speed Up the Transaction: You can increase the fee on an unconfirmed transaction to incentivize miners to process it more quickly. For Bitcoin, this can be achieved using Replace-By-Fee (RBF), which allows you to resend the same transaction with a higher fee (if RBF was initially enabled), or Child-Pays-for-Parent (CPFP), where a new transaction spending the unconfirmed output adds a high fee to incentivize miners to confirm both transactions.
• Wait Longer: If your fee wasn’t too low and the network is simply congested, your transaction should eventually go through, though it might take a few days.

Monitoring the Mempool

Real-time mempool data is available from Blockchain.com, Mempool.space, and Etherscan. Unconfirmed transactions, mempool size, and average/median transaction fees for different confirmation times are included. Users may better comprehend network congestion and estimate suitable costs with the use of this information.

Similarities Between Bitcoin and Ethereum Mempools

The transaction validation procedure in both mempool variants works nearly the same way, despite their fundamental differences as blockchain networks. Both employ a fee-based prioritization structure for miners/validators and store and validate pending transactions. Ethereum Virtual Machine (EVM) and smart contracts allow more accurate, automated condition verification, which may speed up validation. However, network congestion and processing resource overuse may hinder Ethereum transactions.

Summary Table

You can also read P2SH-P2WPKH: Backward-Compatible SegWit Addresses