Option to turn off RBF gone

[BurnedLung]

The option to turn off RBF has seemingly disappeared in the new update (Windows), it was important for me to turn this off for instant processing on certain websites, but now I need to wait for one full confirmation when transacting. Is this a bug?

[1714897425]

1714897425

[1714897425]

1714897425

[nc50lc]

It's not a bug, it's intentionally removed in version 4.4.0.

Here's the commit that removed all "opt-in" rbf related settings and enabled it by default: github.com/spesmilo/electrum/commit/e1dc7d1e6fb2fc5b88195b62cbe1613b252db388
And here's the reasons behind it: https://github.com/spesmilo/electrum/issues/8088

[o_e_l_e_o]

Given that Full RBF support is increasing, then opting out of RBF will soon be a thing of the past anyway, and services which offer instant processing for non-RBF transactions will no longer be able to offer this.

In the meantime, you can always download an older version from here: https://download.electrum.org/

[Yamane_Keto]

The option to turn off RBF has seemingly disappeared in the new update (Windows), it was important for me to turn this off for instant processing on certain websites, but now I need to wait for one full confirmation when transacting. Is this a bug?

With the current situation, even if the transaction does not contain a RBF flag, those sites will not accept payments with zero confirmations.
According to https://fullrbf.mempool.observer there are too many recent transaction that have been bumped using RBF option

In the meantime, you can always download an older version from here: https://download.electrum.org/

It is better to use a wallet that does not support RBF, downloading old versions is not always the best solution.

[dkbit98]

The option to turn off RBF has seemingly disappeared in the new update (Windows), it was important for me to turn this off for instant processing on certain websites, but now I need to wait for one full confirmation when transacting. Is this a bug?

It's not a bug and you can probably still keep older Electrum version (as standalone or portable) in some cases when you need to send transactions without RBF, or just use alternative open source wallets like Sparrow.
Having latest updated version of Electrum is better because they fixed some bugs, but with recent interface changes many people decided to stick with old versions a bit longer.

[BitMaxz]

It is better to use a wallet that does not support RBF, downloading old versions is not always the best solution.

There is no problem using older versions than 4.4.0 I still using them the latest version only has new features added.

The only problem is if he already installed it the wallet encryption is already upgraded and can't able to load it on an older version the only way to restore it is to import it again with seed backup.

How about using coinb.in to make transactions and disable the RBF flag on the advance option to generate unsign hex transaction and sign and broadcast it to Electrum?

[PawGo]

How about using coinb.in to make transactions and disable the RBF flag on the advance option to generate unsign hex transaction and sign and broadcast it to Electrum?

That's pity we must do kind of kung-fu not to lose functionality which was available a few weeks ago. What is more annoying, RBF is off for payments to LN, so it is not like they just deleted piece of code.
There are also other annoying things in the latest releases (modified UI -> "hidden" settings, unconfirmed transactions are merged (!!) etc.).

[nc50lc]

(-snip- unconfirmed transactions are merged (!!)).

May be caused by the setting "Batch unconfirmed transactions" in the 'New Transaction' settings icon.
But the setting was available in the older versions' "Tools->Preferences->Transactions" settings (disabled by default)

How about using coinb.in to make transactions and disable the RBF flag on the advance option to generate unsign hex transaction and sign and broadcast it to Electrum?

Coinb.in does not output "Partially Signed Bitcoin Transaction" (PSBT) so it'll have to be converted first before it can be imported to Electrum;
If not converted to .psbt, Electrum wont be able to sign it and "broadcast" will be clickable regardless of the unsigned status.

If he feel like it's the only way, he can use Bitcoin Core's console/cli while offline so that it won't sync.
Then use this command to convert it: converttopsbt "hex_encoded_unsigned_raw_transaction"

[PawGo]

(-snip- unconfirmed transactions are merged (!!)).

May be caused by the setting "Batch unconfirmed transactions" in the 'New Transaction' settings icon.
But the setting was available in the older versions' "Tools->Preferences->Transactions" settings (disabled by default)

Yes, exactly. I just wonder why, if I have used previous version and had my setting saved, it was ignored and new version by default enables it.
I think we are just a victims of features lost somewhere on the way from highly customized client for fans to simple & user-friendly client for everyone.

[nc50lc]

Yes, exactly. I just wonder why, if I have used previous version and had my setting saved, it was ignored and new version by default enables it.

I don't know if that's a bug (that setting being enabled regardless of the previous setting) in versions between v4.4.1 & v4.4.3
but to test it, I tried the latest version with a fresh config file and Electrum started with "Batch unconfirmed transactions" turned off by default.

To check if they moved the setting to the wallet file which could cause Electrum to ignore the previous setting,
I've enabled the setting and checked the freshly created "config" file if it added a "batch_rbf": true, line, and it did.
So it's still saved in the config file, and with the test above, it's disabled by default.
So if there's a previous setting, it shouldn't change by itself. (unless it's a bug in 4.4.1 or 4.4.2)

To fully test: Reproduce the issue by installing v4.3.4, disable the setting, close, update Electrum and see if it's enabled.