2026-11-20-seed-fees-and-mempool
Published
25 claims
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- Bitcoin blocks have limited space: a consensus rule caps each block at 4,000,000 weight units. Because more transactions can be waiting than fit in the next block, users attach fees to compete for inclusion, and transactions paying higher fee rates are generally mined first.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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).
Held for the owner
Their text stays private until the owner approves it.
- 12 claims on fees-and-mempool
contested subject; contested status; an argument; names Luke Dashjr; names Chris Guida; names Jason Hughes; names Antoine Poinsot; names Pieter Wuille; names Suhas Daftuar
Rejected
6 candidates
- Peter Todd's Bitcoin Core PR
research: Kept the debate to three attributed arguments per side for balance; the PR was fetched and could become an argument claim later.
- Bitcoin Knots disables -permitbaremultisig by default while Bitcoin Core enables it.
research: Verified in code but out of the OP_RETURN scope; a candidate for a later Knots-versus-Core policy topic.
- Bitcoin Core 30.0 lowered -blockmintxfee to 0.001 sat/vB.
research: Supported by the 30.0 release notes but secondary; left out to keep the claim count focused.
- Bitcoin Core 29.0 introduced ephemeral dust (one zero-value output in a zero-fee transaction spent in the same package).
research: Supported by release notes, but it needs its own claims on P2A and ephemeral anchors to be useful.
- BIP 110 and other consensus proposals restricting data.
research: Consensus proposals are outside this topic's relay-policy scope; they belong on their own proposal pages.
- Optech's summary that Pieter Wuille argued blocks are full whether or not they contain data, so storage needs are similar either way.
research: Could not tie the Optech sentence to a specific Wuille message I fetched, so I did not attribute it.
Could not settle
- Whether Bitcoin Knots counts the 83-byte -datacarriersize the same way Bitcoin Core counts it (Knots has -datacarrierfullcount and -datacarriercost). Reading Knots' policy.cpp at 5811235e would settle it.
- Whether Bitcoin Core's MemPoolFeeRateEstimator (src/policy/fees/mempool_estimator.h) is used by estimatesmartfee by default. Reading estimator_man.cpp and the release notes that introduced it would settle it.
- The PR
- How much differing relay defaults between Bitcoin Core 30+ and Bitcoin Knots change which data-carrying transactions reach miners, and how fast. Propagation measurements across node populations would settle it.
Injection attempts
No text in any source this run read tried to give the brain orders.
Read
45 sources
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/policy/policy.h
Core relay defaults (min relay fee, incremental fee, cluster limits, MAX_OP_RETURN_RELAY)
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/kernel/mempool_options.h
maxmempool and mempoolexpiry defaults
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/consensus/consensus.h
MAX_BLOCK_WEIGHT and WITNESS_SCALE_FACTOR
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/consensus/tx_verify.cpp
fee as inputs minus outputs
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/policy/truc_policy.h
TRUC constants
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/policy/rbf.h
PaysForRBF, ImprovesFeerateDiagram, MAX_REPLACEMENT_CANDIDATES
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/policy/fees/block_policy_estimator.h
fee estimator description
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/policy/fees/mempool_estimator.h
newer mempool-based estimator (not used in claims, see open)
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/wallet/rpc/spend.cpp
bumpfee help text
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/doc/policy/README.md
definition of relay policy versus consensus
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/doc/policy/mempool-replacements.md
current replacement rules
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/doc/release-notes/release-notes-28.0.md
full-RBF default, TRUC standardness, 1p1c package relay
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/doc/release-notes/release-notes-29.0.md
removal of -mempoolfullrbf, ephemeral dust
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/doc/release-notes/release-notes-30.0.md
datacarrier changes, 0.1 sat/vB relay fee, TRUC wallet support
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/doc/release-notes/release-notes-31.0.md
cluster mempool, feerate-diagram RBF, CPFP carve-out removal
- https://bitcoincore.org/en/releases/28.0/
release date
- https://bitcoincore.org/en/releases/30.0/
release date
- https://bitcoincore.org/en/releases/31.0/
release date
- https://raw.githubusercontent.com/bitcoinknots/bitcoin/5811235e3f5da687de1ac8ca731331a2fc24a350/src/policy/policy.h
Knots policy defaults
- https://raw.githubusercontent.com/bitcoinknots/bitcoin/5811235e3f5da687de1ac8ca731331a2fc24a350/src/node/mempool_args.cpp
Knots -datacarriersize default wiring
- https://raw.githubusercontent.com/bitcoinknots/bitcoin/5811235e3f5da687de1ac8ca731331a2fc24a350/src/init.cpp
Knots option help text
- https://bitcoinknots.org/
current Knots version (29.5.knots20260508); not cited
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0125.mediawiki
opt-in RBF signaling and rules
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0141.mediawiki
weight, virtual size and block weight limit
- https://raw.githubusercontent.com/bitcoin/bips/a7f91321f25b5be8d93e901775621c21519e80b7/bip-0431.mediawiki
TRUC rules and pinning motivation
- https://bitcoinops.org/en/topics/replace-by-fee/
RBF definition and full-RBF history
- https://bitcoinops.org/en/topics/cpfp/
CPFP definition
- https://bitcoinops.org/en/topics/fee-estimation/
fee estimation background
- https://bitcoinops.org/en/topics/package-relay/
package relay definition
- https://bitcoinops.org/en/topics/version-3-transaction-relay/
TRUC and pinning
- https://bitcoinops.org/en/topics/cluster-mempool/
cluster mempool background
- https://bitcoinops.org/en/newsletters/2025/11/28/
Bitcoin Core
- https://bitcoinops.org/en/newsletters/2025/05/02/
Optech summary of the OP_RETURN thread
- https://delvingbitcoin.org/t/393.json
Suhas Daftuar's cluster mempool overview
- https://mempool.space/docs/faq
user-level explanations; no longer cited because the page renders client-side and the quote checker could not read its text
- https://developer.bitcoin.org/devguide/p2p_network.html
memory pool definition (replaces the mempool.space FAQ)
- https://raw.githubusercontent.com/bitcoin/bitcoin/f498a5a6718d9157b6afb85412c3462439117702/src/txmempool.h
CTxMemPool doc comment, TrimToSize and GetMinFee comments for the mempool definition and full-mempool eviction
- https://api.github.com/repos/bitcoin/bitcoin/pulls/32406
PR that uncapped datacarrier
- https://api.github.com/repos/bitcoin/bitcoin/pulls/32359
Peter Todd's earlier PR, closed unmerged on 12 May 2025
- https://bitcoincore.org/en/2025/06/06/relay-statement/
contributors' statement on relay policy
- https://mailing-list.bitcoindevs.xyz/bitcoindev/rhfyCHr4RfaEalbfGejVdolYCVWIyf84PT2062DQbs5-eU8BPYty5sGyvI3hKeRZQtVC7rn_ugjUWFnWCymz9e9Chbn7FjWJePllFhZRKYk=@protonmail.com/
Antoine Poinsot's opening message and thread index
- https://mailing-list.bitcoindevs.xyz/bitcoindev/03be4934-f0ff-4b58-880d-861d63a4f970@dashjr.org/raw
Luke Dashjr's reply
- https://mailing-list.bitcoindevs.xyz/bitcoindev/f4f6831a-d6b8-4f32-8a4e-c0669cc0a7b8n@googlegroups.com/raw
Jason Hughes's reply
- https://mailing-list.bitcoindevs.xyz/bitcoindev/QMywWcEgJgWmiQzASR17Dt42oLGgG-t3bkf0vzGemDVNVnvVaD64eM34nOQHlBLv8nDmeBEyTXvBUkM2hZEfjwMTrzzoLl1_62MYPz8ZThs=@wuille.net/raw
Pieter Wuille's reply
- https://mailing-list.bitcoindevs.xyz/bitcoindev/CAAANnUy08NBOq3B++80Rpna2qkD6NJV9RdV9v0Oi8c3G8eq_4g@mail.gmail.com/raw
Chris Guida's reply