A few more questions: Did you run the portable version off a USB stick, or your hard drive? It's supposed to unpack all Python files into a subdirectory (the Electrum-P folder), next to the executable (elec055-portable.exe). Did it do that?
I will try to find a Vista machine so I can do some testing.
EDIT: Note that in portable mode, the executable doesn't need the -w parameter. It will automatically use the wallet file (electrum.dat) located in the same directory. Sorry, I should have mentioned this.
|
|
|
I tried the portable version but i cant install it (Vista). The normal version works.
Hi, do you get an error message with the portable version? Another bug: I cant see the privkey of imported addresses with the command: -o addresses -ak With previous versions it worked. (the wallet is unencrypted)
Indeed, same problem here. I guess this is a new bug. File "electrum", line 398, in <module> addr += ':' + str(wallet.get_private_key_base58(addr, password)) File "C:\Documents and Settings\ffly\Application Data\Electrum-P\0.55\C_\ElectrumPY\lib\wallet.py", line 388, in get_private_key_base58 pk = self.get_private_key(address, password) File "C:\Documents and Settings\ffly\Application Data\Electrum-P\0.55\C_\ElectrumPY\lib\wallet.py", line 409, in get_private_key raise BaseException("unknown address") BaseException: unknown address
|
|
|
Version 0.55 is now available, with some sexy new (advanced) features! See this thread for more info. Enjoy!
|
|
|
OK, I did find some time to make the Windows builds for 0.55. Available now!
|
|
|
No good - I've gotten stuck at the same block again.
I would really appreciate some help here[/b]. It's getting to the point where it's not worth it to store my coins on this client anymore.
Are you mining? If not, perhaps you should consider switching to another, blockchain-less client? I would suggest checking out Electrum and MultiBit, both are quite good and stable. To compare their features, you can use my chart, which is up to date: http://dre.tx0.org/compare.htm (There's Armory too, but it's still in alpha for now)
|
|
|
No need for Linux to do that. To extract your private keys, Pywallet works just fine on windows. You need to install python 2.7 first. Let me know if you need help with the process. As for clients that support importing of external keys, for windows, check out Electrum and MultiBit, both are real good. To compare their features, you can use my chart, which is up-to-date: http://dre.tx0.org/compare.htm (There's Armory too, but it's still in alpha for now)
|
|
|
Awesome release. And it's great that the advanced features are disabled by default, to avoid confusing new users.
Win-optimized builds will only be pushed late Sunday I believe. But PM me if you need early access, and I'll see what I can do.
|
|
|
Hi Sean,
any news on when you expect to be able to send the pending rewards?
Thanks!
|
|
|
signmessage / verifymessage don't seem to work for me, verify always produces False - could someone else test as well?
|
|
|
It may be worth trying to scan your hard disk for remnants of deleted copies of the wallet. To do that, I highly recommend the portable version of Recuva. It's very simple to use. If you're lucky, you could find one that is unencrypted (until recently, Bitcoin-Qt had a bug that sometimes left the wallet file partially unencrypted on the hard disk). Enable deep scan mode, and look for any recoverable DAT files that are similar in size to your wallet file.
|
|
|
EDIT2: I have fixed this in Windows build 0.53-2 (just released) - There were some HTTP-related libs missing following the upgrade to Python 2.7.3.1.
Was this a problem on the client? From what I see in the traffic, the client is polling the server just fine - it's just not getting back the transaction notification. On Windows, there was a problem on the client with HTTP connections, which is now fixed. But it seems that what you are reporting is perhaps a separate issue. What is the command you are using in your tests? Do you have the same issue with the "electrum balance" command?
|
|
|
However, after a bit of testing, there seems to be a bug [...]
If you go up(maybe back a page or two) I read some people were getting balance mistakes from the ecdsa.org server but valid on every other server. it sounds like a mix up on the ecdsa servers only. [...] I just tried it on electrum.novit.ro and btcback.com with the same results: when the client is connected over TCP, an incoming transaction generates the appropriate server->client message in 5-10 seconds, whereas if the client is connected over HTTP, nothing happens (I waited ~2 minutes before restarting the client, at which point the transaction shows up). Confirmed, HTTP fails for me too. EDIT1: are you using the Windows build? The issue could be specific to Windows builds. I will investigate further. EDIT2: I have fixed this in Windows build 0.53-2 (just released) - There were some HTTP-related libs missing following the upgrade to Python 2.7.3.1.
|
|
|
Are there any limitations in the portable version?
No, the portable and non-portable versions are perfectly identical (they share the same SHA-1 hash), except that the portable version doesn't write ANY data outside of the folder it is stored in - it automatically considers the location of electrum.dat is next to the executable (the command-line version still needs the -w parameter, though). I hope this answers your question. Do not hesitate to let me know if any issues.
|
|
|
Glad you like it! But I believe genjix is quite focused on the Bitcoinica issue at this time (which is fully understandable).
|
|
|
use the -o (offline) option when working with wallets on a non-networked computer.
You can create more than 5 addresses by editing the code, but you have to remember to do that same count when/if you restore in the future. I believe the actual line/file you need to change is documented earlier in this thread.
Line 257 in wallet.py: self.gap_limit = 5 # configuration
Or, new receive addresses get automatically created by the client as you use the existing ones.
|
|
|
Slightly updated the chart CSS layout to fix a display issue with older IE versions.
|
|
|
Release 0.53-1 is out.
Just a minor release, with better error messages and further stability improvements. As always, feel free to let me know if any issues or comments.
|
|
|
have you tried 6.2? it downloaded all blocks for me in about 20/30 mins yesterday
Wow... that's the time my laptop takes to update like, a single week of blocks. And I'm using 6.2. I'm not too sure about that, but wouldn't that kind of issue be helped by forwarding port 8333 (at router level)?
|
|
|
Personally, I use Electrum, but figuring out how to run a python app is also beyond any noob.
There are window builds (exe's which I don't think require Python?)... but I think MultiBit might be a better choice because it still requires a blockchain (although much more compact). Indeed, no need to install Python when using the windows binary (An up-to-date compact version of Python 2.7 is included, and is totally noob-friendly)
|
|
|
|