Ever sent a Bitcoin payment and watched it sit in "pending" for hours while the fee estimate jumped? That frustration stems from how Mempool Policy is the set of local rules each Bitcoin node uses to decide which unconfirmed transactions to store, relay, and prioritize for mining. It’s not just about paying more; it’s about understanding the invisible traffic control system that determines whether your transaction gets into the next block or waits days. As of 2026, with the release of Bitcoin Core 31.0 introducing a new cluster-based design, the mechanics have shifted significantly, making it crucial to understand how Transaction Priority is calculated using fee rates measured in satoshis per virtual byte (sat/vB).
The Difference Between Consensus Rules and Local Policy
To grasp why some transactions fly through while others stall, you need to distinguish between consensus and policy. Consensus rules are the roughly 100 strict laws that define a valid block on the Bitcoin network. If a transaction breaks these, it’s invalid everywhere. Policy, however, is local. Each of the tens of thousands of full nodes running Bitcoin Core maintains its own mempool-a temporary holding area for unconfirmed transactions.
Policy rules act as a filter before a transaction even enters this pool. For instance, if you send a transaction paying only 0.05 sat/vB, it might be technically valid under consensus, but default nodes will reject it because it falls below the minimum relay threshold. This means there is no single global mempool. A transaction might exist in 10,000 nodes' mempools but vanish from another 1,000 that have stricter settings. This decentralization of policy allows for flexibility but also creates confusion for users who see different statuses across explorers.
Key Parameters Controlling Your Transaction's Fate
Several numerical thresholds dictate whether your transaction survives the mempool gauntlet. Understanding these specific values helps you avoid common pitfalls like dust outputs or premature eviction.
- Minimum Relay Fee: Since Bitcoin Core 29.1 (released September 2025), the default floor is 0.1 sat/vB. Previously, it was 1 sat/vB. This 90% reduction reflects higher BTC prices and aims to allow low-value payments without spamming the network.
- Mempool Size Cap: Default nodes limit their memory usage to 300 MB. When this cap is hit, the lowest-fee transactions are evicted (dropped) to make room for higher-paying ones.
- Expiry Time: Transactions stay in the mempool for up to 336 hours (14 days) by default. After this, they are purged unless re-broadcast. Some operators extend this to months, but most drop them at two weeks.
- Dust Limits: To prevent bloating the blockchain with uneconomical outputs, nodes reject outputs smaller than certain thresholds. For standard P2PKH addresses, this is 546 satoshis. For SegWit (P2WPKH) addresses, it’s lower, around 294 satoshis, due to reduced data size.
How Miners Select Transactions: The Fee Rate Race
Miners don’t care about absolute fee amounts in isolation; they care about density. They want to maximize revenue per unit of space. This is where Fee Rate becomes the primary metric used by miners to rank transactions, calculated as total fee divided by virtual size. A small transaction paying 100 sat/vB is often preferred over a large one paying 30 sat/vB, even if the latter pays more in total satoshis.
In Bitcoin Core 31.0, this selection process became more sophisticated with the introduction of cluster limits. Instead of looking at individual parent-child relationships, the software now groups connected transactions into clusters. These clusters are capped at 64 transactions and 101 kilobytes of virtual size. The miner’s algorithm calculates an average feerate for the entire cluster. If a group of five transactions has a combined feerate of 50 sat/vB, it competes against single transactions based on that package rate. This ensures that complex payment structures, like Child-Pays-For-Parent (CPFP) scenarios, are evaluated fairly against simpler transfers.
Stuck Transactions and the Role of RBF
What happens when you pay too little? Your transaction gets stuck. During high-demand periods, such as the spikes seen in 2021 or occasional surges in 2026, low-fee transactions can wait days. If the mempool fills up, your transaction may be evicted entirely. Once evicted, it doesn’t automatically refund you; the coins remain locked in an unspent output until you create a new transaction.
This is where Replace-by-Fee (RBF) is a mechanism allowing users to broadcast a new version of a transaction with a higher fee to replace the original one comes in. RBF is enabled by default in most modern wallets. To successfully replace a transaction, the new one must meet strict criteria:
- All conflicting inputs must signal RBF capability.
- The replacement must pay a fee that is at least equal to the sum of the original fees plus an incremental amount (typically 0.1 sat/vB times the size).
- The replacement cannot involve more than 100 descendant transactions, preventing massive chain replacements.
Navigating Fee Estimates in 2026
Fee markets fluctuate. In the stable period of mid-2026, typical feerates hover between 2 and 17 sat/vB. However, during congestion, these can spike to 100+ sat/vB. Tools like mempool.space provide real-time recommendations categorized by priority:
- High Priority: Targets confirmation in the next block. Usually corresponds to the median feerate of the current mempool top.
- Medium Priority: Targets confirmation within 2-3 blocks.
- Low Priority: Accepts longer waits, potentially several hours or days.
| Parameter | Bitcoin Core 29.1 (Sep 2025) | Bitcoin Core 31.0 (Apr 2026) |
|---|---|---|
| Minimum Relay Fee | 0.1 sat/vB | 0.1 sat/vB |
| Mempool Size Limit | 300 MB | 300 MB |
| Package Limits | Ancestor/Descendant (25 txns, ~100 kB) | Cluster-based (64 txns, 101 kB) |
| RBF Logic | Standard BIP 125 rules | Cluster-aware "strictly better" feerate check |
| Dust Threshold (P2WPKH) | ~294 sats | ~294 sats |
Practical Tips for Users
If you’re sending Bitcoin regularly, keep these strategies in mind to ensure smooth confirmations:
- Check Current Feerates: Never rely on fixed fee assumptions. Use a live explorer or wallet estimator. A fee that was sufficient yesterday might be insufficient today.
- Avoid Dust Outputs: If splitting payments, ensure each output exceeds the dust limit (294 sats for SegWit). Otherwise, your transaction may be rejected by nodes.
- Use RBF Proactively: If your transaction hasn’t confirmed after 1-2 hours, consider bumping the fee via RBF rather than waiting for potential eviction.
- Understand Cluster Limits: If you use multi-sig or complex scripts, remember that your related transactions form a cluster. Keep the total size under 101 kB to avoid policy rejection.
Why did my Bitcoin transaction get stuck?
Your transaction likely paid a fee rate lower than the current market demand. If the mempool is congested, miners prioritize higher-fee transactions. Additionally, if the transaction fell below the node's minimum relay fee (0.1 sat/vB) or created dust outputs, it may have been rejected by many nodes. Waiting for the mempool to clear or using RBF to increase the fee are the standard solutions.
What is the difference between consensus and policy in Bitcoin?
Consensus rules are global and mandatory for all nodes; breaking them makes a transaction invalid forever. Policy rules are local to each node and determine which valid transactions are stored and relayed. A transaction can be consensus-valid but policy-invalid on specific nodes, meaning it won't be included in those nodes' mempools or block templates.
How does Bitcoin Core 31.0 change transaction prioritization?
Bitcoin Core 31.0 replaces ancestor/descendant limits with cluster-based limits. Transactions are grouped into clusters of up to 64 entries or 101 kB. Miners evaluate the average feerate of the entire cluster, ensuring that packages of related transactions compete fairly against single transactions. This simplifies resource management and improves RBF consistency.
Is it safe to pay the minimum relay fee of 0.1 sat/vB?
It is safe in terms of validity, but risky for speed. At 0.1 sat/vB, your transaction is at the bottom of the priority queue. During any congestion, it will likely wait days or be evicted. It is suitable only for very low-value, non-urgent payments where you are willing to wait indefinitely or re-broadcast later.
What happens if a transaction is evicted from the mempool?
The transaction disappears from the node's memory, but the UTXOs it spent remain unspent on-chain. You do not lose the funds, but the transaction is no longer being propagated. To recover, you must create a new transaction spending the same inputs, typically with a higher fee, or wait for the original to be rebroadcast by a wallet that still holds it.
