Bitcoin developers propose abandoning Replace-by-Fee: a step towards complete privacy or technical cleanup?
The Bitcoin developer community has initiated an important discussion: it is proposed to completely abandon the Replace-by-Fee (RBF) function in wallets. This mechanism, which for a long time served as a tool for accelerating transactions by increasing the fee in the mempool, is now considered outdated and potentially dangerous for user privacy.
After the network switched to full-RBF mode, the BIP-125 standard, which formalized this capability, became redundant. The essence of the problem is that the old version of the function allows external observers to track which specific wallet the sender used. This creates serious privacy risks: attackers can analyze transaction replacement patterns to de-anonymize network participants.
From a technical standpoint, abandoning RBF will simplify wallet code and reduce the load on the mempool, as the need to process multiple versions of the same transaction will disappear. However, this decision is not without controversial aspects. For many users, RBF remained a convenient way to "catch up" with an outgoing block if they accidentally set too low a fee. Without this function, such transactions could get stuck in the mempool indefinitely.
I believe this proposal is a logical step in Bitcoin's evolution. Full-RBF already performs the same task, but more efficiently. However, the community will have to decide whether it is willing to sacrifice convenience for enhanced privacy. If the changes are adopted, it will set an important precedent for reviewing other "legacy" functions of the network.