Topic: [ANNOUNCE] Electrum - Lightweight Bitcoin Client - page 95. (Read 274562 times)

unfortunately, no.
I do add comments to git commits, but I agree that this does not really replace a proper changelog.
most of the recent commits were improvements of the communication between client and server.

concerning the above mentioned bug, I could reproduce it.
It is caused by the client not properly requesting information concerning its change address.
I will fix it asap

even if it is a UI bug, I would like to know about it.
what did the UI display exactly? which version were you using?

's no problem

Here's the newest version compiled:

Electrum 0.24 Windows Binary Build 1

Edit: ThomasV, do you have a changelog?

I edited my post. It was a UI bug. Sorry to make you go through all that trouble.

Removed all links to the windows build until more is clear about this bug. (Note that this isn't necessarily a windows bug. But it might be, so that's why I'm taking precautions.)

Huge bug found.
I was in #bitcoin when a newb came in asking for some BTC to play with, so I opened up electrum and sent .01 BTC to his address. It sends my entire balance. :/ Only 4.519187 BTC in that wallet, though. Luckily it wasn't my savings wallet!

This was on windows 7 64bit.

Edit: Should mention I was using BTCurious' latest binary.

Edit: Closed out electrum and reopened, and my coins were back. Must've been a UI bug.

I'm sure it would not be difficult. I never used pyqt, but I guess it is just as easy as pygtk

ThomasV: How hard do you think it might be for me to make a new gui for this with pyqt? Do you think it would be fairly easy to port?

Well, importing keys is not going to mess up new address generation, but it might interfer with the recovery from seed process.

First, exogenous addresses will obviously not be recovered from the seed (ok, you knew it). Second, since the added addresses
will occupy slots normally used by addresses generated by the seed, these addresses might create gaps (sequences of unused
addresses) in your list of addresses. If these gaps become larger than the gap limit set in your preferences, then you cannot rely
on this parameter to recover your wallet.

ThomasV helped me import a private key into Electrum, so I'm putting it down in case anyone else would like to do it. Currently it's manual, but someday there might be an option inside GUI. It would be a killer feature, something that BitcoinJ based clients are not able to do as far as I know.

Here is how it's done:
- find your electrum.dat wallet file (~/.electrum/electrum.dat in linux, ~\AppData\Local\Electrum\electrum.dat in windows)
- backup the file, just in case
- run electrum, disable wallet encryption (at your own risk), create new address (temp address), close program
- prepare your private key to import (offline key) in sipa format (starts with a '5'), together with a matching address (offline address). If your private key is not in correct format, use bitaddress.org to convert it.
- open electrum.dat in text editor, find the temp address. It should be the last one in a list of addresses enclosed by []. After the list of addresses, there is a similar list of private keys, they match addresses by index. Last private key matches last address etc.. Use your text editor search/replace functionality to search for this newly generated temp address and replace all instances with your offline address. Next, replace matching temp private key with offline key. Save the file.
- run electrum, your offline key should show up as any other keys, with correct balance. Encrypt and backup the wallet.

Electrum has deterministic wallet. ThomasV warned me this could mess up new address generation, which would not be deterministic anymore. I tested it and looks like there is no problem. Use at your own risk.

Hey, thank ThomasV. I'm just running a batch script every time he does something.

*tries to figure out how to start a new project on github

You could use github.com.
I love this project. Keep up the great work ThomasV!

Electrum 0.23 build 1 windows binary

I suppose I should upload this to a permanent location and then replace the file, so the link stays the same. Hmm..

thanks a lot. your patch is in version 0.23

Copy address to clipboard doesn't work on windows, the following error is thrown:

client\gui.py:893: GtkWarning: gdk_property_change: assertion `window != NULL' failed
  gtk.main()

It seems there is a bug in GTK:
https://bugzilla.gnome.org/show_bug.cgi?id=648931

I found a workaround.
Replaced:
                c = gtk.clipboard_get()
                c.set_text( address )
with this:
                from Tkinter import Tk
                r = Tk()
                r.withdraw()
                r.clipboard_clear()
                r.clipboard_append( address )
                r.destroy()

and now it works for me too!

I guess it would not be difficult to create an electrum-over-tor server... all you need is to forward the requests. However this is not something I will do myself, because I have no experience with Tor.

More important, I hope that we will soon have more than one single server. Electrum was designed with the idea that redundancy is good, and that clients should not rely on a single server. At some point, the client should be able to connect to several servers, and servers should be able to return a list of peers.

Is it possible to connect through TOR with it?

Any plans to make that a https connection to a server for added privacy possibility (man listening in the middle)? I suppose connecting to a electrum server across tor would work just as well against that anyway.


PS: Nice project. I particularly like the way the deterministic seed and passphrase combination for the wallet separates the theft versus loss of keys and/or back-ups problems, clever.

New windows binary (v2.2):

(If anything isn't working, it's because I just won a drinking game)
@ThomasV: If you need to reach me, you can just leave a message on here, or on IRC. I'm not very active in the weekend, but I'll see it eventually

thanks for the tip; I do not want to work on localization for the moment, but I'll keep it in mind.

Unrelated note: I wrote a http proxy server, so that electrum servers can be reached
through http using port 80. (for example, you can use ecdsa.org:80 in your settings)

http is is slower than the direct socket connection, but it can be useful if you are in
an environment that blocks high port numbers (for example a public wifi).