CoinDesk
Bitcoin developers are coordinating on a code change to remove the legacy Replace-by-Fee (BIP 125) signaling flag from wallet software, on the grounds that full-RBF has been standard mempool policy for some time and the opt-in bit no longer changes how miners treat a transaction. With the signal now redundant, every wallet that still sets it is effectively stamping an extra piece of identifying metadata into the transaction, narrowing the field of which software authored the spend.
The proposal surfaced on the Bitcoin developer mailing list from contributor rkrux, who noted the explicit BIP 125 flag is on its way out of Bitcoin Core because the network already replaces any transaction at a higher fee by default. The leftover signal, in other words, is a fingerprint with no remaining functional purpose.
Why it matters
The technical catch is that the signal field cannot simply be left blank: every input requires a sequence number, so wallets that each pick a different default would make their transactions look distinct on-chain, the opposite of the privacy goal. Community participant Murch pointed out that about 75% of transactions already settle on one specific sequence value, mostly MAX-2, so the cleanest move is for the rest of the wallet ecosystem to converge on that same default rather than invent new ones.
The wider read is that Bitcoin's wallet layer is being slowly forced to behave like a single piece of software at the protocol level. Standardizing on a shared input sequence number is a small but concrete step toward making user transactions less trivially attributable to a specific wallet vendor, which matters as on-chain analytics firms continue to refine clustering heuristics.
Market impact
There is no direct price or flow implication; the change lives entirely in wallet defaults and BIP-level coordination, not in consensus rules. The downstream effect is a marginal reduction in the wallet-attribution surface for surveillance companies and a quieter standardization of how a "vanilla" Bitcoin transaction looks in 2026, both of which Bitcoin Core contributors have framed as long-overdue housekeeping rather than a protocol overhaul.
Frequently asked questions
-
What is Bitcoin's RBF signaling and why are developers removing it?
RBF signaling is the BIP 125 flag a wallet sets to tell the network a transaction can be replaced with a higher-fee version. Developers want to remove it because full-RBF is now standard mempool policy, so the flag no longer changes miner behavior and only acts as a wallet fingerprint.
-
Why can't wallets just leave the RBF signal blank?
The signal sits in a mandatory sequence-number field on every transaction input, so a value has to be chosen. If each wallet picks a different default, transactions become more distinguishable on-chain, which is the opposite of the privacy goal.
-
What sequence number are wallets converging on?
Community discussion points to MAX-2, the value already used by roughly 75% of transactions. Standardizing on that dominant default lets the remaining wallets blend in instead of standing out.
-
Does this change require a Bitcoin consensus rule update?
No. The proposal is a wallet-level and policy-level change inside Bitcoin Core and other wallet software, not a change to consensus rules. Miners and nodes do not need to upgrade for it to take effect.
-
How does removing the RBF signal improve user privacy?
Every wallet that still sets the BIP 125 flag is leaving a small marker of which software authored the transaction. Dropping the signal and aligning on a common input sequence makes transactions less trivially attributable to a specific wallet vendor.
Benjamin Cowen
CryptoSlate
WatcherGuru
Crypto News
Lookonchain