Topic: Electrum "stuck" - showing unverified transactions (Read 5624 times)

Change the title for your message, I had to read it entirely to end up with "fixed"

This problem has been evident for me for the past 24hrs.

Also moving my coins from the change wallet to the main wallet, its been sitting on unverified for the last hour.

I've tried everything in this thread as well as trying flatfly's latest portable build (1.9. and problem persists.

Renaming the blockchain headers files results in losing my history, but my balance stays and the problem persists.

Any suggestions?

Update: Using flatfly's 1.7.4 build fixed my issue after a few minutes. I'm going to guess the newer builds aren't downloading the headers properly. The newer builds should have a "reset/redownload headers" option in the menu. Since there is no file menu and way to save the wallet.dat, do I just backup electrum.dat to backup my wallet? Hmm there is no option to capture the seed pass phrase in 1.7.4 either.. Hmm

Tried the latest (1.9. of flatfly and all transactions cept one i stuck on unverified. The headers file is over 20mb. Seems 1.9.x isn't updating the transactions properly?

Ok fixed it. Unchecked auto connect, closed client, selected a different server and selected autoconnect. It synched successfully with all transactions bar one (not enuf confirms; at least its not -1) confirmed.

Problem with this version is that it opens hidden and I don't get it to show itself unless I click on "hide" in the system tray.

Had this problem, upgraded client, problem solved!

Thanks DEV team.

This issue should be fixed in 1.9.3 - Win/Mac builds will be available some time this week.

Yea , i'v got it too , i did post in another thread but then spotted this one so excuse the double post on same subject.

2 transactions have been stuck for days now , tried all servers most connect fine but nothing changes , both transactions have cleared through the chain fine and have 100's of conformations.

I have not closed , hibernated or sent to sleep at all wile wallet was open.

EDIT:- ok after reading some more threads on same subject i found that a simple file/open/default_wallet sorted it. Might go back to multibit until this has been looked at.

same problem here (electrum 1.9.2 linux)

outgoing transaction had 3 confimations on blockchain already but still showed unverified, -1 transactions in electrum. Network dialog showed Server having latest block, switching servers multiple time (and also trying https instead of ssl) did not help, restarting electrum finally solved it.

This bug should have a high priority, this is one of the most central features of a wallet app and people are expecting it to work: permanently being updated about latest status of payments! If even such basic core functionality is buggy and unreliable it does not inspire trust in the software, especialy for newcomers who are not yet very familiar with how it all works and alternatives of tracking their transactions.

How is this implemented? Does the server push or does the client poll? what happens on reconnect or connect to a different server, what is different from reconnect after program restart? What does it need the blockchain headers for, isn't this what the servers are supposed to handle?

indeed, you are the second user to report that i gets fixed by restoring from seed.
apparently something was corrupted in the wallet file

Its over 24 hours and the transaction is still not verified whats going on?

Edit: Deleted everything to do with Electrum and reinstalled using my seed and now its verified, quite a serious bug.

I'm using the Windows installer version. I did originally use the the standalone exe but switched to the installed version. I'm on Windows 8.1 Pro 64 bit.

edit: It has now connected but the transaction is still showing as "unverified" with -1 confirmations.

please report if you were using the windows portable version of 1.9
it is broken and I removed it from the website

Well my first test transfer  completed and verified with no problems within 30 mins. Its only when I transferred the rest of my btc that it wont verify. The transaction is currently sitting at 146 confirmations when I look on blockchain.info. Also now the program wont connect at all it either says not connected or just sits at synchronizing forever...some real help would be greatly appreciated.

Currently web download of the headers will only fetch 17 MB. It needs over 20 MB that are downloaded in chunks directly from the electrum servers, it takes quite a lot of time.

I've just switched from Bitcoin QT to Electrum today and transferred some bitcoin to my Electrum wallet and I'm getting the exact same issue. I've tried all the suggestions in this thread and nothing has fixed it. Is there anything else I should try or is it just a waiting game?

Well, deleting the directory wasn't the first thing I tried.  Assuming you are correct, if Electrum isn't ready for service, some indication of that should be given through the user interface. Downloading a 20 MB file should be almost instantaneous on my connection.

If you deleted the Electrum directory you'd need to wait for the headers to be downloaded from the servers for SPV before seeing your confirmations as confirmed

I'm having the same problem. Steps I've taken (unsuccessfully):

1. Choose a new server.
2. Stop the client and restart.
3. Stop the client, delete the .electrum directory, restart and restore from seed.
4. Upgrade to 1.9 git, delete local wallet directory, restart, restore.

None of these steps help.  Multibit shows verified. Blockchain.info shows 27 confirmations.

Maybe all of the servers are being DDOS'ed?

"Status: -1 confirmations"

------------------------------------------------------------------------------------------------------
Edit:

Got an exception while quitting the 1.9 client... maybe this will help narrow down the problem:

./electrum
Exception in thread Thread-13 (most likely raised during interpreter shutdown):
Traceback (most recent call last):
  File "/usr/lib/python2.7/threading.py", line 551, in __bootstrap_inner
  File "/home/user/Downloads/electrum/lib/wallet.py", line 1540, in run
  File "/home/user/Downloads/electrum/lib/wallet.py", line 1596, in run_interface
: 'NoneType' object has no attribute 'Empty'

And now out of the blue, it is verified and jumped from -1 to 31 confirmations after the crash.

This happens to me too. Really something the developers should check out if we're all seeing it. Sure, workarounds are nice, but fixing the problematic behaviour is better.

This happens to me all the time. Maybe it's because I regularly put my Mac in standby. Restarting or selecting a new server works, but perhaps Electrum could do a forced reset this way every 10 minutes or so? This issue is currently stopping me from recommending Electrum to newbies.

Oh this may be dangerous. I once tried to restore an electrum.dat file without the blockchain header files and it didn't work. Note this was not a backup made using the UI but a straight copy of the file from the .electrum folder. So before you go deleting the header files do a proper backup of your wallet using the menu options in the UI.

Switch to different servers a few times. That always works for me.