Bitcoin developers propose to abandon the Replace-by-Fee function
A discussion is gaining momentum in the Bitcoin developer community regarding the advisability of retaining the Replace-by-Fee (RBF) function in wallets. This mechanism, which has long served as a tool for increasing the fee of a transaction in the mempool, may be deemed obsolete and removed from client software.
The key argument in favor of abandoning RBF is related to the network's transition to a full-RBF mode. Since miners and nodes have begun to universally support replacing transactions with higher fees, the initial signal defined by the BIP-125 standard has become redundant. Now that replacement occurs automatically at the network level, explicitly indicating the use of RBF in a wallet loses its practical meaning.
Moreover, as analysis has revealed, the outdated function carries a serious risk to user privacy. The presence of an RBF signal in a transaction allows third-party observers to determine with high accuracy which specific wallet or client the sender used. This reveals information about the software, which can be exploited for deanonymization and profiling of network participants.
From my professional perspective, this proposal is a logical and timely step in the evolution of the protocol. Removing redundant and potentially privacy-threatening elements is not merely a technical simplification, but a necessary condition for enhancing the network's security and anonymity. The market and users should welcome such initiatives aimed at eliminating vulnerabilities that have accumulated over the years. In the long term, abandoning BIP-125 will make Bitcoin more resistant to chain analysis and surveillance.