Skip to content
This repository has been archived by the owner on Sep 5, 2020. It is now read-only.

Accounts Locked - No transactions getting confirmed or completed (selected one transaction fee too low) #719

Closed
larrysmith1000 opened this issue May 26, 2016 · 7 comments
Milestone

Comments

@larrysmith1000
Copy link

larrysmith1000 commented May 26, 2016

Today, from Mist Ethereum Wallet, I tried to send ether from my contract wallet to my account (the owner of the contract wallet. For the first time, I selected the lowest possible transaction fee, to see how long it would take. The transaction appeared (greyed) in the "latest transactions" list. After about 5 minutes, (~20 blocks), the transaction disappeared from the list, and the transaction was never confirmed or transferred. I checked the blockchain for the transaction with an explorer. No luck. Then the real problem started.

I assumed that the fee I selected was too low, and no miners took it, so I tried to do the transaction again (from my contract wallet to my account), and this time selected a high fee -- The same thing happened. The transaction appeared (greyed in the list), no confirmations came for several blocks, then the transaction disappeared from the list.

I then tried to transfer some ether to The DAO from my contract wallet. Same thing happened.
I then tried to transfer some ether from the owner account to another account (second owner of the Contract Wallet). No luck there either!

It seems that the first transaction I requested is not getting picked up by miners due to me selecting too low of a fee, and with that transaction request still out there, my contract wallet and owner accounts are locked. Has anyone experienced this?

Is there an expiration time for transaction requests? Can I delete the queue of transaction requests? If that first transaction goes through, will all the other ones I tried going to go through right after?

I want to buy some DAO Tokens before the deadline, but I am locked up here. Any help would be appreciated.

Thanks!

@larrysmith1000
Copy link
Author

I don't know if it was a coincidence, but now (3 hours later) I tried sending one more transaction (1 eth) from the owner's account, and again chose maximum fee. On the very next block, the transaction went through, and so did all the prior transactions simultaneously.

Can anyone explain why this happened? It is definitely a usability problem for noobs like me, which we should be trying to attract.

@luclu
Copy link
Contributor

luclu commented May 27, 2016

I was able to observe this behaviour on another user's system.
@alexvandesande could this be related to the gas-estimate bug, fixed in geth 1.4.5?

@larrysmith1000
Copy link
Author

I did read one thread about that, and it does sound very similar:
ethereum/go-ethereum#906

@FaguiCurtain
Copy link

it looks like I have a similar problem, initially due to sending myself a wrong transaction ?

#739

@luclu luclu added this to the 0.7.5 milestone May 30, 2016
@luclu luclu modified the milestones: 0.7.5, 0.8.2 Jul 11, 2016
@alexvandesande
Copy link
Collaborator

Yes, transactions are removed by the node after going unconfirmed for long. As it seems you've been able to send transactions again I'm closing this issue

@david-sg
Copy link

I have the same issue- 10 days later when my account balance hit the initial amount, the transaction was mined, sending my ether to the other account. This happened twice.

@lock
Copy link

lock bot commented Mar 31, 2018

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

@lock lock bot locked and limited conversation to collaborators Mar 31, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants