AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 38 Bitcoin

Limit mempool size based on chunk feerate

Public commit record

What the developer wrote

Authored by Suhas Daftuar

80/100 · Strong
Limit mempool size based on chunk feerate

Rather than evicting the transactions with the lowest descendant feerate,
instead evict transactions that have the lowest chunk feerate.

Once mining is implemented based on choosing transactions with highest chunk
feerate (see next commit), mining and eviction will be opposites, so that we
will evict the transactions that would be mined last.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
The short version

What changed, and why it matters

This Bitcoin Core commit changes how the mempool (the waiting area for unconfirmed transactions) decides which transactions to kick out when it gets too full. Previously it used 'descendant feerate'; now it uses 'chunk feerate' so that the transactions a miner would pick last are the same ones the mempool evicts first. This is a consistency improvement in transaction selection policy, not a fix for a clear exploit. The change could affect transaction propagation, fee estimation, and mempool behavior under load, but the commit itself does not describe any security vulnerability.

Recommended action

Review the interaction between the new chunk graph (m_txgraph) and the legacy mapTx index to ensure the staged entries always correspond to live mempool entries. Verify that UpdateForRemoveFromMempool plus removeUnchecked correctly maintains mempool invariants (ancestors/descendants, cached fees/sizes) and that no entries are double-removed or leaked. Run the updated MempoolSizeLimitTest and fuzz/stress tests for mempool trimming.

Security signals we found

01

Change in mempool eviction policy from descendant feerate to chunk feerate

02

Manual staging and removal logic replacing RemoveStaged

03

Potential for inconsistent mempool state if GetWorstMainChunk and mapTx drift

04

Behavioral change in which transactions are evicted under memory pressure

05

No explicit security claim or CVE in commit message

Risk score

Why this scored 38/100

Our methodology →
Potential impact 8/30
Exploitability 5/25
Stealth signal 6/15
Affected reach 10/15
Confidence 6/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.