Replace-by-Fee (RBF) is a Bitcoin transaction replacement policy that lets a wallet broadcast a higher-fee transaction which conflicts with an earlier, unconfirmed transaction. A node may accept the replacement if it satisfies that node’s current mempool rules; RBF is transaction-relay policy, not a Bitcoin consensus rule. 12
| Proposal | BIP 125 was assigned on December 4, 2015; Bitcoin Core 0.12.0 introduced its opt-in replacement policy in 2016. 15 |
|---|---|
| Specification | BIP 125 specification |
| Current node policy | Bitcoin Core replacement policy |
| Directory | Bitcoin Directory |
How Replace-by-Fee works
A Bitcoin transaction spends earlier outputs. Two unconfirmed transactions conflict when they try to spend at least one of the same inputs. With RBF, a wallet creates and broadcasts a new transaction that conflicts with the original and offers a higher fee. The new transaction may adjust the payment or change output as well as the fee; it does not edit or erase the transaction already sent. 4
Each node decides independently whether to keep the original, accept the replacement, and relay it onward. Bitcoin Core’s current replacement policy requires, among other conditions, that the replacement pay at least the combined absolute fees of the transactions it replaces and enough additional fee to cover the bandwidth cost of relaying it. The policy also applies limits to the conflicting transaction cluster and evaluates whether the replacement improves the mempool’s feerate ordering. These are software policy rules and can change between versions or differ across nodes; they are not requirements that every miner or node must share. 2
BIP 125 describes the earlier opt-in signaling policy, including signaling through an input sequence value. Bitcoin Core 28.0 later changed its default full-RBF setting to enabled, but that is a software policy choice, not a network-wide consensus change. Other node software, versions, wallets, and payment services may behave differently, so a signal or wallet setting is not a guarantee that every participant will relay or accept a replacement. 126
RBF and CPFP compared
| Method | What changes | Typical use |
|---|---|---|
| RBF | A new transaction replaces a conflicting unconfirmed one and pays a higher fee. | The sender’s wallet can create a replacement that satisfies node policy. |
| Child Pays for Parent (CPFP) | A new child transaction spends an output from the low-fee parent and adds a fee to the package. | A recipient or another output owner can sometimes raise the combined package feerate without replacing the parent. |
These methods are complementary, but neither guarantees confirmation. CPFP depends on having an output that can be spent and on package handling by the wallet, node, and miner involved. See Child Pays for Parent (CPFP) for the related mechanism. 3
Why it matters and practical limits
RBF gives a sender a way to respond when a transaction is waiting with a fee that is no longer competitive. It can also correct some transaction details before confirmation, depending on the wallet. A wallet may need to build a replacement from the original inputs, preserve enough value for the intended payment, and satisfy the node’s fee and conflict rules.
Because an unconfirmed transaction can be replaced under some policies, a merchant or recipient should not treat an unconfirmed RBF-eligible payment as final. Waiting for confirmation reduces replacement risk, although confirmation is still subject to Bitcoin’s normal settlement considerations. Users should review the replacement’s outputs and total fee in their wallet before authorizing it. RBF does not reverse a confirmed payment, guarantee a faster confirmation, or let someone spend coins they do not control.
History
- 2015 — BIP 125, “Opt-in Full Replace-by-Fee Signaling,” was assigned and proposed a standard way for transactions to signal replaceability. 1
- 2016 — Bitcoin Core 0.12.0 introduced opt-in transaction replacement, using the policy described in BIP 125. 5
- 2024 — Bitcoin Core 28.0 changed its default full-RBF setting to enabled and added limited package RBF. These changes affect that software’s policy; they did not change Bitcoin consensus rules. 6
Related Terms
Related Articles
- What Happens to Bitcoin Mining Rewards After New BTC Issuance Ends?
- Bitcoin as Collateral: Bank Loans, Mortgages, and DeFi Explained
- What the 2024 U.S. Spot Bitcoin ETP Launch Changed—and What It Didn’t
- Why Bitcoin Can Move With Stocks—and Why Correlation Changes
See Also
Page updated: November 10, 2026.
Sources
- Bitcoin Improvement Proposals. “BIP 125: Opt-in Full Replace-by-Fee Signaling.” Assigned December 4, 2015. Accessed November 10, 2026. https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki.
- Bitcoin Core Developers. “Mempool Replacements.” Bitcoin Core documentation. GitHub. Accessed November 10, 2026. https://github.com/bitcoin/bitcoin/blob/master/doc/policy/mempool-replacements.md.
- Bitcoin Core Developers. “Package Mempool Accept.” Bitcoin Core documentation. GitHub. Accessed November 10, 2026. https://github.com/bitcoin/bitcoin/blob/master/doc/policy/packages.md.
- Bitcoin Developer Guide. “Transactions.” Accessed November 10, 2026. https://developer.bitcoin.org/devguide/transactions.html.
- Bitcoin Core Developers. “Bitcoin Core 0.12.0 Release Notes.” GitHub. Accessed November 10, 2026. https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.12.0.md.
- Bitcoin Core Developers. “Bitcoin Core 28.0 Release Notes.” GitHub. Accessed November 10, 2026. https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-28.0.md.