-
Notifications
You must be signed in to change notification settings - Fork 2.1k
refactor sendTransaction error alerts #664
Comments
I am getting the error "Insufficient funds for gas * price + value”. However, I have a balance of 0.090948 |
Hello, have a same issue insufficient funds for gas * price + value. Any solution? |
Here is the response from MetaMask... Hello, There is currently a combination of both a backlog in pending transactions on the network as well as rising competition for gas prices with CryptoKitties. Unfortunately this is causing some transactions with lower gas prices to take longer to process or even fail. Unfortunately there is little to be done about this besides waiting for any pending transactions to go through or show as failed/rejected. This waiting period can take up to 24 hours during congested network times such as this. For your refernece in using gas with Dapps such as CryptoKitties, Ether Delta and others: https://support.metamask.io/kb/article/25-transaction-submission-best-practices-on-etherdelta-and-dapps/ |
Could "wrong password" error show up upon importing a pre-sale wallet due to any node-related errors? |
Currently "wrong password" error will show up for any node-related error.
We will try to catch the errors by
string
for now. But to ensure consistency and compatibility to other nodes these error codes should be implemented by the nodes.update:
Following strings will be emitted by geth:
could not decrypt key with given passphrase
(wrong password)multiple keys match address
(multiple copies of the same account)Insufficient funds for gas * price + value
(not enough ether in etherbase account to invoke contract transaction)Unable to connect to socket: timeout
(node terminated, etc; used to beCONNECTION ERROR
as in Mist's current code)fixed with PR #959
Additionally there should be a warning if a transaction should deplete the etherbase account to a balance that would not allow to execute transfers from contract wallets.
duplicates:
#368
#866
#869
#875
#923
#926
#948
The text was updated successfully, but these errors were encountered: