RBF (Replace-By-Fee)
Transactions● Common
A mechanism allowing unconfirmed transactions to be replaced with new versions paying higher fees. Useful for fee bumping stuck transactions. BIP-125 defines opt-in RBF signaling via nSequence. Full RBF (default in Core 28.0+) allows replacing any unconfirmed transaction.
Technical Notes
Signal: nSequence < 0xfffffffe on any input. Replacement must pay higher total fee and higher feerate. Can change outputs (redirect payment). Controversy: breaks zero-conf assumptions for merchants. Full RBF debate resolved in favor of opt-out being unenforceable.
Metadata
Visibility: Public
Created:1/3/2026by System