Skip to content

Remove opt-in RBF#936

Open
polespinasa wants to merge 1 commit into
bitcoin-core:masterfrom
polespinasa:2026-05-05-remove-optinRBF
Open

Remove opt-in RBF#936
polespinasa wants to merge 1 commit into
bitcoin-core:masterfrom
polespinasa:2026-05-05-remove-optinRBF

Conversation

@polespinasa
Copy link
Copy Markdown
Member

With the whole network mostly running with Full Replace By Fee, it does not make sense to let the user signal or not to signal for RBF on their transactions.

With this PR the transactions created using the GUI will fallback to the wallet configuration in order to signal or not to signal BIP 125. (True by default).

@DrahtBot
Copy link
Copy Markdown
Contributor

DrahtBot commented May 5, 2026

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Reviews

See the guideline for information on the review process.

Type Reviewers
ACK sedited

If your review is incorrectly listed, please copy-paste <!--meta-tag:bot-skip--> into the comment that the bot should ignore.

Comment thread src/qt/sendcoinsdialog.cpp
@polespinasa polespinasa force-pushed the 2026-05-05-remove-optinRBF branch from db677ef to d10a3e6 Compare May 13, 2026 18:45
Remove the option to signal or not signal for BIP 125 (Opt-in Full Replace-By-Fee).
By removing the option in the GUI it will fallback to the wallet configuration which by default is
true unless the user changed it using CLI.
@polespinasa polespinasa force-pushed the 2026-05-05-remove-optinRBF branch from d10a3e6 to 90eda67 Compare May 13, 2026 18:46
Copy link
Copy Markdown
Contributor

@sedited sedited left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK 90eda67

@polespinasa
Copy link
Copy Markdown
Member Author

Failing test seems unrelated

Copy link
Copy Markdown
Member

@hebasto hebasto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the "RPC only" note still correct here:

argsman.AddArg("-walletrbf", strprintf("Send transactions with full-RBF opt-in enabled (RPC only, default: %u)", DEFAULT_WALLET_RBF), ArgsManager::ALLOW_ANY, OptionsCategory::WALLET);
?

Comment on lines +355 to +357
// append RBF message
question_string.append("<span style='font-size:10pt; font-weight:normal;'>");
question_string.append(tr("You can increase the fee later."));
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if Bitcoin Core is run with -walletrbf=0?

Copy link
Copy Markdown
Member Author

@polespinasa polespinasa May 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have to test to ensure there's no random check that blocks the transaction from being broadcasted but it is redundant.

Anyway there is work ongoing towards deprecating and removing it.
bitcoin/bitcoin#34917

Edit: Just checked and it doesn't matter, the wallet still broadcast it, we are not enforcing RBF even if -walletrbf=0. The only difference is the sequence number value, but has no effect.

@polespinasa
Copy link
Copy Markdown
Member Author

Is the "RPC only" note still correct here

Not at all. If this gets merged I can open a follow-up PR to change that line, maybe can just ask to get it modified here bitcoin/bitcoin#34917.
Happens when repos are split 🤷‍♂️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants