you should file an issue on github because this looks like a bug |
|
|
|
|
you keep asking questions but don't read the answers given to you. use the script i posted above in post 4 or just do what bob123 said in post 7. there is nothing to install or extract with the appimage. just make it executable and run it.
|
|
|
|
The reason you can't do the setup is because python-pip and pyqt5 from apt are not built against the newer version of python you installed from that third party repo. I think you should just use the appimage download instead. It contains all dependencies and is designed for old linux distros like the one you have. Here's a script that will fetch it for you: https://github.com/AbdussamadA/electrum-install |
|
|
|
I think 2.8 is to old and the latest Electrum version will not be able to read and/or upgrade the wallet file
You may be right, but as far as i remember, Electrum maintains forward & backward compatibility for both wallet files and seed/mnemonic. Both Electrum docs and GitHub commit shows/mention forward & backward compatibility, but i don't know far the compatibility support. If i am correct that only works if you upgrade from version 2.8 and download EVERY version and upgrade step by step but it does not work from 2.8 directly to 3.3.6 That's not true. The latest version of Electrum will attempt to upgrade the wallet file and will go through all the steps needed for old wallet files. However it is best to be cautious and have backups of the seed and multiple copies of the old wallet file (In case the upgrade fails you can still extract the secrets from the old wallet files manually) |
|
|
|
Just install electrum and create a standard single sig wallet. Don't bother with cold storage if you're just starting out. Also don't choose segwit when asked. You will find reasons why in step 4. Another thing you can do is bookmark electrum.org in your browser and make sure you only download electrum using that bookmark. Never ever download it from anywhere else. |
|
|
|
Electrum is trying to force users that in some way choose SegWit instead Legacy address by placing this option as a primary, and by number of threads open here with similar issues, we see that a good number of users still do not know the difference between these two options.
The maintainer believes in this strongly so what can we do? It would be nice if exchanges started supporting it because it does save users transaction fees. By placing Legacy as first option we would avoid that users create bc1 type address, what can be especially stressful in case of wallet recovery when users with Legacy wallet instead of thier balance see 0 and unknown address.
The seed mnemonic contains a seed prefix which tells electrum what type of wallet to create. So the user won't have to choose between legacy and segwit when restoring. Electrum will detect it automatically. The 0 balance issues we sometimes see on the forum are never caused by this. |
|
|
|
|
Transaction fees have gone down so you should set a lower fee. Even 5 sat/byte is plenty now. Another possibility is that you have a 2fa wallet and it's sending the 2fa fees to your cosigner's address. If you click on preview on the send tab it should show that output highlighted in purple. You can 2fa change fee settings by clicking on the blue-white shield icon in the bottom right.
|
|
|
|
|
You can begin a new wallet via file > new/restore, enter a unique filename and click next.
|
|
|
|
|
when you run electrum and it shows you that install wizard dialog you can click on the browse button to choose a specific wallet file. alternatively file > open in the electrum main window lets you do the same thing.
also file > save copy is handy for saving wallet files and saves you from digging through the file system looking for it.
restoring from seed is not recommended because you will lose metadata like transaction and address labels.
|
|
|
|
you can open a different wallet file via file > open or file > recently open. you can also specify a specific wallet file via the -w command line switch so if you modify your electrum shortcut and incorporate that in there you won't ever mistakenly open the wrong wallet file. for example: c:\programfiles\blah\blah\electrum.exe -w c:\path\to\wallet\file
You can save the wallet file to a specific location via file > save copy or reference it in its default location: http://docs.electrum.org/en/latest/faq.html#where-is-my-wallet-file-located |
|
|
|
|
phishing messages in old versions are how the malware is spread. i suggest you check your browser history and tell us where you downloaded this software.
also you haven't answered pooya's question above about what characters your seed starts with. if you go to wallet menu > seed what are the first few characters of your seed given there?
finally just to clarify you are trying to send money to that bc1... address you posted above right?
|
|
|
|
|
You can bump the fee by right clicking on the transaction on the history tab and choosing increase fee, set a new fee, then click sign and broadcast.
|
|
|
|
I suspect it to be either the conversion from string to hex or some kind of change concerning the Electrum seed system. Of course I also installed again the old versions 2.7.9 and 3.0.0 and tried my seed without success.
WTF man! You're not using the "Electrum seed system"! You came up with your own custom scheme and now are blaming electrum for it. Your system has no checksums in it like HCP pointed out. Any minor variation in the seed string or mistakes in copying the hex code could cause problems. |
|
|
|
One last thing. Now i have established access, what should i make sure to back up to avoid this again.
I have written and rewritten the 12 word seed that allowed me access. It isnt stored online or anything like that.
Someone else had asked whether i have any of the addresses saved. I guess i can do that now i have access. Should i do this? If so could you kindly direct me on how to do so?
Thanks a million
First of all you should give back to the community by telling us exactly what the problem was. That way we can learn and anyone else who has this problem can also learn from your experience. Second there is no reason to save the addresses. As long as you have the 12 words you are fine. The reason you were told whether you knew any of the addresses is because it would serve as a check for whether the correct wallet was restored. A check that could be useful if you needed to run brute force recovery tools. However non of that is necessary if you have the seed written down correctly. What you can do is save the wallet file as well if you care about labels for transactions and addresses. You can do this via file > save copy. |
|
|
|
Can you recall the original addresses? Do they start with "1", "3" or "bc1"?
Also, you said you've tried to enable the "BIP39" option, right?
If it happened to be a BIP39 SEED, was the message on the left side of the option said "BIP39 (checksum: failed)" or "BIP39 (checksum: ok)"?
Because any of the two will enable you to press "next" button to create the wallet but real BIP39 SEED will display as "ok".
If not, you might have miss-clicked one or changed the order (now or during the 1st wallet creation backup).
It's not bip39 because he says above that there are words that are not a part of the bip39 wordlist. |
|
|
|
...but then it pops up this messege and says: Wallet file corruption detected. Please restore your wallet from seed, and compare the addresse…
This means that your wallet file is corrupted and could possibly be creating addresses that are not backed up by your recovery seed. There was an old issue that was fixed whereby you could end up with a situation like this: When creating a new wallet, the path would be set to the path of an existing wallet, as due to os.path.exists failing, the wizard would think there is no file there yet. However in the wallet storage constructor, os.path.exists would suddenly work and the existing file would get opened. The wizard would then start modifying the existing file, thinking it's a new one. The wizard would put a new seed and xpub there. Then, the task that creates the addresses for the xpub (create_addresses) would be a no-op, as it would find that there are already "enough" addresses generated in the file (corresponding to the old wallet!).
When the wizard finished, the wallet would then get opened as normally. The wallet file would contain the new seed, new xpub, but old addresses. It would appear that you might have had something similar happen... You should create a new wallet ("File -> New\Restore -> NEW_WALLET_NAME -> Standard wallet -> I already have a seed"), as suggested by nc50lc... and see if it generates the same addresses as the wallet that is giving you the corruption warning. If it does not, then your seed will not be able to restore your wallet file. You should immediately create a new wallet (with new seed) and send all your Bitcoins from "corrupt" wallet to new wallet. He should definitely attempt a restore but if his seed doesn't generate the same addresses he won't be able to send coins from the old to the new one. That's because the old wallet doesn't have the corresponding private keys/precursor seed either. |
|
|
|
No, some of them are not in there.
You did check both lists right? If yes then it's not an electrum seed. |
|
|
|
I compared my seed with the list and all the words are there...I triple checked when writing it down.
what software was originally used to create the seed? |
|
|
|
are all the words in this list? this is the old electrum wordlist and is different from the bip39 one. |
|
|
|
|
Show Posts
