Bitcoin developers are pushing to remove explicit replace-by-fee (RBF) signaling from wallet software, arguing the feature has become redundant now that full-RBF is standard network policy and creates unnecessary on-chain fingerprints that can reveal which wallet was used for a transaction.

Market Context

The move comes as Bitcoin's network infrastructure continues to evolve toward greater privacy and efficiency. Full-RBF—treating all transactions as replaceable at higher fees by default—was adopted as standard policy, eliminating the need for users to manually opt into the replacement mechanism when initiating transactions.

RBF signaling first gained traction years ago as a helpful tool for users looking to speed up stuck transactions. By flipping a switch in their wallet, users could signal they might want to "fee-bump" later if network congestion caused delays. The higher fee served as an incentive for miners to prioritize the replacement transaction.

Analysis

The core issue is that explicit RBF signaling has become vestigial code. Since every transaction on the network now handles replacements automatically regardless of opt-in status, the legacy flag serves no functional purpose while simultaneously leaving digital fingerprints of the wallet software involved in each transaction.

Developer rkrux outlined the proposal on Bitcoin's developer mailing list, stating: "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."

The challenge lies in implementation. Simply removing the signal isn't as straightforward as deleting a checkbox—the sequence number field must contain a value. Community participant Murch explained that "every sender has to pick a sequence for every input," meaning wallets cannot simply leave the field empty.

If different wallets remove RBF signaling inconsistently, transactions processed through various software would appear distinct on-chain, making them easier to track rather than harder. This creates a camouflage problem where divergent removal approaches would actually reduce privacy instead of improving it.

Key Numbers

- Approximately 75% of Bitcoin transactions already use the MAX-2 sequence number as their default input sequence

- BIP 125 is the Bitcoin Improvement Proposal that originally defined opt-in RBF signaling rules

- Full-RBF adoption means all transactions are now treated as replaceable by default, regardless of explicit signaling

What to Watch

Developers are coordinating on a common default input sequence number—likely the already dominant MAX-2—so that transactions from different wallets appear similar on-chain and resist fingerprinting. The Bitcoin Core wallet PR removing BIP 125 RBF signaling remains under discussion, with community members emphasizing the need for consensus on which sequence number becomes the universal standard.

The outcome will set a precedent for how the Bitcoin network handles legacy features as they become obsolete, potentially informing future protocol-level changes aimed at enhancing privacy and reducing unnecessary data exposure.