Why it exists
BIP 125 describes the original opt-in replace-by-fee policy. It lets a wallet signal that an unconfirmed transaction may be replaced, providing a way to raise its fee instead of waiting indefinitely. Replacement concerns node mempools; it does not reverse a confirmed payment.
How it works
Under the original scheme, an input with nSequence below 0xfffffffe signals replaceability. Descendants can inherit that signal from an unconfirmed ancestor. A replacement conflicts with an existing transaction by spending at least one of the same inputs.
The historical rules also constrain fees and the transactions being evicted, to make replacement costly enough to deter bandwidth abuse. Modern nodes have evolved beyond that exact policy. A wallet’s fee-bump workflow must construct and sign a valid replacement and satisfy the policy of the nodes that relay it.
A practical example
Suppose a wallet has an unconfirmed transaction paying a merchant 100,000 sats and a 500-sat fee. It could reduce its own change by 1,000 sats to offer a 1,500-sat fee while leaving the merchant’s output unchanged. Whether that replacement propagates depends on current fee and mempool conditions.
What to keep in mind
An absent opt-in signal is not a guarantee against replacement. A replacement can also change recipients, so an unconfirmed receipt should not be mistaken for final settlement. A higher fee improves incentives, not certainty about the next block.
Status & implementation
BIP 125 is Deployed as a historical policy specification. Core 28 enabled full-RBF by default; Core 31 evaluates replacements using cluster feerate diagrams. Its original five rules are not a complete description of current Core behaviour.
Specification status: Deployed · Sources checked 13 November 2026
