Skip to main content
£0.00 0

Basket

No products in the basket.

ASIC mining articles and advice

Bitcoin Core maxmempool Explained: Limits and Eviction

Bitcoin Core maxmempool guide covering memory limits, package eviction, rolling minimum fees, mining effects, monitoring and safe capacity tests.

Bitcoin Core maxmempool guide cover

This guide explains Bitcoin Core maxmempool in plain English. It focuses on what the subject is, why it matters and what a beginner should remember.

TL;DR

  • What it is: Bitcoin Core 0.12 introduced a bounded transaction mempool controlled by maxmempool, expressed in megabytes. When the pool exceeds that target, the node removes low-fee transaction packages and raises a local rolling minimum feerate.
  • Why it matters: maxmempool is a resource-control and relay-policy input, not a consensus rule. Size it from measured workload and total memory headroom, then verify eviction, mining and failover behaviour under deliberate pressure.
  • Current position: Bitcoin Core 0.12 introduced a bounded transaction mempool controlled by maxmempool, expressed in megabytes.

Bitcoin Core maxmempool in simple English

Bitcoin Core maxmempool: The setting bounds the mempool data structure used for unconfirmed transactions, measured with release-specific accounting. It does not cap total bitcoind resident memory.

Simple example

A miner is checking Bitcoin Core maxmempool. Capacity planning must compare observed RSS and cgroup limits, not equate the argument with process size. An operator should test realistic chains rather than assume every transaction competes independently on its own feerate.

Key terms in plain English

Bitcoin Core:
Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
RPC:
A command that software sends to a node to request information or a local action.
Consensus:
The shared rules full nodes use to decide whether blocks and transactions are valid.
Mempool:
A node’s changing local collection of valid, unconfirmed transactions.
Node:
A computer running Bitcoin software that checks data and communicates with other peers.

What the limit covers

The setting bounds the mempool data structure used for unconfirmed transactions, measured with release-specific accounting. It does not cap total bitcoind resident memory. Peer buffers, validation caches, wallet state, indexes, RPC responses and the operating system page cache remain separate. Capacity planning must compare observed RSS and cgroup limits, not equate the argument with process size.

Package-aware eviction

Transactions can depend on unconfirmed parents. Evicting a single low-fee parent can make descendants unusable, so Core evaluates packages and removes related entries. The exact ancestor and descendant logic evolved. An operator should test realistic chains rather than assume every transaction competes independently on its own feerate.

Rolling minimum fee

After eviction the node raises its effective mempool minimum above the removed package and later decays that threshold. This local policy reduces immediate re-entry and repeated churn. Two honest nodes with different memory pressure can therefore accept different transactions while agreeing completely on consensus-valid blocks.

Bitcoin Core maxmempool technical diagram
Rolling minimum fee: the fields, validation boundary and operational evidence that implementations need to agree.

Mining and template effects

A pool node can only select transactions it has retained or can reacquire. A small mempool may discard low-fee packages that later become attractive through descendants, while an oversized pool can compete with template construction and validation for memory. Measure template latency, stale work and package availability on primary and failover nodes.

Interaction with other fees

maxmempool works with incremental relay fee, minimum relay fee, replacement rules and transaction expiry. Those controls answer different questions. The memory cap triggers eviction; relay thresholds govern admission; replacement pricing discourages bandwidth churn; expiry removes old entries. Treating one as a substitute for the others creates surprising policy.

Monitoring the effective state

Use getmempoolinfo fields appropriate to the installed release, alongside RSS, swap, allocator behaviour and eviction-related logs. Watch bytes, usage, transaction count and mempool minimum rather than one dashboard number. Alert on sustained pressure and on divergence between nodes that should provide equivalent mining or wallet service.

How specialists test it

Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.

Frequently asked questions

What is the main point of Bitcoin Core maxmempool?

Bitcoin Core maxmempool: The setting bounds the mempool data structure used for unconfirmed transactions, measured with release-specific accounting.

For Bitcoin Core maxmempool, what should a beginner know about what the limit covers?

The setting bounds the mempool data structure used for unconfirmed transactions, measured with release-specific accounting.

For Bitcoin Core maxmempool, what should a beginner know about package-aware eviction?

Transactions can depend on unconfirmed parents. Evicting a single low-fee parent can make descendants unusable, so Core evaluates packages and removes related entries.

For Bitcoin Core maxmempool, what should a beginner know about rolling minimum fee?

After eviction the node raises its effective mempool minimum above the removed package and later decays that threshold.

Conclusion

maxmempool is a resource-control and relay-policy input, not a consensus rule. Size it from measured workload and total memory headroom, then verify eviction, mining and failover behaviour under deliberate pressure.

Primary sources

Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.

ASIC MINER PICKS

Recommended ASIC Mining Hardware

Compare three of our highest ranked ASIC miners currently available, with live product details and pricing.
Overall ranking
Overall rank#1of 163AvailableAll: #6 / 836
Bitmain Antminer S21+ Hydro 395Th SHA-256 Bitcoin Miner
Bitmain
Pre-OrderFree Shipping
Hashrate
395TH
Efficiency
15W/TH
Power
5925W
Earns/kWh
£0.057
Price · delivered
£2,970.00
ex VAT
Est. per month
£245.77
Payback 1 Year
Overall ranking
Overall rank#3of 163AvailableAll: #8 / 836
Canaan Avalon A1566HA Hydro 2U 460Th SHA-256 Bitcoin Miner
Canaan
In stockFree Shipping
Hashrate
460TH
Efficiency
16.8W/TH
Power
7728W
Earns/kWh
£0.051
Price · delivered
Original price was: £5,176.00.Current price is: £3,430.00.
ex VAT
Est. per month
£286.22
Payback 12 Months
Overall ranking
Overall rank#5of 163AvailableAll: #11 / 836
MicroBT Whatsminer M65S+ Hydro 414Th SHA-256 Bitcoin Miner
MicroBT
In stockFree Shipping
Hashrate
414TH
Efficiency
17W/TH
Power
7038W
Earns/kWh
£0.050
Price · delivered
£2,970.00
ex VAT
Est. per month
£257.59
Payback 11.5 Months
Browse all ASIC miners
MORE MINING ADVICE

More ASIC Mining Articles

Read practical advice about choosing hardware, calculating electricity costs, setting up miners, hosting and maintenance.
MINER COMMUNITY

Join the ASIC Mining Discussion

Ask a question or share what has worked for you. Your experience may help another miner make a better decision.

Members can read and join the discussion

Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.

Log in to read comments Register to join the discussion

Membership helps us protect the discussion from spam and keep answers useful.

ASIC MINING SUPPORT

Need Help Choosing an ASIC Miner?

Tell us what you want to mine, your electricity cost and where the machine will run. We can help you compare hardware, power requirements, hosting and repairs.
Contact our mining team
Browse ASIC miners