The fee market and mempool policy
Reading as Holder. What matters when you hold your own coins.10 of 25 claims
What it isCurious
A Bitcoin transaction's fee is not a separate field: it is the total value of the transaction's inputs minus the total value of its outputs. Bitcoin Core's consensus code computes the fee this way and rejects as invalid a transaction that spends inputs worth less than its outputs.1: open 2 sources
DefinitionCuriousEstablishedHigh confidence
T1Bitcoin Core src/consensus/tx_verify.cpp, Consensus::CheckTxInputsSource code, says this directly
const CAmount txfee_aux = nValueIn - value_out;
Consensus::CheckTxInputs, fee computation, read 2026-11-20
T1Bitcoin Core src/consensus/tx_verify.cpp, Consensus::CheckTxInputsSource code, says this directly
if (nValueIn < value_out) {
Consensus::CheckTxInputs, inputs below outputs check, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/consensus/tx_verify.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/consensus/tx_verify.cpp | grep -nF 'const CAmount txfee_aux = nValueIn - value_out;'bitcoin/bitcoin at f498a5a671 contains this text in src/consensus/tx_verify.cpp.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/consensus/tx_verify.cpp | grep -nF 'bad-txns-in-belowout'Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 2/2, code 2/2History, hash and citation
A mempool (short for memory pool) is the set of valid but unconfirmed transactions that a Bitcoin node holds while they wait to be mined. Each node keeps its own mempool under its own local rules, so there is no single network-wide mempool.2: open 3 sources
DefinitionCuriousEstablishedMedium confidence
T2Bitcoin Developer Guide, P2P Network, Memory PoolDocumentation, says this directly
Bitcoin Core stores them in non-persistent memory, calling them a memory pool or mempool.
Memory Pool, read 2026-11-20
T1Bitcoin Core src/txmempool.h, CTxMemPool doc commentSource code, says this directly
CTxMemPool stores valid-according-to-the-current-best-chain transactions
Doc comment above class CTxMemPool, read 2026-11-20
T2Bitcoin Core doc/policy/README.mdDocumentation, supports part of it
These rules are local to the node and configurable, see "Node relay options" when running `-help`.
Opening paragraph, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 3/3History, hash and citation
Fee rates and waitingUser
Bitcoin fee rates are usually quoted in satoshis per virtual byte (sat/vB). BIP 141 defines a transaction's virtual size as its weight divided by 4, rounded up, so the same fee rate costs a larger transaction more sats in total.3: open 2 sources
DefinitionUserEstablishedHigh confidence
T1BIP 141, Segregated Witness (Consensus layer)BIP, says this directly
Virtual transaction size is defined as Transaction weight / 4 (rounded up to the next integer).
Specification, Transaction size calculations, read 2026-11-20
T1Bitcoin Core 30.0 release notesRelease notes, supports part of it
(`-incrementalrelayfee`) have been changed to 0.1 satoshis per vB.
Policy, minimum relay feerate (#33106), read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/consensus/consensus.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/consensus/consensus.h | grep -nF 'inline constexpr int WITNESS_SCALE_FACTOR = 4;'Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 2/2, code 1/1History, hash and citation
A Bitcoin transaction can stay unconfirmed for a long time when its fee rate is low compared with other transactions waiting to be mined, because transactions paying higher fee rates are generally mined first. Since Bitcoin Core 31.0, its block templates select mempool transactions in order of the fee rate at which they are expected to be mined.4: open 3 sources
How it worksUserEstablishedMedium confidence
T1Bitcoin Core 31.0 release notesRelease notes, says this directly
Within the mempool, transactions are ordered based on the feerate at which
Mempool, cluster mempool ordering, read 2026-11-20
T1Bitcoin Core 31.0 release notesRelease notes, says this directly
by the algorithms that implement transaction selection for constructing block
Mempool, cluster mempool ordering, read 2026-11-20
T1Bitcoin Core src/policy/fees/block_policy_estimator.h, CBlockPolicyEstimator commentSource code, supports part of it
the assumption that in general transactions of higher feerate will be
Doc comment above class CBlockPolicyEstimator, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 3/3History, hash and citation
Bitcoin Core limits its mempool to 300 MB of memory by default (the -maxmempool option). When the mempool is full, a node starts rejecting new transactions below a minimum fee rate threshold and evicts low fee rate transactions, so a low-fee transaction can drop out of some nodes' mempools.5: open 4 sources
How it worksUserEstablishedHigh confidence
T1Bitcoin Core src/kernel/mempool_options.hSource code, says this directly
/** Default for -maxmempool, maximum megabytes of mempool memory usage */
DEFAULT_MAX_MEMPOOL_SIZE_MB, read 2026-11-20
T1Bitcoin Core src/txmempool.h, TrimToSizeSource code, says this directly
Remove transactions from the mempool until its dynamic size is <= sizelimit.
Doc comment above CTxMemPool::TrimToSize, read 2026-11-20
T1Bitcoin Core src/txmempool.h, GetMinFeeSource code, says this directly
The minimum fee to get into the mempool, which may itself not be enough
Doc comment above CTxMemPool::GetMinFee, read 2026-11-20
T1Bitcoin Core 31.0 release notesRelease notes, supports part of it
eviction from the mempool when it is full
Mempool, cluster mempool ordering, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/kernel/mempool_options.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/mempool_options.h | grep -nF 'inline constexpr unsigned int DEFAULT_MAX_MEMPOOL_SIZE_MB{300};'Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 4/4, code 1/1History, hash and citation
Bitcoin Core removes a transaction from its mempool if it is still unconfirmed 336 hours (14 days) after entering, by default. The limit is set by the -mempoolexpiry option, so other nodes may keep or drop the same transaction at different times.6: open 1 source
FactUserEstablishedHigh confidence
T1Bitcoin Core src/kernel/mempool_options.hSource code, says this directly
/** Default for -mempoolexpiry, expiration time for mempool transactions in hours */
DEFAULT_MEMPOOL_EXPIRY_HOURS, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/kernel/mempool_options.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/kernel/mempool_options.h | grep -nF 'inline constexpr unsigned int DEFAULT_MEMPOOL_EXPIRY_HOURS{336};'Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 1/1, code 1/1History, hash and citation
Speeding up a transactionHolder
Replace-by-fee (RBF) is a node relay policy that lets an unconfirmed Bitcoin transaction be replaced by a different transaction spending at least one of the same inputs and paying a higher fee. A sender can use RBF to speed up a stuck transaction.7: open 2 sources
DefinitionHolderEstablishedMedium confidence
T2Bitcoin Optech topic, Replace-by-fee (RBF)Bitcoin Optech, says this directly
Replace-By-Fee (RBF) is a node policy that allows an unconfirmed transaction in a mempool to be replaced
Topic summary, read 2026-11-20
T2Bitcoin Core doc/policy/mempool-replacements.mdDocumentation, supports part of it
A transaction conflicts with an in-mempool transaction ("directly conflicting transaction") if they
Opening paragraph, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 2/2History, hash and citation
Child pays for parent (CPFP) is a way to speed up a stuck, low fee rate Bitcoin transaction: someone who controls one of its outputs spends that output in a new child transaction with a high fee rate, which encourages miners to include both transactions in a block.8: open 1 source
DefinitionHolderEstablishedMedium confidence
T2Bitcoin Optech topic, Child pays for parent (CPFP)Bitcoin Optech, says this directly
Child Pays For Parent (CPFP) is a fee bumping technique where a user spends an output from a low-feerate unconfirmed
Topic summary, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 1/1History, hash and citation
Bitcoin Core's wallet has a bumpfee command that replaces an unconfirmed wallet transaction with a new version paying a higher fee, taking the extra fee from change outputs or by adding inputs when necessary.9: open 2 sources
FactHolderEstablishedHigh confidence
T1Bitcoin Core src/wallet/rpc/spend.cpp, bumpfee help textSource code, says this directly
Bumps the fee of a transaction T, replacing it with a new transaction B.
bumpfee_helper, RPC description, read 2026-11-20
T1Bitcoin Core src/wallet/rpc/spend.cpp, bumpfee help textSource code, says this directly
The command will pay the additional fee by reducing change outputs or adding inputs when necessary.
bumpfee_helper, RPC description, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/wallet/rpc/spend.cpp, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/wallet/rpc/spend.cpp | grep -nF 'Bumps the fee of a transaction T, replacing it with a new transaction B.'Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 2/2, code 1/1History, hash and citation
Consensus and relay policyBuilder
Bitcoin Core's relay policy is a set of rules a node applies, in addition to consensus rules, to unconfirmed transactions before accepting them into its mempool. Policy is local to each node and configurable, and it is not applied to transactions in blocks, so a block can contain transactions a node would not have relayed.10: open 2 sources
DefinitionBuilderEstablishedMedium confidence
T2Bitcoin Core doc/policy/README.mdDocumentation, says this directly
Policy (Mempool or Transaction Relay Policy) is the node's set of validation rules, in addition to consensus,
Opening paragraph, read 2026-11-20
T2Bitcoin Core doc/policy/README.mdDocumentation, says this directly
Policy is *not* applied to transactions in blocks.
Opening paragraph, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 2/2History, hash and citation
Because relay policy differs from node to node, a transaction one node accepts may not reach miners. The Bitcoin Core 30.0 release notes warn that transactions created with the newly allowed lower fee rates are not guaranteed to propagate or confirm unless the lower defaults are widely adopted across the network.11: open 1 source
How it worksBuilderEstablishedMedium confidence
T1Bitcoin Core 30.0 release notesRelease notes, says this directly
Note that unless these lower defaults are widely adopted across the network, transactions
Policy (#33106), read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 1/1History, hash and citation
Since Bitcoin Core 30.0, published on 10 October 2025, the default minimum relay fee rate (-minrelaytxfee) and incremental relay fee rate (-incrementalrelayfee) are both 0.1 sat/vB, set in the code as 100 satoshis per 1,000 vB.12: open 3 sources
FactBuilderEstablishedHigh confidence
T1Bitcoin Core 30.0 release notesRelease notes, says this directly
The default minimum relay feerate (`-minrelaytxfee`) and incremental relay feerate
Policy (#33106), read 2026-11-20
T1Bitcoin Core src/policy/policy.h, DEFAULT_MIN_RELAY_TX_FEESource code, says this directly
inline constexpr unsigned int DEFAULT_MIN_RELAY_TX_FEE{100};
DEFAULT_MIN_RELAY_TX_FEE, read 2026-11-20
T1Bitcoin Core 30.0 release announcementRelease notes, supports part of it
Bitcoin Core 30.0 was published on October 10, 2025.
Release page header, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/policy/policy.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/policy/policy.h | grep -nF 'inline constexpr unsigned int DEFAULT_MIN_RELAY_TX_FEE{100};'bitcoin/bitcoin at f498a5a671 contains this text in src/policy/policy.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/policy/policy.h | grep -nF 'inline constexpr unsigned int DEFAULT_INCREMENTAL_RELAY_FEE{100};'Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 3/3, code 2/2History, hash and citation
CBlockPolicyEstimator, a fee estimator in Bitcoin Core's src/policy/fees/block_policy_estimator.h, estimates the fee rate a transaction needs to be confirmed within a target number of blocks by grouping observed transactions into buckets of similar fee rates and tracking how quickly each bucket confirms.13: open 3 sources
TraceBuilderEstablishedHigh confidence
T1Bitcoin Core src/policy/fees/block_policy_estimator.hSource code, says this directly
The BlockPolicyEstimator is used for estimating the feerate needed
Doc comment above class CBlockPolicyEstimator, read 2026-11-20
T1Bitcoin Core src/policy/fees/block_policy_estimator.hSource code, says this directly
At a high level the algorithm works by grouping transactions into buckets
Doc comment above class CBlockPolicyEstimator, read 2026-11-20
T2Bitcoin Optech topic, Fee estimationBitcoin Optech, background
Fee estimation is the process of estimating the feerate a transaction will need to pay to have a high probability
Topic summary, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/policy/fees/block_policy_estimator.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/policy/fees/block_policy_estimator.h | grep -nF 'class CBlockPolicyEstimator'Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 3/3, code 1/1History, hash and citation
Replacement rulesBuilder
BIP 125 specifies opt-in replace-by-fee: a transaction signals that it may be replaced if any of its inputs has an nSequence value below 0xfffffffe, and BIP 125 caps the transactions a replacement may evict, counting their descendants, at 100.14: open 2 sources
FactBuilderEstablishedHigh confidence
T1BIP 125, Opt-in Full Replace-by-Fee SignalingBIP, says this directly
if any of its inputs have an nSequence number less than (0xffffffff - 1).
Summary, signaling, read 2026-11-20
T1BIP 125, Opt-in Full Replace-by-Fee SignalingBIP, says this directly
which will be evicted from the mempool must not exceed a total of 100 transactions.
Implementation details, rule 5, read 2026-11-20
BIP 125's Title is "Opt-in Full Replace-by-Fee Signaling" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0125.mediawiki | grep -m1 -E '^ *Titles?:'Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 2/2, code 1/1History, hash and citation
Bitcoin Core 28.0, published on 2 October 2024, changed the default of the -mempoolfullrbf option from 0 to 1 (Bitcoin Core PR #30493), so nodes running defaults accept replacements of unconfirmed transactions whether or not they signal BIP 125 replaceability.15: open 3 sources
EventBuilderEstablishedHigh confidence
T1Bitcoin Core 28.0 release notesRelease notes, says this directly
The default value of the `-mempoolfullrbf` configuration option has been changed from 0 to 1,
Mempool policy changes (#30493), read 2026-11-20
T1Bitcoin Core 28.0 release announcementRelease notes, supports part of it
Bitcoin Core 28.0 was published on October 02, 2024.
Release page header, read 2026-11-20
T2Bitcoin Optech topic, Replace-by-fee (RBF)Bitcoin Optech, supports part of it
whether or not it signals BIP125 replaceability.
Topic summary, full-RBF, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 3/3History, hash and citation
Bitcoin Core 29.0 removed the -mempoolfullrbf option (Bitcoin Core PR #30592), making full replace-by-fee the standard behavior. Since then, Bitcoin Core's replacement rules no longer require a transaction to signal BIP 125 replaceability before it can be replaced.16: open 3 sources
EventBuilderEstablishedHigh confidence
T1Bitcoin Core 29.0 release notesRelease notes, says this directly
users no longer benefit from disabling it, so the option has been removed, making full replace-by-fee the standard behavior.
Mempool policy changes (#30592), read 2026-11-20
T2Bitcoin Core doc/policy/mempool-replacements.mdDocumentation, says this directly
Signaling for replace-by-fee is no longer required as of
History, read 2026-11-20
T2Bitcoin Optech topic, Replace-by-fee (RBF)Bitcoin Optech, says this directly
Bitcoin Core #30592 removes the mempoolfullrbf setting
Optech newsletter mentions, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 3/3History, hash and citation
Under Bitcoin Core's replacement rules, a replacement transaction must pay at least the total absolute fee of the transactions it replaces, plus enough extra to pay for its own size at the incremental relay fee rate: at 0.1 sat/vB, a 500 vB replacement must add at least 50 sats.17: open 3 sources
How it worksBuilderEstablishedHigh confidence
T2Bitcoin Core doc/policy/mempool-replacements.mdDocumentation, says this directly
The replacement transaction pays an absolute fee of at least the sum paid by the original transactions.
Rule 3, read 2026-11-20
T2Bitcoin Core doc/policy/mempool-replacements.mdDocumentation, says this directly
replacement pays a fee at least 50 satoshis higher than the sum of the original transactions.
Rule 4, read 2026-11-20
T1Bitcoin Core src/policy/rbf.h, PaysForRBFSource code, supports part of it
std::optional<std::string> PaysForRBF(CAmount original_fees,
PaysForRBF declaration, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/policy/policy.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/policy/policy.h | grep -nF 'inline constexpr unsigned int DEFAULT_INCREMENTAL_RELAY_FEE{100};'Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 3/3, code 1/1History, hash and citation
TRUC, packages and clustersBuilder
BIP 431 defines TRUC (Topologically Restricted Until Confirmation) transactions: a transaction with version 3 opts into rules that, while it is unconfirmed, allow at most one unconfirmed parent or child, cap its size at 10,000 vB, and cap a TRUC child of an unconfirmed TRUC parent at 1,000 vB.18: open 3 sources
FactBuilderEstablishedHigh confidence
T1BIP 431, Topology Restrictions for PinningBIP, says this directly
An unconfirmed TRUC transaction cannot have more than 1 unconfirmed descendant.
Specification, rule 3, read 2026-11-20
T1BIP 431, Topology Restrictions for PinningBIP, says this directly
A TRUC transaction cannot have a sigop-adjusted virtual size larger than 10,000 vB.
Specification, rule 4, read 2026-11-20
T1Bitcoin Core src/policy/truc_policy.hSource code, says this directly
inline constexpr int64_t TRUC_CHILD_MAX_VSIZE{1000};
TRUC_CHILD_MAX_VSIZE, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/policy/truc_policy.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/policy/truc_policy.h | grep -nF 'inline constexpr int64_t TRUC_MAX_VSIZE{10'"'"'000};'bitcoin/bitcoin at f498a5a671 contains this text in src/policy/truc_policy.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/policy/truc_policy.h | grep -nF 'inline constexpr int64_t TRUC_CHILD_MAX_VSIZE{1000};'BIP 431's Title is "Topology Restrictions for Pinning" on the default branch.
Run it yourself
curl -s https://raw.githubusercontent.com/bitcoin/bips/master/bip-0431.mediawiki | grep -m1 -E '^ *Titles?:'Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 3/3, code 3/3History, hash and citation
Since Bitcoin Core 28.0, version 3 transactions are standard on all networks, subject to the opt-in TRUC (Topologically Restricted Until Confirmation) policy of BIP 431 (Bitcoin Core PR #29496).19: open 2 sources
EventBuilderEstablishedHigh confidence
T1Bitcoin Core 28.0 release notesRelease notes, says this directly
Transactions with version number set to 3 are now treated as standard on all networks (#29496),
Mempool policy changes, TRUC (#29496), read 2026-11-20
T1Bitcoin Core src/policy/truc_policy.hSource code, supports part of it
inline constexpr decltype(CTransaction::version) TRUC_VERSION{3};
TRUC_VERSION, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/policy/truc_policy.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/policy/truc_policy.h | grep -nF 'inline constexpr decltype(CTransaction::version) TRUC_VERSION{3};'Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 2/2, code 1/1History, hash and citation
Since Bitcoin Core 28.0, a node that receives a transaction paying too low a fee rate for its mempool can pair it with a child transaction and evaluate both as a package (1-parent-1-child package relay), so a child can pay for a parent that would otherwise be rejected. The release notes call this feature limited and not yet reliable under adversarial conditions.20: open 4 sources
How it worksBuilderEstablishedHigh confidence
T1Bitcoin Core 28.0 release notesRelease notes, says this directly
Transactions having a feerate that is too low will be opportunistically paired with
P2P and network changes, package relay (#28970), read 2026-11-20
T1Bitcoin Core 28.0 release notesRelease notes, says this directly
Warning: this P2P feature is limited (unlike the `submitpackage` interface, a child with multiple unconfirmed parents is not supported) and not yet reliable under adversarial conditions.
P2P and network changes, package relay (#28970), warning, read 2026-11-20
T2Bitcoin Optech topic, Package relayBitcoin Optech, supports part of it
Package relay is a proposed feature for Bitcoin relay nodes that would allow them to send and receive packages
Topic summary, read 2026-11-20
T1Bitcoin Core 30.0 release notesRelease notes, supports part of it
Opportunistic 1-parent-1-child package relay has been improved to handle
P2P, 1p1c improvement (#31385), read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 4/4History, hash and citation
Bitcoin Core 31.0, published on 19 April 2026, reimplemented the mempool as a "cluster mempool": it groups connected unconfirmed transactions into clusters, by default at most 64 transactions and 101 kvB each, and drops the earlier ancestor and descendant limits.21: open 4 sources
EventBuilderEstablishedHigh confidence
T1Bitcoin Core 31.0 release notesRelease notes, says this directly
limiting clusters to 64 transactions and up to 101 kB in virtual size.
Mempool, cluster limits, read 2026-11-20
T1Bitcoin Core 31.0 release notesRelease notes, says this directly
The mempool no longer enforces ancestor or descendant size/count limits.
Mempool, ancestor and descendant limits, read 2026-11-20
T1Bitcoin Core 31.0 release announcementRelease notes, supports part of it
Bitcoin Core 31.0 was published on April 19, 2026.
Release page header, read 2026-11-20
T2Bitcoin Optech NewsletterBitcoin Optech, supports part of it
Bitcoin Core #33629 completes the cluster mempool implementation by partitioning the mempool into clusters
Notable code changes, Bitcoin Core, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/policy/policy.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/policy/policy.h | grep -nF 'inline constexpr unsigned int DEFAULT_CLUSTER_LIMIT{64};'bitcoin/bitcoin at f498a5a671 contains this text in src/policy/policy.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/policy/policy.h | grep -nF 'inline constexpr unsigned int DEFAULT_CLUSTER_SIZE_LIMIT_KVB{101};'Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 4/4, code 2/2History, hash and citation
Pinning and cluster mempool designResearcher
Transaction pinning is when an attacker exploits limits in mempool relay policy to stop an incentive-compatible transaction from being accepted or fee-bumped. BIP 431's TRUC rules (also called version 3 transaction relay) were designed to make pinning harder for contract protocols such as Lightning, where parties sign time-sensitive transactions to broadcast later.22: open 4 sources
DefinitionResearcherEstablishedHigh confidence
T1BIP 431, Topology Restrictions for PinningBIP, says this directly
malicious actors may sometimes exploit limitations to prevent incentive-compatible transactions
Motivation, read 2026-11-20
T1BIP 431, Topology Restrictions for PinningBIP, says this directly
Pinning is consequential to contracting protocols in which untrusted parties construct and sign time-sensitive transactions to be broadcast on-chain later
Motivation, contracting protocols, read 2026-11-20
T2Bitcoin Optech topic, Version 3 transaction relayBitcoin Optech, supports part of it
Combined with package relay, these policies help enable the use of dynamic feerates with LN onchain transactions.
Topic summary, read 2026-11-20
T2Bitcoin Optech topic, Version 3 transaction relayBitcoin Optech, says this directly
designed to prevent pinning attacks.
Topic summary, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 4/4History, hash and citation
Since Bitcoin Core 31.0, a replacement is accepted only if the mempool's feerate diagram is strictly better afterward, a check performed by the function ImprovesFeerateDiagram, declared in src/policy/rbf.h. The release notes say this eliminates all known cases where replacements left the mempool worse off.23: open 3 sources
TraceResearcherEstablishedHigh confidence
T1Bitcoin Core 31.0 release notesRelease notes, says this directly
This eliminates all known cases of replacements occurring that make the mempool worse off, which was possible
Mempool, RBF rule changes, read 2026-11-20
T2Bitcoin Core doc/policy/mempool-replacements.mdDocumentation, says this directly
The feerate diagram of the mempool must be strictly improved by the replacement transaction.
Rule 6, read 2026-11-20
T1Bitcoin Core src/policy/rbf.h, ImprovesFeerateDiagramSource code, says this directly
The replacement transaction must improve the feerate diagram of the mempool.
ImprovesFeerateDiagram declaration, read 2026-11-20
bitcoin/bitcoin at f498a5a671 contains this text in src/policy/rbf.h, and still does on the default branch.
Run it yourself
git clone https://github.com/bitcoin/bitcoin && git -C bitcoin show f498a5a6718d9157b6afb85412c3462439117702:src/policy/rbf.h | grep -nF 'ImprovesFeerateDiagram(CTxMemPool::ChangeSet& changeset);'Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 3/3, code 1/1History, hash and citation
Bitcoin Core 31.0 removed the CPFP carve-out, which had let one extra small child join a package already at its descendant limit. The release notes say contract protocols needing similar behavior are expected to use TRUC transactions and sibling eviction instead.24: open 2 sources
EventResearcherEstablishedMedium confidence
T1Bitcoin Core 31.0 release notesRelease notes, says this directly
The CPFP carveout allowed one additional child transaction to be added to a package that's already at its
Mempool, CPFP carveout, read 2026-11-20
T1Bitcoin Core 31.0 release notesRelease notes, says this directly
It is expected that smart contracting use-cases requiring similar functionality employ TRUC transactions
Mempool, CPFP carveout, read 2026-11-20
Checked at block 976,759, 20 Nov 2026, 17:28 UTC: quotes 2/2History, hash and citation