Bitcoin Core developers move to drop legacy BIP125 RBF signaling
With full-RBF now standard policy, wallets are discussing a shared sequence default to reduce fingerprinting.
Bitcoin wallet developers are moving to remove explicit BIP125 opt-in replace-by-fee (RBF) signaling now that full-RBF is treated as standard network policy. The change is framed as a privacy cleanup, but it requires wallets to converge on a common input sequence number to avoid creating new on-chain fingerprints.
Key Takeaways
- Full-RBF is treated as standard network policy, making explicit BIP125 opt-in RBF signaling in wallets functionally redundant.
- Removing the legacy signal is being pursued to reduce on-chain wallet fingerprinting that can reveal which software created a transaction.
- Bitcoin Core wallet maintainers signaled intent to remove BIP125 RBF signaling for transactions tied to a pull request.
- Sequence numbers are mandatory per input, and one value already dominates roughly 75% of transactions, mostly MAX-2.
Legacy Opt-In RBF Signaling Becomes Redundant Under Full-RBF
Developers are discussing removing explicit opt-in RBF signaling (BIP125) from wallet transactions because the network now treats transactions as replaceable by default under full-RBF policy. In practice, that means the old “opt-in” marker no longer changes what the network will accept, even though wallets have historically used it to indicate a transaction could be fee-bumped.
Developer rkrux wrote on the developer-mailing list: “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,”.
For traders and power users, the functional point is straightforward: if full-RBF is already the baseline policy, keeping an explicit opt-in flag does not add capability. It does, however, keep a distinguishable marker in the transaction template.
Wallet Fingerprinting Risk: Why Developers Want the Signal Gone
The push is explicitly about privacy and traceability. Developers described the legacy signal as an “unnecessary on-chain fingerprint” that can help observers infer which wallet software produced a transaction.
That matters because wallet fingerprinting is a second-order leak. Even if two users behave similarly on fees and UTXO selection, consistent differences in transaction fields can become clustering inputs. Under full-RBF, the opt-in bit stops being a user-facing feature and starts looking like a self-inflicted label.
The market relevance is indirect but real: privacy consistency affects how easily flows can be profiled, and profiling affects everything from surveillance heuristics to how counterparties assess transaction provenance. This is not a throughput upgrade. It is an attempt to remove a low-value identifier now that the network policy has moved on.
Sequence Numbers Are Mandatory, So Wallets Need a Shared Default
Dropping the opt-in signal is not a simple deletion. Bitcoin transactions require an input sequence number for every input, and changing how wallets populate that field can itself become a new fingerprint.
Community participant Murch summarized the constraint: “stopping to signal replaceability makes it sound like it's a matter of dropping a fingerprint, but... every sender has to pick a sequence for every input.”
The implementation risk is fragmentation. If wallets remove BIP125 signaling but diverge on sequence defaults, the ecosystem trades one recognizable pattern for several smaller ones. That would weaken the privacy goal by making minority behaviors stand out more clearly on-chain.
MAX-2 Emerges as the Dominant Candidate for Convergence
Developers are steering toward convergence on the already-common sequence value rather than inventing a new standard from scratch. Murch said about 75% of transactions already use one specific code, “mostly MAX-2,” and argued that blending into the dominant pattern is the best camouflage.
rkrux framed the coordination problem as an ecosystem norm-setting exercise: “The default input sequence number should be the one that's agreed on by the wider wallet community as a best practice,”.
The near-term signals are procedural. The specific Bitcoin Core pull request that removes BIP125 opt-in signaling has not been identified in the packet, and the merge outcome will matter. So will whether other major wallets follow with release notes or commits that both remove explicit signaling and align on the same sequence default. The other open variable is measurement: the ~75% dominance claim is directionally important, but the underlying dataset and time range were not provided, so updated counts would help validate that MAX-2 convergence really means “hide in the crowd.”
The Real Trade-Off Is Privacy Consistency vs. Wallet UX Expectations
I see this as a cleanup that only works if wallets coordinate. Full-RBF being standard policy strips the opt-in flag of functional value, leaving it as a pure identifier. Removing it is the easy part conceptually, but the real test is whether wallets converge on the same sequence behavior so the fingerprint does not just migrate.
The threshold that matters is broad adoption of a shared default, likely MAX-2, alongside a merged Bitcoin Core change. If that holds, the setup starts to look structural rather than narrative-driven because it reduces a persistent on-chain differentiator without breaking fee-bump expectations in practice.
