Developers propose removing the “replace with a higher fee” button — what that means for miners

The confirmed facts

Changes to wallet software will not reduce miners’ fee revenue — full‑RBF is already standard network policy and the option to replace a transaction with a higher fee remains. The developer rkrux has published a proposal to remove the explicit BIP‑125 RBF signal from the built-in Bitcoin Core wallet, with the goal of eliminating the redundant on‑chain fingerprint that makes it possible to tell which piece of software created a given transaction (the original coverage).

What changed and how we got here

Full‑RBF became standard network policy back in Bitcoin Core v28.0 in October 2024, when the -mempoolfullrbf option was turned on by default. In April 2025 Bitcoin Core v29 removed the option to disable full‑RBF, which made it permanent. In that context the explicit opt‑in BIP‑125 flag has become redundant as a mechanism for signalling that a transaction can be replaced.

rkrux’s proposal (published on the bitcoin‑dev list) addresses exactly that: removing the legacy RBF signal at the wallet level and aligning the way wallets set input sequence numbers (converging on the already dominant MAX‑2), so that transactions from different wallets look more alike and are harder to trace (rkrux’s post).

What this means for miners — economics and practice

• Miners will not lose fee revenue: with full‑RBF policy already established, replacing unconfirmed transactions with a higher fee remains possible and operationally unchanged.

Removing the explicit BIP‑125 flag from the transactions Bitcoin Core generates eliminates a small but constant bit of data in the block — this reduces redundant on‑chain overhead and closes off one source of fingerprinting that analysts and observers used to link transactions to specific wallets. For miners this is a net gain for network privacy, with no direct financial effect on transaction selection.

At a practical level, miners and pools do not need to change the way they accept or order unconfirmed transactions: the validity rules and the fee market remain unchanged at the protocol level. An important practical consequence is that operators should keep their nodes and software up to date, so they do not rely on outdated indicators or side logic that might read the absence of a BIP‑125 flag as a difference in transaction behaviour.

What operators should do — conclusion and the Bitminers assessment

Bitminers assesses this as a piece of technical housekeeping with a positive effect on network privacy and zero negative effect on miners’ fee revenue. Our practical advice:

• Keep your nodes and your mining software / pool software updated to current versions of Bitcoin Core, so you avoid inconsistencies in how transactions are recognised and processed.
• Do not change your tactical transaction-selection policies because of the removal of the explicit RBF flag — transactions with higher fees are still replaced and remain a priority.

The bottom line: this is a small but useful change at the wallet level, one that makes on‑chain fingerprints less informative and does not affect the economics of mining. Miners gain from a more uniform, less traceable network and should treat the change as an administrative maintenance task, not as a reason for an operational change.