Bitcoin developers are discussing removing the explicit Replace-by-Fee (RBF) signal from wallet software. As full-RBF has become the network’s standard policy, this old marker no longer serves a core function and may instead expose additional wallet characteristics.
The old tag has become redundant.
RBF was originally designed to allow higher fees to be added during transaction congestion, replacing older transactions with new ones to secure faster confirmation. In the past, this capability typically required wallets to first send a clear signal indicating that the transaction is replaceable.
However, full-RBF is now widely regarded as the default network policy. Nodes generally accept replacement transactions with higher fees, regardless of whether users explicitly opted in. Developers therefore believe it is no longer practically necessary for wallets to retain such explicit markings.
On-chain fingerprint issues are emerging
Developers are more concerned about privacy implications. The old RBF signaling caused different wallets to leave identifiable differences on the blockchain, making it easier for external observers to determine which wallet software a transaction originated from.
Bitcoin developer rkrux stated on the mailing list that the Bitcoin Core wallet intends to remove BIP 125-based RBF signaling, primarily because this mechanism has become redundant since the adoption of full-RBF.
The wallet community plans to standardize the values.
However, removing a signal does not equate to directly deleting a field. Every input in a Bitcoin transaction must include a sequence value, and wallets cannot leave it blank. If different wallets use different approaches, new on-chain fingerprints will still emerge.
Community participant Murch stated that each sender must choose a sequence value for each input, so the key is not just to cancel old signals, but to encourage different wallets to adopt similar default practices.
Developers are currently trending toward coordinating and standardizing default input sequence values. Murch notes that approximately 75% of transactions already use a specific encoding, with MAX-2 being the most common. If more wallets adopt this mainstream default, on-chain transactions will appear more similar and become harder to track and distinguish.