💡 The Plain-English Definition
RBF — Replace-By-Fee — is a mechanism that lets you replace an unconfirmed outgoing Bitcoin transaction with a new version of the same transaction that pays a higher fee, moving it to the front of the queue when the original was too cheap to confirm promptly.
🤔 But Why Though?
Bitcoin fees are set by a market — transactions bid for limited block space. If you send one with a low feerate (the fee per unit of transaction weight, in satoshis per virtual byte) and the mempool — Bitcoin’s waiting room for unconfirmed transactions — then fills up with higher-feerate transactions, yours gets pushed to the back and may wait hours or days. Before RBF, there was no good fix: the transaction was stuck until either the mempool cleared or, in extreme cases, it was dropped entirely after about two weeks.
RBF lets the sender broadcast a replacement transaction that spends the same inputs but pays a higher fee. Nodes that support RBF — now most of them — swap the original for the higher-fee version in their mempools, and miners naturally prefer the more profitable one.
There are two versions. Opt-in RBF (defined in BIP125) requires the original transaction to signal that it’s replaceable — a flag that says “this may be replaced.” Full RBF, on by default since Bitcoin Core 24.0, lets any unconfirmed transaction be replaced whether or not it was flagged, closing a loophole where unflagged transactions could get stuck for good.
The controversy around RBF was about zero-confirmation payments — treating an unconfirmed transaction as “good enough” for a small purchase. Merchants who did that found RBF let a sender reverse an apparently completed payment by replacing it with a version sending the funds elsewhere. The practical answer: for small purchases the risk is low, but for larger amounts, wait for at least one confirmation.
🌍 The Real-World Analogy
Think of RBF like a taxi queue at a busy airport. You join the queue, but it’s barely moving. RBF is the option to walk to the front and pay the waiting driver a premium — your higher offer bumps your earlier low one. The driver goes with whoever pays most. The original queued offer is withdrawn, because you’ve spent the same “taxi voucher” on a better offer.
⚡ So What?
RBF is a practical tool every self-custody user should know. If your outgoing transaction is stuck — check mempool.space to see how congested things are — most modern wallets let you raise the fee with a tap or two. Reach for it when you need faster confirmation and underestimated the feerate at first. The difference from CPFP (Child Pays For Parent, speeding up a stuck incoming transaction with a high-fee child transaction) matters: RBF works on your own outgoing transactions, while CPFP works on incoming ones you didn’t send.
