Key Takeaways
Bitcoin developers want to remove legacy RBF signaling because full-RBF support has made the feature largely redundant.
Different wallets implement RBF signaling differently, creating transaction fingerprints that can weaken user privacy.
The proposal would not change Bitcoin’s functionality, allowing users to continue speeding up transactions with higher fees.
Why Devs Want to Drop RBF Signaling
Bitcoin developers are discussing a small technical change that they believe could improve privacy for users.
The idea is to remove an old feature called Replace-by-Fee (RBF) signaling from Bitcoin wallets. Developers say the feature is no longer needed and may now reveal extra information about users.
The change would not affect how Bitcoin works. Users would still be able to speed up transactions by paying a higher fee.
Replace-by-Fee, or RBF, helps users when a Bitcoin transaction gets delayed.
When someone sends bitcoin, the transaction waits in a queue before being confirmed. They will get included in blocks based on the fee they pay. During busy periods, transactions with low fees can take longer.
RBF lets users send a new version of the same transaction with a higher fee. Miners usually process the higher-fee transaction faster.
Years ago, wallets had to include a special signal to tell the network that the transaction could later be replaced. That was called an RBF flag.
Developers say that the signal is no longer necessary. In October 2024, Bitcoin Core changed its default settings to support full Replace-by-Fee. This means the network and the majority of nodes already allow unconfirmed transactions to be replaced with higher-fee versions.
As a result, wallets no longer need to send a separate signal. Developer rkrux explained the reason behind the proposal:
“There is an intention in the bitcoin core wallet to remove the BIP 125 RBF signaling in transactions for which a PR is raised. The primary reason for its removal is because ever since full-RBF became a standard policy, this signaling has become redundant.”
In simple terms, the feature still exists in wallets even though the network no longer needs it.
The bigger issue is privacy. Different wallets currently fill in the RBF-related data in slightly different ways. Those small differences appear publicly on the blockchain.
This can allow observers to guess which wallet software created a transaction. Developers call this a fingerprint because it creates small patterns that may help track wallet usage.
The proposal aims to reduce these clues and make transactions look more similar.
Removing the signal sounds easy, but it is more complicated. Bitcoin transactions require a value to stay in that part of the transaction. Wallets cannot simply leave it empty.
If different wallet companies choose different replacement values, new patterns could appear and make tracking easier again.
Community contributor Murch explained that every wallet still has to choose a sequence value, so developers should agree on one common approach. Right now, many developers support using a value called MAX-2.
About 75% of transactions already use MAX-2, which means most wallets already follow that pattern. If more wallets adopt the same value, transactions will become harder to tell apart.
For most Bitcoin users, nothing would change. People would still be able to increase transaction fees and speed up payments when needed. Bitcoin’s rules would stay the same.
The proposal only changes how wallet softwares prepare transactions before sending them. The discussion is still in the early stages and no final decision has been made.
But if developers agree on a shared approach, the update could improve privacy without changing the way users interact with Bitcoin.
100% of the sats go directly to the author
