On a related question, will seeds that are more than 12 words (and multiples of 3) always be supported? It came up in this thread where hobbes talks about concatenating 2 wallet seeds to create a 24 word seed: https://bitcointalk.org/index.php?topic=354261.0in version 2.0, the seed phrase will be hashed in order to generate the master public key. thus, any phrase length will be supported. However, in order to recognize seeds from version < 2, I plan to check if the number of words is 12. so it's probably not a good idea to create 24 words seeds now. |
|
|
|
yes, the seed is encoded using groups of 3 words, extra words are ignored.
(note that version 2.0 will use a hash of the seed phrase)
How come it does not warn the user when entering a short seed? This significantly increases the chance of a collision. you are right, it should warn the user. however, the software only generates seeds with 12 words. there can be a collision only if users invent a seed, and "restore" from it |
|
|
|
|
yes, the seed is encoded using groups of 3 words, extra words are ignored.
(note that version 2.0 will use a hash of the seed phrase)
|
|
|
|
Yes I have the words and everytime I restore it brings up a different wallet.
that's probably the issue. can you reproduce this? |
|
|
|
|
Two memory leaks were fixed sunday and yesterday.
These leaks had been there for a long time, but were revealed by the release of the 1.9 client and its multiple connections.
Please git pull!
|
|
|
|
|
version 2.0 will have multiple accounts, so you can choose to freeze one
|
|
|
|
Yes I have the words and everytime I restore it brings up a different wallet.
some time ago there was the case of a user suffering from dyslexia. he had saved his seed on paper, but was not able to restore because he made several mistakes writing it down. luckily I was able to find the original seed. This is why the client now asks users to retype their seed during wallet creation. I guess this is about the best we can do to prevent such disasters. |
|
|
|
I cannot see the new coin control "send from"
select one or several address in the receive tab, and right click |
|
|
|
Coin control seems to have taken a step backwards, as you can now only select one address to send from specifically. What was wrong with the "prioritize" option?
you can select multiple addresses with crtl + mouse |
|
|
|
|
Electrum 1.9.5 was released. (binaries will follow)
Changes:
* coin control: the 'prioritize' command is replaced by a "send from" menu in the Qt GUI.
(you may select multiple addresses to spend from with the mouse, and the "!" shortcut is compatible with this)
* used addresses are moved to a collapsed section
* more bug fixes
|
|
|
|
|
yes, you can do it if you create your watching-only wallet with the 'deseed' command, from the wallet containing the imported keys
|
|
|
|
it looks more like a noob trying to attract attention.. electrum uses the python-ecdsa library to generate the seed, which calls os.urandom(), and not python's random library. btw, this "cracker" does use python's random library. on linux, os.urandom is non blocking, meaning that it is safe as long as you don't call it repeatedly (which might deplete your entropy pool). |
|
|
|
if you need to change the gap limit in a 1.9.x wallet, you may do it in the python console. For example, to set it to 10, by type: wallet.storage.put('gap_limit',10)then close the electrum client, and restart it |
|
|
|
I can also just use 1.9.4 and select file > open and use the wallet.dat file from my old version 1.8.1. What ticks me off is the arbitrary change in 1.9.4 removing expert mode so I can no longer set the gap limit where I need it. Bring back expert mode please.
Agreed I am stuck using 1.8.1 unless developer brings back option to adjust gap limit. I use MPK in a store plug in and gap limit has to be set high. It is not good idea to take options away from wallet after users have adopted. I think developer is trying to make wallet more user friendly for newbies at cost of upsetting present users. I acknowledge there is a bug with the current gap limit flag (-G) operation. I will fix it for the next release. |
|
|
|
Ok I did that. Thanks. But it displays red in the label column next to those new addresses. That isn't going to be a problem, is it?
red means that the address is beyond the gap limit, so it will not be recovered if you restore from seed the red color will disappear once other (preceding) addresses receive coins. |
|
|
|
in the python console, you can do: wallet.accounts[0].create_new_address(0) it will create a new address, beyond your gap limit. (you might need to restart the client to refresh the display) |
|
|
|
|
only Electrum relies on servers.
if servers were down or unreachable, you could still export your private keys from Electrum, and import them in another client.
|
|
|
|
I entered my master public key on a separate internet connected computer to create a watching only wallet, but if I right click on a public address and click on "private key", I can see the address's private key without it asking me for my password. Am I wrong or is this in effect no different than having an unencrypted wallet? If someone could hack into my computer, they could see the private keys for all my addresses. Until this is clarified, I have transferred all my funds out of electrum wallets for the time being (though electrum is otherwise great).
Does this happen to anyone else?
I guess you are talking about the wallet that has your seed (not the watching-only wallet), and that you forgot to encrypt it. just add a password.. or maybe you selected 'restore from seed' and typed your master public key there Nope. It is my watching-only wallet on a computer that has never had a hot wallet on it. I even erased the watching only wallet, reentered my MPK and it still happens. However, I compared the private keys shown on the watching-only wallet to the cold storage wallet the private keys are different. Could a dev or someone explain what is going on? Does this mean I am okay? you definitely selected 'restore from seed' instead of 'restore from master public key', and typed your master public key there |
|
|
|
I entered my master public key on a separate internet connected computer to create a watching only wallet, but if I right click on a public address and click on "private key", I can see the address's private key without it asking me for my password. Am I wrong or is this in effect no different than having an unencrypted wallet? If someone could hack into my computer, they could see the private keys for all my addresses. Until this is clarified, I have transferred all my funds out of electrum wallets for the time being (though electrum is otherwise great).
Does this happen to anyone else?
I guess you are talking about the wallet that has your seed (not the watching-only wallet), and that you forgot to encrypt it. just add a password.. or maybe you selected 'restore from seed' and typed your master public key there |
|
|
|
yes, but doing it with a single click instead of having to switch around and copy paste would be easier.
I agree |
|
|
|
|
Show Posts
