Bitcoin developers urge to abandon Replace-by-Fee: the feature is outdated and threatens privacy
A debate is heating up in the Bitcoin developer community regarding the continued use of the Replace-by-Fee (RBF) feature in wallets. This mechanism, which historically allowed users to increase the fee for an already sent but unconfirmed transaction (still in the mempool), is being viewed as an anachronism that creates privacy issues.
The key argument against RBF is its redundancy after the Bitcoin network has almost completely transitioned to full-RBF mode. In this mode, any node by default accepts a transaction replacement with a higher fee, making the special BIP-125 signal optional.
Moreover, the outdated RBF flag in transactions creates a serious vulnerability for user privacy. By analyzing network traffic, attackers can determine with high accuracy which specific wallet the sender used. This "digital fingerprint" allows linking previously anonymous addresses and building behavioral profiles.
What Developers Propose
As part of the discussion, it is proposed to completely remove support for the BIP-125 signal from client software. This will simplify wallet code, enhance their security, and eliminate a source of metadata leakage. Instead, users who want to speed up a transaction are advised to use other methods—such as CPFP (Child Pays for Parent), which does not leave such traces.
My analysis: The initiative is completely logical in the context of Bitcoin's evolution. Full-RBF has already become the de facto standard, and retaining the old mechanism only breeds privacy attacks. Removing RBF is a step toward a cleaner and more secure protocol, where every byte of data does not reveal unnecessary information. However, the community will have to overcome inertia: many popular wallets still use the old signal by default.