Bitcoin Core developers have put forward a proposal to strip redundant Replace-by-Fee (RBF) signaling from wallet software. The idea is to standardize how wallets handle RBF, cutting down on transaction fingerprinting that can undermine user privacy. But the fix comes with a warning: if not everyone gets on board, it could fragment the network.
Inside the proposal
The change targets the explicit signaling that some wallets use to indicate a transaction is replaceable. That signal, while not strictly necessary for the RBF mechanism to work, creates a unique pattern that observers can link to specific wallet implementations. By removing it, all transactions would look more alike—making it harder for chain analysts to single out certain users.
Developers argue the privacy gain is worth the trouble. But they also note that the proposal only works if wallet maintainers across the ecosystem adopt it. Patchwork adoption would leave some transactions marked and others not, potentially creating two classes of privacy.
Why RBF signaling matters
RBF lets a sender bump a stuck transaction by replacing it with a new one with a higher fee. The optional signal, a flag in the transaction data, tells miners and nodes that this transaction can be replaced. Over time, that flag has become a privacy leak. Analytics firms can fingerprint wallets based on whether they use the flag, then correlate that behavior across transactions.
Removing the signal doesn't break RBF—it just makes the replaceability implicit rather than explicit. Nodes and miners would still process replacements, but there'd be no visible marker. The trade-off is a small increase in complexity for full nodes, which would have to assume any transaction might be replaceable.
The fragmentation risk
Not everyone is on board. Some wallet developers worry that dropping the signal could cause unexpected behavior in older software that relies on the flag to detect replaceability. If a major wallet opts out of the change while others adopt it, users of the holdout wallet could end up with transactions that are harder to replace—or that get stuck more often during mempool congestion.
Bitcoin Core's maintainers have acknowledged the risk. They're asking for feedback on the mailing list and plan to review implementation details over the coming weeks. No timeline for a merged patch has been set.
The next concrete step is a formal discussion thread on the Bitcoin-Dev mailing list, expected within the next two weeks. Whether the core developer community can reach consensus—and how quickly wallet makers follow—will determine if this privacy fix actually sticks.
