Bitcoin Forum

Bitcoin => Electrum => Topic started by: Grayman101 on May 01, 2023, 09:01:35 PM



Title: 100%+ fees for sending btc and fees decrease for increased speed?
Post by: Grayman101 on May 01, 2023, 09:01:35 PM
I'm having an issue I've never experienced before with my standard wallet. Every time I try to send coin, regardless of using the mempool, static, or eta sliding scale for the fee, i get an error message because the fee is 100% or more. And when I increase the gas, the rate goes down when it should go up. And goes up when it should go down.
Another weird thing is that all of my previous withdrawals now show a gas fee equal to or greater than the withdrawal amount. Does anyone know what's happening or if my funds are recoverable?

The error type says: bool object is not callable. What does this mean?


Title: Re: 100%+ fees for sending btc and fees decrease for increased speed?
Post by: nc50lc on May 02, 2023, 09:03:48 AM
I'm having an issue I've never experienced before with my standard wallet. Every time I try to send coin, regardless of using the mempool, static, or eta sliding scale for the fee, i get an error message because the fee is 100% or more.
-snip-
This may be caused by the common (non) issue of confusing the unit "mBTC" with "BTC".
Check if you're using the default mBTC while wanting to send at BTC unit.
Example, if you want to send "0.001 BTC" but typed '0.001' while using the 'mBTC' unit, the actual amount would be "0.000001 BTC" which is lower than the lowest possible fee.

If that's the case, you can change the unit in the settings: "Tools->Preferences->Units->Base unit".
If not the case, what's the actual "fee is 100%" message that you're seeing?

-snip- or if my funds are recoverable?
If you actually sent those transactions with very high transaction fee, there's nothing you can do to recover your bitcoins.

The error type says: bool object is not callable. What does this mean?
You'll have to enable logging and check the .log file to see what could've caused it.
Logging can be enabled in "Tools->Preferences->Misc->Write logs to file".
logs can be accessed in "logs" folder inside Electrum's data directory (location (https://electrum.readthedocs.io/en/latest/faq.html#where-is-the-electrum-datadir-located))

But AFAIK, no other users have reported such error.


Title: Re: 100%+ fees for sending btc and fees decrease for increased speed?
Post by: Yamane_Keto on May 03, 2023, 01:58:52 PM

The error type says: bool object is not callable. What does this mean?

Are you sure you have downloaded the wallet from https://electrum.org and Verify GPG signatures, such strange errors could be from scam phishing versions.
Why do you describe fees as gas? The term gas is used in Ethereum.




Title: Re: 100%+ fees for sending btc and fees decrease for increased speed?
Post by: logfiles on May 03, 2023, 09:02:35 PM
Are you sure you have downloaded the wallet from https://electrum.org and Verify GPG signatures, such strange errors could be from scam phishing versions.
Why do you describe fees as gas? The term gas is used in Ethereum.
It's a known bug involving the android mobile app and 2FA enabled wallet and has been reported over 101 time on their GitHub (https://github.com/spesmilo/electrum/issues/8368)
The Developers have already worked on the issue and the next update will have the bug fixed.


Title: Re: 100%+ fees for sending btc and fees decrease for increased speed?
Post by: DaveF on May 03, 2023, 10:54:32 PM
Are you sure you have downloaded the wallet from https://electrum.org and Verify GPG signatures, such strange errors could be from scam phishing versions.
Why do you describe fees as gas? The term gas is used in Ethereum.
It's a known bug involving the android mobile app and 2FA enabled wallet and has been reported over 101 time on their GitHub (https://github.com/spesmilo/electrum/issues/8368)
The Developers have already worked on the issue and the next update will have the bug fixed.

And now 102....
Makes you wonder how a show stopper like that made it into the release.

I saw some separate comments someplace else (reddit? Don't remember) that it can be duplicated without 2fa.

Not sure was not paying that much attention.

-Dave


Title: Re: 100%+ fees for sending btc and fees decrease for increased speed?
Post by: Sinner1605 on May 04, 2023, 01:17:09 PM
I'm having an issue I've never experienced before with my standard wallet. Every time I try to send coin, regardless of using the mempool, static, or eta sliding scale for the fee, i get an error message because the fee is 100% or more.
-snip-
This may be caused by the common (non) issue of confusing the unit "mBTC" with "BTC".
Check if you're using the default mBTC while wanting to send at BTC unit.
Example, if you want to send "0.001 BTC" but typed '0.001' while using the 'mBTC' unit, the actual amount would be "0.000001 BTC" which is lower than the lowest possible fee.

If that's the case, you can change the unit in the settings: "Tools->Preferences->Units->Base unit".
If not the case, what's the actual "fee is 100%" message that you're seeing?

-snip- or if my funds are recoverable?
If you actually sent those transactions with very high transaction fee, there's nothing you can do to recover your bitcoins.

The error type says: bool object is not callable. What does this mean?
You'll have to enable logging and check the .log file to see what could've caused it.
Logging can be enabled in "Tools->Preferences->Misc->Write logs to file".
logs can be accessed in "logs" folder inside Electrum's data directory (location (https://electrum.readthedocs.io/en/latest/faq.html#where-is-the-electrum-datadir-located))

But AFAIK, no other users have reported such error.
have same problem with "bool object is not callable". Wallet was downloaded from Google play market.


Title: Re: 100%+ fees for sending btc and fees decrease for increased speed?
Post by: nc50lc on May 04, 2023, 03:54:00 PM
But AFAIK, no other users have reported such error.
have same problem with "bool object is not callable". Wallet was downloaded from Google play market.
I called this too early.
Please, check the other replies since they found a possibly related issue reported by Android users.
The descriptions are way too far from the issue in this topic though.

The good news is, the error should be fixed in the new release.