- Bitcoin developers want to remove explicit replace-by-fee (RBF) signaling from wallet software because full-RBF is now standard policy, making the old opt-in flag redundant.
- Keeping the legacy RBF signal creates unnecessary on-chain fingerprints that can reveal which wallet software was used.
- Developers are coordinating on a common default input sequence number, likely the already dominant MAX-2, so that transactions from different wallets look similar and are harder to track.
For years, users looking to speed up their transactions on the Bitcoin blockchain relied on a handy optional feature that essentially says, "I might want to replace this transaction with a higher fee."
But what started as a helpful tool has become redundant and a small privacy issue, prompting some developers to discuss possible ways to do away with it.
Let's first take a look at the so-called replace-by-fee (RBF) signaling, then discuss the developers' proposals.
Replace by fee (RBF) signaling
Imagine sending a paper check through the mail, but the postal system is stretched and congested. To ensure your payment doesn't get stuck, the check has a small checkbox that says, "I reserve the right to cancel this check and write a new one with a higher rush fee if it gets delayed." (The higher fee, of course, is an incentive for the postal system to prioritize your transaction.)
Such a feature is called Replace-by-Fee (RBF) in the Bitcoin ecosystem. For years, when you sent bitcoin, your wallet let you flip a switch, signaling to the network that you might want to "fee-bump" to speed up your transaction later.
This optionality became the standard network policy recently. The network by default began treating every transaction as replaceable at a higher fee regardless of whether the user opted in for a replacement.
Because the entire network now handles transaction replacements automatically, the explicit "replace later" signaling in Bitcoin wallets has become redundant — a vestigial piece of code that leaves unnecessary digital fingerprints of the wallet involved in the transaction.
So, developers are proposing a code change to remove this signaling mechanism from the wallet software.
"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," developer rkrux posted to the developer-mailing list.
Camouflage issues
Implementing this requires careful planning because if different wallets delete this replace function in different ways, then transactions processed through these wallets will look distinct on-chain, which makes them easy to track.
Note that removing a signal may sound as simple as removing a sticker off a box or a button from a screen, but that's not the case in Bitcoin, where the signal is a mandatory field that must be filled with a value.
Community participant Murch explained why just deleting it isn't so simple, saying that "stopping to signal replaceability makes it sound like it's a matter of dropping a fingerprint, but... every sender has to pick a sequence for every input."
In other words, wallets can't just have "nothing" there; the code requires you to pick a number. Murch noted that since about 75% of transactions are already using one specific code, mostly MAX-2, the best way to hide is to join them rather than trying differently and stand out.
"The default input sequence number should be the one that's agreed on by the wider wallet community as a best practice," rkrux said.
