Bitcoin RBF privacy flag removal targets wallet tracking
Bitcoin RBF is under review in Bitcoin Core PR #35405. A developer proposed removing the legacy BIP125 opt-in Replace-by-Fee (RBF) signaling because full RBF is already the network default, making the old flag redundant.
The privacy issue is that the nSequence field is mandatory. If wallets drop the BIP125 flag without coordinating on a shared default nSequence value, they could create a new on-chain fingerprint that makes wallets easier to identify. Developers highlighted a coordination problem: every wallet must choose a sequence per input.
Community members and wallet developers (including Electrum’s SomberNight) largely favor using MAX-2 as the ecosystem default. Data referenced by Bitcoin Optech suggests MAX-2 is already the dominant nSequence value in roughly 75% of transactions. Switching to MAX-1 was discussed but rejected because it would make transactions visually distinct from the existing majority.
The change preserves fee-bumping functionality for users and keeps full-RBF semantics intact, but it reduces the visibility of “optional replaceability” in transaction structure. Traders should note implications for zero-confirmation (0-conf) merchant workflows: merchants may need to treat any unconfirmed transaction as potentially replaceable under policy.
Overall, the core move is cross-wallet standardization around Bitcoin RBF behavior to reduce wallet fingerprinting while maintaining usability.
Neutral
This is a Bitcoin protocol/wallet-standardization change focused on reducing wallet fingerprinting, not a change to consensus rules or block validity. In the short term, traders are unlikely to see direct effects on BTC price, liquidity, or network security, but there may be localized operational adjustments for wallets and merchant 0-conf handling.
Historically, privacy- or mempool-policy-adjacent proposals (such as RBF-related upgrades or wallet-flag cleanups) tend to affect user behavior and tooling more than markets. The main market impact is usually sentiment around “privacy and usability,” with limited immediate price follow-through unless adoption is uneven or causes interoperability issues.
Longer term, if most wallets converge on the agreed nSequence default (e.g., MAX-2), the network could see fewer privacy leaks and smoother cross-wallet consistency. That could be mildly positive for ecosystem trust. However, because the change is explicitly about signaling structure/visibility while full RBF remains the default, the net expected impact on trading flows is modest—hence neutral.