Bitcoin developers propose to abandon the Replace-by-Fee (RBF) feature — what this means for the network
The Bitcoin developer community has once again raised the question of the advisability of retaining the Replace-by-Fee (RBF) function in wallets. This mechanism, implemented in BIP-125, allowed users to increase the fee for a transaction sitting in the mempool to speed up its confirmation. However, in my opinion, the time has now come when RBF is becoming not just redundant, but also potentially harmful to privacy.
The key argument in favor of removing RBF is the network's transition to full-RBF mode. After the activation of this update, all nodes began accepting new versions of transactions replacing old ones without the need for an explicit signal from the sender. Thus, BIP-125 has lost its original function: now any node can process replacements, and a special flag in the wallet is no longer needed.
Moreover, the outdated RBF function creates a serious vulnerability for confidentiality. By analyzing the presence or absence of an RBF signal in a transaction, attackers can determine with high accuracy which specific wallet the sender used. This is especially critical amid growing regulatory attention to tracking fund flows.
What does this mean for users?
Removing RBF from wallets will simplify client software and increase the level of transaction anonymity. However, it is worth considering that without this function, users will lose the ability to "catch up" their transfers if they initially set too low a fee. In the era of full-RBF, this is compensated by the fact that miners can still select transactions with higher fees if they arrive through other channels.
My expert assessment: Removing RBF is a logical step in the evolution of the Bitcoin network. It reduces the attack surface for privacy and decreases code complexity. However, users should be more careful when setting fees, as the ability to "fix" a transaction via RBF will disappear. I recommend using wallets with dynamic fee estimation and, if necessary, applying protocols like CPFP (Child Pays for Parent) to speed up confirmations.