Bitcoin developers propose removing 'replace-by-fee' transaction feature

Bitcoin developers are proposing to remove the 'replace-by-fee' (RBF) feature, a mechanism that allows users to replace a pending transaction with a new one that includes a higher fee. Introduced in Bitcoin Core version 0.12.0 in February 2016, RBF was designed to offer users flexibility in speeding up transactions or adjusting fees during periods of high network congestion.

However, the feature has become redundant and is now seen by some as a 'fingerprint' for tracking transactions. The proposal to remove RBF comes amid discussions about optimizing the Bitcoin protocol. A recent transaction highlighted the complexities of transaction fees, with a user paying an exceptionally high fee of $3.1 million to transfer 139.42 BTC, a fee that was potentially influenced by RBF or misjudgment.

The RBF policy, formalized in BIP 125, allows senders to signal that their transactions can be replaced. This mechanism is crucial for accelerating stuck transactions by increasing the fee. While RBF is supported by Bitcoin Core, its implementation can vary across different wallets and services. The core principle of RBF is that a new transaction must spend the same inputs as the original and pay a higher fee, with only one of the two transactions ultimately being confirmed.