Bitcoin developers propose abandoning the Replace-by-Fee mechanism
A debate is heating up in the Bitcoin community about the advisability of keeping the Replace-by-Fee (RBF) function in wallets. A number of leading developers are proposing to completely abandon this mechanism, which previously allowed users to increase the fee for a transaction already in the mempool.
The essence of the proposal is that after the network transitions to full-RBF — a mode in which all nodes automatically accept transaction replacements with higher fees — the old mechanism described in BIP-125 becomes redundant. Full-RBF is already implemented in Bitcoin Core 26.0 and above, making manual RBF activation in wallets an outdated practice.
Moreover, retaining BIP-125 carries privacy risks. The outdated function allows external observers to easily identify which specific wallet the sender used. This creates a potential vulnerability for transaction deanonymization, contradicting the privacy principles the Bitcoin community seeks to strengthen.
The arguments of those in favor of removing RBF boil down to simplifying the codebase and increasing security. Instead of supporting two competing standards, the network should rely solely on full-RBF, which ensures more predictable mempool behavior and reduces node load.
However, not all market participants agree with this approach. Critics note that a complete abandonment of BIP-125 could limit user flexibility during periods of high network congestion, when the ability to manually increase the fee becomes critically important for transaction confirmation.
My assessment: This proposal is a logical step in the protocol's evolution. Eliminating outdated mechanisms in favor of more efficient standards is a normal process for a mature network. However, the community will need to find a balance between privacy and functionality so as not to alienate users accustomed to manual fee management.