thanks for the support!

New clients filter out all the old servers since the protocol has changed. For the moment there are only two servers running the new protocol:
electrum.bysh.me and ecdsa.org

flatfly, I just tested latest 1.5.4 build. Not displaying QR codes is known issue (seed, address on Receive tab)?

Btw any chance to pack Electrum with zbar package, which is available for Windows as well? It adds QR scanning features to Send dialog...

Hi slush,

Thanks for trying the new build!

Yes the qr bugs are known issues, but the good news is that thomasv just fixed them on the github master! What other bugs have you noticed in 1.5.4?  If there are too many, I'll consider making a 1.5.3 build available as well until they're fixed.

About the zbar package, I usually try to keep my builds as lean as possible, but I'll see if I can include that (+ any required dependencies) in my main build without impacting the download size too much.

Also, as I often get requests for custom builds, and the time I can currently devote to this is quite limited, I usually give priority to donators

Hi, thanks for trying my build

Indeed, some GUIs (gtk and text) are not supported in my build.
Regedit is not necessary to fix the issue you have, as Electrum doesn't save anything
to the Windows registry. The best way to solve the issue is to issue the following command
from the console:

 electrum set gui "qt"

This will set the default GUI back to Qt (classic).

The above is normal: I've spent a lot of time to make my build totally self-contained so it doesn't require "installing", and does not touch the Windows system files in any way.



This is not normal - It is probably due to an old electrum.dat wallet file lying around on your hard disk from the old days, and pointing to a non-existing server... To fix the issue, find that file (in your Application Data folder, not sure about the exact path on Win7 x64), rename it to something else, and start Electrum again. It should then prompt you to create a new wallet (or restore an existing one from seed.)

Let me know how that goes so I can help you further if needed.


You could give it a try, but I think it will exhibit the same behavior, as we're using the same codebase.

Electrum.dat is the only file where all sensitive information is stored.
The private keys to those 5 (and any subsequent) addresses are not stored anywhere, they are dynamically computed from the seed, which is stored in the electrum.dat file. This is one of the great benefits of deterministic wallets: you only need to back up your wallet just once, and that's it!

Just be sure to use a strong password and the seed will always be stored in encrypted form, using AES256.

If, for any reason, you do need to access the private keys for each individual address, you can do so by issuing the following command:

1. Sure, any imported private keys get encrypted as well.  However please note that electrum doesn't support importing compressed keys at this time. There is a pull request for this but it still needs to be adapted to the current codebase and merged in.
Anyway, the best practice is to avoid importing keys as much as possible, and send funds from bitcoin-qt to electrum addresses instead (if at all possible in your case) - this is to get the full benefits of deterministic wallets.

2.  That's the encrypted version of the seed (ending with equal signs). It can't be used without your password. The actual seed is a 128-bit high-entropy random number, which is usually displayed as either a 12-word mnemonic code or a 32-digit hex number.



No problem, always glad to help. I won't be online very much next week, though, but you can also get assistance in the main electrum thread or on the #electrum IRC channel.

The server is down  :

Thanks!

In Lite mode: if you start typing previously saved Label in "Enter a recipient address..." field, whole string (label and address) is copied... string stays in RED color (indicating an error address) and I'm unable to send BTCs.

It works fine in classic mode, though.

Donation sent.

Where is a list of version changes?