NodeGuide / Optional reference / Mempool & Fees
Mempool & Fees Reference Guide
Scroll down to see entire page
Quick definitions appear when you tap technical terms during setup. This optional guide gives you more help with setup, settings, and troubleshooting.
Safety wording reviewed September 23, 2026. Reference instructions may differ by device, app and installed software version; NodeGuide does not detect your version. Check the current official instructions before making a change.
Space used for waiting transactions
This setting controls how much memory your node can use to hold unconfirmed transactions. Most beginners can leave the default setting unchanged.
How long waiting transactions are kept
This setting controls how long an unconfirmed transaction can remain in your node’s mempool before it may be removed.
Lowest fee your node will normally share
This is the lowest transaction fee your node normally requires before it will accept and share a transaction. Most beginners can leave the default setting unchanged.
Transaction fees and confirmation
Transactions that pay higher fees may be confirmed sooner when block space is busy, but no fee level guarantees exactly when a transaction will confirm.
Replace-by-fee (RBF)
RBF lets some unconfirmed transactions be replaced by a newer version that pays a higher fee. This can help a transaction confirm sooner.
Keeping waiting transactions after a restart
When this setting is turned on, your node can save its current mempool when it shuts down and restore it after restarting.
Why nodes may show different waiting transactions
Different Bitcoin nodes may show different unconfirmed transactions because of timing, internet connections, relay settings, fees, and other settings.
Common mempool & fee troubleshooting
If a transaction is missing or is not being shared, first check your node connections, mempool size, minimum relay fee, and transaction settings. Change one setting at a time.