You have chosen "Preserve payment". This means Electrum will not change the amount(s) you are sending to the output(s) of your transaction, so any additional fee has to come from another input, but your wallet does not currently contain a suitable output which can be used as another input in to your transaction to contribute additional fees.
You have three options if you still want to bump this transaction using RBF:
1 - Send some more coins to this wallet in order to create a suitable output which can be included to bump the fee.
2 - Swap from "Preserve payment" to "Decrease payment". This will reduce the amount(s) being sent to the output(s) of your transaction, and use this money instead to pay a higher fee.
3 - If you want to "Preserve payment" and not have to make an additional transaction as in Option 1, then manually create a transaction including an additional input from elsewhere to pay a higher fee and sign it separately. (You could also do this option by importing all the necessary private keys together in to the same wallet, but this carries the additional risk which comes with handling and importing raw private keys.)
Topic: Electrum 4.4.4 Released (Read 198 times)
I am stuck on 9 sat/vb fee last a couple of days, but I'm not in a hurry.
I believe you can find the explanation for no suitable output error in this forum, for example in this thread[1]. AFAIK, it basically means you don't have any more output to spend to increase the fee. It is not a new change at all. CMIIW.[1] https://bitcointalksearch.org/topic/cannot-bump-fees-on-a-rbf-electrum-2651778
The Electrum development team released a minor upgrade a couple of days ago.
I am not sure this upgrade make an effect on the bump fee transactions, as I remembered a couple of weeks ago when used 4.4.3, I still can bump the fee even if I max the transaction. but today, I can't bump the fee with the same situation, I don't know what happens, or they change the default setting. Thanks
* I am stuck on 9 sat/vb fee last a couple of days, but I'm not in a hurry.
Under Network --> Server Settings --> Uncheck Select server automatically --> Select your preferred server --> Press Ok
That should pick that one server every time you load your wallet.
That will still allow Electrum to pick other nodes to connect to.That should pick that one server every time you load your wallet.
What he meant is same as the "oneserver" setting or command line option which will keep your Electrum connected to a single node, your selected server.
here https://bitcointalksearch.org/topic/is-there-a-way-to-downgrade-electrum-android-wallet-5451215
New updates are pushing users to the importance of privacy and security, but sometimes some of them complicate the user experience.
It's by design and i don't expect it to be reverted. That feature protects users from leaking their seeds to third party keyboard, some of which might be malicious, and I 100% support it. Better safe than sorry. Bitcoin safety first. - https://github.com/spesmilo/electrum/issues/8256New updates are pushing users to the importance of privacy and security, but sometimes some of them complicate the user experience.
How do you force Electrum for Android to only connect to one server? I do not see the options for this version. Maybe it is in an older version and I might have to install that first, set the option, then upgrade to this version. I do not like the app to connect to more than 1 server.
Under Network --> Server Settings --> Uncheck Select server automatically --> Select your preferred server --> Press OkThat should pick that one server every time you load your wallet.
Do you mean in the Android app? TBH that functionality in kivy might have been accidental... What exactly is your use case?
here https://bitcointalksearch.org/topic/is-there-a-way-to-downgrade-electrum-android-wallet-5451215New updates are pushing users to the importance of privacy and security, but sometimes some of them complicate the user experience.
How do you force Electrum for Android to only connect to one server? I do not see the options for this version. Maybe it is in an older version and I might have to install that first, set the option, then upgrade to this version. I do not like the app to connect to more than 1 server.
For the desktop applications, you can edit the config file.
and it will only connect to one server of your choosing.
For the desktop applications, you can edit the config file.
Code:
"oneserver": true,
and it will only connect to one server of your choosing.
As expected, they did not restore the ability to copy wallet seeds without having to type them manually.
Do you mean in the Android app? TBH that functionality in kivy might have been accidental... What exactly is your use case?
As expected, they did not restore the ability to copy wallet seeds without having to type them manually. I heard a lot of complaints from members here about the latest version. I hope this version has solved all the problems because I stopped using Electrum a month ago and I'm thinking of returning to it.
The Electrum development team released a minor upgrade a couple of days ago. It looks like it's mostly fixing some issues with the Android GUI as it relates to creating multi-sig wallets.
Don't forget to verify the download!
Don't forget to verify the download!
# Release 4.4.4 (May 31, 2023)
* QML GUI:
- fix creating multisig wallets involving BIP39 seeds (#8432)
- fix "cannot scroll to open a lightning channel" (#8446)
- wizard: "confirm seed" screen to normalize whitespaces (#8442)
- fix assert on address details screen (#8420)
* Qt GUI:
- better handle some expected errors in SwapDialog (#8430)
* libsecp256k1: bump bundled version to 0.3.2 (10574bb1)
* QML GUI:
- fix creating multisig wallets involving BIP39 seeds (#8432)
- fix "cannot scroll to open a lightning channel" (#8446)
- wizard: "confirm seed" screen to normalize whitespaces (#8442)
- fix assert on address details screen (#8420)
* Qt GUI:
- better handle some expected errors in SwapDialog (#8430)
* libsecp256k1: bump bundled version to 0.3.2 (10574bb1)
Jump to: