Since you didn't mentioned the option that I gave you,
I suppose removing the wallet's password while offline to manually get the keys from the wallet didn't worked because it crashed regardless of the offline status?
Have you tried increasing the machine's "paging file" to a very large amount (restart it) and see if it'll stabilize?
Topic: Electrum issue ... argh (Read 259 times)
so .. there is no way to somehow group the 200k txns into some order so the dust can be consolidated into the 4 - 7 btc that its showing?
id have to say that sounds reasonable to what is occurring...
Can you start by answering this?id have to say that sounds reasonable to what is occurring...
So OP: what did you do? 
I can think of several things to try, but it kinda depends on how you got here. If you just imported a shitload of publicly known private keys, chances are the total balance is 0 and you'll only see that after it finishes syncing. 
I'm curious: how did you get to this point? I see many dust transactions from last year.
If I had to guess based on OP's post history these keys are the publicly known private keys from puzzles, small keys (like 1), brainwallets, etc. which is why if you check out the timestamps on the transactions in the history, each transaction is usually spent immediately within seconds.
Those things are not usually required for regular Bitcoin users, so it's always suspicious when such a question is asked. Not because I have anything against them attempting to crack keys, but because I think it is pointless brute-forcing Bitcoin addresses, so I'm wasting my time trying to help them do it.
Don't forget the other rare reason, bad programming from years ago when BTC was under $100 and transactions were free.
I am probably responsible for a lot of dust being out there in 1000s and 1000s of addresses from me being a crap programmer trying to make things work a decade ago.
It is what it is. This case is different but at times it is legit.
-Dave
so .. there is no way to somehow group the 200k txns into some order so the dust can be consolidated into the 4 - 7 btc that its showing?
id have to say that sounds reasonable to what is occurring...
I'm curious: how did you get to this point? I see many dust transactions from last year.
If I had to guess based on OP's post history these keys are the publicly known private keys from puzzles, small keys (like 1), brainwallets, etc. which is why if you check out the timestamps on the transactions in the history, each transaction is usually spent immediately within seconds.Those things are not usually required for regular Bitcoin users, so it's always suspicious when such a question is asked. Not because I have anything against them attempting to crack keys, but because I think it is pointless brute-forcing Bitcoin addresses, so I'm wasting my time trying to help them do it.
Don't forget the other rare reason, bad programming from years ago when BTC was under $100 and transactions were free.
I am probably responsible for a lot of dust being out there in 1000s and 1000s of addresses from me being a crap programmer trying to make things work a decade ago.
It is what it is. This case is different but at times it is legit.
-Dave
I'm curious: how did you get to this point? I see many dust transactions from last year.
If I had to guess based on OP's post history these keys are the publicly known private keys from puzzles, small keys (like 1), brainwallets, etc. which is why if you check out the timestamps on the transactions in the history, each transaction is usually spent immediately within seconds.Those things are not usually required for regular Bitcoin users, so it's always suspicious when such a question is asked. Not because I have anything against them attempting to crack keys, but because I think it is pointless brute-forcing Bitcoin addresses, so I'm wasting my time trying to help them do it.
If I had to guess based on OP's post history these keys are the publicly known private keys from puzzles, small keys (like 1), brainwallets, etc.
That's what I thought, but in that case I'd expect him to have the private keys instead of needing to export them. An incomplete synchronization could also explain the 7 Bitcoin balance.So OP: what did you do?
I'm curious: how did you get to this point? I see many dust transactions from last year.
If I had to guess based on OP's post history these keys are the publicly known private keys from puzzles, small keys (like 1), brainwallets, etc. which is why if you check out the timestamps on the transactions in the history, each transaction is usually spent immediately within seconds.
To summarize your 2 screenshots:
You have 5194 transactions, many dust transactions in and out, 99387 private keys, and a total balance around 7 Bitcoin. With that balance, I would continue working offline!
I'm curious: how did you get to this point? I see many dust transactions from last year.
After exporting the keys, I'd import them all into Bitcoin Core. You should be able to do that from the command prompt, and when done let Bitcoin Core update it's wallet. From what I've read, it should be able to handle that many keys without problems.
You may want to read my topic on consolidating small inputs to save on transaction fees.
You have 5194 transactions, many dust transactions in and out, 99387 private keys, and a total balance around 7 Bitcoin. With that balance, I would continue working offline!
I'm curious: how did you get to this point? I see many dust transactions from last year.
Run Electrum offline, remove the password (leave "New Password" blank) and open the wallet file as text.
The keys should be listed there under "keystore", import them by batch per wallet this time.
All the more reason to do this offline. And start by making another backup of your wallet file before doing this.The keys should be listed there under "keystore", import them by batch per wallet this time.
After exporting the keys, I'd import them all into Bitcoin Core. You should be able to do that from the command prompt, and when done let Bitcoin Core update it's wallet. From what I've read, it should be able to handle that many keys without problems.
You may want to read my topic on consolidating small inputs to save on transaction fees.
Does anyone know of a way to either xfer the thousands of txns out of this ,... or a way to export my data ... without this crashing?
Run Electrum offline, remove the password (leave "New Password" blank) and open the wallet file as text.The keys should be listed there under "keystore", import them by batch per wallet this time.
Note: Make sure that the text editor and your PC can handle large txt files (you managed to create that wallet so I guess you already got it covered).
Wallet file can be found here: electrum.readthedocs.io/en/latest/faq.html#where-is-my-wallet-file-located
I don't think there is any solution to this. The way Electrum wallet is designed, it is not made for such gigantic number of keys/transactions! The wallet file is a simple JSON that loads into the memory and it is not normal either to have nearly 100k keys in the wallet.
You should use another wallet like core that handles wallets as a database not a simple JSON file.
You should use another wallet like core that handles wallets as a database not a simple JSON file.
I'd also recommend to move this into the correct board, i.e. Bitcoin Forum > Bitcoin > Development & Technical Discussion > Wallet software > Electrum .
From the above screenshot we can see that your electrum is synchronizing. Let the wallet synchronize itself first (allow 10-20mins depending on your internet connection speed) and try again. Also, you should upgrade it to the latest version 4.3.3 from the official website since you are using an older version as seen by your screenshot. Older versions might have few unsolved bugs.
Does anyone know of a way to either xfer the thousands of txns out of this ,... or a way to export my data ... without this crashing? I have tried for longer than i will admit to move funds or export keys... and upon the export it crashes.
It indicates its sync'd to the current date there but i think its false as it never completes and always cycles and then crashed into a pile of burning crap. I tried a key export again only running that and it disappears after so often... see pic
I read somewhere i need to compile and run X-server also for this ... is there anyone who can suggest something perhaps? i am at the end of my rope with it.
Yes i did ask the devs awhile back on github about this crashing and the response was not something helpful
yes i know its alot of little nothings...
It indicates its sync'd to the current date there but i think its false as it never completes and always cycles and then crashed into a pile of burning crap. I tried a key export again only running that and it disappears after so often... see pic
I read somewhere i need to compile and run X-server also for this ... is there anyone who can suggest something perhaps? i am at the end of my rope with it.
Yes i did ask the devs awhile back on github about this crashing and the response was not something helpful
yes i know its alot of little nothings...
Jump to: