Great! I guess it's donation time again for both of you : )
Thanks minimalB, really appreciated. And I'm glad you like the new build!
Topic: [ANNOUNCE] Electrum - Lightweight Bitcoin Client - page 69. (Read 274537 times)
Thanks minimalB, really appreciated. And I'm glad you like the new build!
@ThomasV: any idea why do i get this message occasionally? It happens once out of 10 times in general... it also happened before, so it's not about this brand new build.
I click OK and try sending again and then it works...
I click OK and try sending again and then it works...
I noticed this on my server.
I did investigate a few of those transactions, and the error was caused by insufficient fees.
(note that you need to pay a higher fee if you try to spend recent coins)
this does not mean that it is always the cause. it might fail at connecting inputs for some other reason (server side bug)
As announced in the other thread, I have found a way to add a virtual
console to my package that should support the full Electrum command-line.
All tests have proven quite good so far.
console to my package that should support the full Electrum command-line.
All tests have proven quite good so far.
this is great news.
with full console support I believe there is no more reason to use the old btcurious builds.
I will therefore stop supporting the old (native) protocol at ecdsa.org, and enforce the stratum protocol used in version 0.44.
users who are still on client 0.43 or older will need to upgrade.
Great! I guess it's donation time again for both of you : )
@flatfly: this font is also cool.
@ThomasV: any idea why do i get this message occasionally? It happens once out of 10 times in general... it also happened before, so it's not about this brand new build.
I click OK and try sending again and then it works...
@flatfly: this font is also cool.
@ThomasV: any idea why do i get this message occasionally? It happens once out of 10 times in general... it also happened before, so it's not about this brand new build.
Code:
---------------------------
Error
---------------------------
error: error: transaction rejected by memorypool: Transaction not accepted to memory pool.
0100000001c806158ebcd026bedd3f58d958d08ca54571fc2278bb630f18435c0971544cdd010000008c493046022100e48326a3da1d2e46a36ecd8a7da860a128c82abc51e6a6d1ff9887bd78c4bce2022100ba0aaa6868453df71ed51c96d392c69883d12cbd63b247b031435223349613fa014104cd06feb6b3b1dd4f190b644f3a7e1a85ed5de5307ef14cc47476594a7eedb84a7fb0f9c9965a320dd88a1556c5f279768a3a6040abfd8eaf0ecc5bc767271b3bffffffff0200e1f505000000001976a9141656d23d35bf965c791649f0664c28bd7f41829f88acb6427200000000001976a9143479b2cc1da46bd7d3ebb4d88b3e854d5eadf65488ac00000000
---------------------------
OK
---------------------------
Error
---------------------------
error: error: transaction rejected by memorypool: Transaction not accepted to memory pool.
0100000001c806158ebcd026bedd3f58d958d08ca54571fc2278bb630f18435c0971544cdd010000008c493046022100e48326a3da1d2e46a36ecd8a7da860a128c82abc51e6a6d1ff9887bd78c4bce2022100ba0aaa6868453df71ed51c96d392c69883d12cbd63b247b031435223349613fa014104cd06feb6b3b1dd4f190b644f3a7e1a85ed5de5307ef14cc47476594a7eedb84a7fb0f9c9965a320dd88a1556c5f279768a3a6040abfd8eaf0ecc5bc767271b3bffffffff0200e1f505000000001976a9141656d23d35bf965c791649f0664c28bd7f41829f88acb6427200000000001976a9143479b2cc1da46bd7d3ebb4d88b3e854d5eadf65488ac00000000
---------------------------
OK
---------------------------
I click OK and try sending again and then it works...
Build 0.51 for Windows has been released.
Probably my most polished build to date!
As announced in the other thread, I have found a way to add a virtual
console to my package that should support the full Electrum command-line.
All tests have proven quite good so far.
Note: I did change the font again, this time to Fixedsys (another default
Windows monospace font), for better compatibility with Vista. I think it
is quite readable too, but am open to suggestions if you don't like it...
Screenshots:
Probably my most polished build to date!
As announced in the other thread, I have found a way to add a virtual
console to my package that should support the full Electrum command-line.
All tests have proven quite good so far.
Note: I did change the font again, this time to Fixedsys (another default
Windows monospace font), for better compatibility with Vista. I think it
is quite readable too, but am open to suggestions if you don't like it...
Screenshots:
since I found out how to install files in setup.py, I added a GNOME menu item in the install script.
Hence the new release (0.51)
If you use GNOME, 'pip install' should add Electrum to your Applications->Network menu
Hence the new release (0.51)
If you use GNOME, 'pip install' should add Electrum to your Applications->Network menu
I've started Slovenian language (si). It's not done jet. I have to contact some of my colleagues (who studied our language at university) for certain words and proper translation. It will take some time...
thanks! that was fast!!
I've started Slovenian language (si). It's not done jet. I have to contact some of my colleagues (who studied our language at university) for certain words and proper translation. It will take some time...
I have offered an undisclosed amount of Bitcoin to my friend in Vietnam to do the translation for this locale.
nice! 
I have offered an undisclosed amount of Bitcoin to my friend in Vietnam to do the translation for this locale.
New version: 0.50
Changelog:
* Electrum is ready for crowdsourced localization!
This release ships with a localization script, 'mki18n.py'.
It also includes language files for German and French (only 3 messages are translated so far)
Anyone can join the translation efffort.
mki18n.py will read translations from https://en.bitcoin.it/wiki/Electrum/Translation and create .mo files in your 'locale' directory
After you call this script, you need to run 'sudo python setup.py install' in order to install the new translation on your system.
(edit: you will need to add a line to setup.py if your language is not there)
Changelog:
* Electrum is ready for crowdsourced localization!
This release ships with a localization script, 'mki18n.py'.
It also includes language files for German and French (only 3 messages are translated so far)
Anyone can join the translation efffort.
mki18n.py will read translations from https://en.bitcoin.it/wiki/Electrum/Translation and create .mo files in your 'locale' directory
After you call this script, you need to run 'sudo python setup.py install' in order to install the new translation on your system.
(edit: you will need to add a line to setup.py if your language is not there)
I also sent you 1BTC as thanks for being so responsive about bugfixes.
thank you!
Awesome! That was what I expected, but now I understand how that's not orthogonal to how "deseed" worked originally.
I also sent you 1BTC as thanks for being so responsive about bugfixes.
I also sent you 1BTC as thanks for being so responsive about bugfixes.
Thanks so much for those bug fixes! As far as I can tell that completely fixes the problems that I listed as 1,2,3, and 5.
However, offline wallets and imported keys are still incompatible:
When you "electrum import:" followed by "electrum deseed" then "electrum addresses -k", is displayed.
However, offline wallets and imported keys are still incompatible:
When you "electrum import
only for imported keys (imported keys are not generated using the seed).
or did you expect deseed to remove the private keys of imported addresses too?
EDIT: I changed that in the way you seem to expect; it makes sense.
see version 0.49d: 'deseed' and 'reseed' now export seed AND imported_keys
Warning: this changes the .seed format. You will not be able to call 'reseed' with the new version and an old .seed file.
Thanks so much for those bug fixes! As far as I can tell that completely fixes the problems that I listed as 1,2,3, and 5.
However, offline wallets and imported keys are still incompatible:
When you "electrum import:" followed by "electrum deseed" then "electrum addresses -k", is displayed.
However, offline wallets and imported keys are still incompatible:
When you "electrum import
I don't think so, because when it does go fine all the way to 152, it doesn't take longer to process addresses 115 and 116 than the others. I'll try to reproduce the error while in console mode to see I can get a traceback or something.
if you feel like debugging, you can uncomment the two lines in interface.py that contain "<--" and "-->"
it will display the messages sent and received from the server
Strange, I never seem to run into the issue when the console is enabled...
But I unfortunately don't have much more time to further investigate this right now.
And the issue is not a biggie for me, as I just need to kill and re-run Electrum, and the restore/sync
then complete fine.
I don't think so, because when it does go fine all the way to 152, it doesn't take longer to process addresses 115 and 116 than the others. I'll try to reproduce the error while in console mode to see I can get a traceback or something.
if you feel like debugging, you can uncomment the two lines in interface.py that contain "<--" and "-->"
it will display the messages sent and received from the server
It displays "synchronizing", but it seems that I do have to kill and restart it before it actually synchronizes.
My wallet file is approximately 500KB.
EDIT: I tried again, this time all went fine with no hiccups, and I found out that I actually have
152 addresses, not 115. So for some reason, it sometimes hangs at or around 115 for me.
My wallet file is approximately 500KB.
EDIT: I tried again, this time all went fine with no hiccups, and I found out that I actually have
152 addresses, not 115. So for some reason, it sometimes hangs at or around 115 for me.
maybe your 116th address has a very long history?
I don't think so, because when it does go fine all the way to 152, it doesn't take longer to process addresses 115 and 116 than the others. I'll try to reproduce the error while in console mode to see I can get a traceback or something.
It displays "synchronizing", but it seems that I do have to kill and restart it before it actually synchronizes.
My wallet file is approximately 500KB.
EDIT: I tried again, this time all went fine with no hiccups, and I found out that I actually have
152 addresses, not 115. So for some reason, it sometimes hangs at or around 115 for me.
My wallet file is approximately 500KB.
EDIT: I tried again, this time all went fine with no hiccups, and I found out that I actually have
152 addresses, not 115. So for some reason, it sometimes hangs at or around 115 for me.
maybe your 116th address has a very long history?
Thanks. I just tested it, and now I can see that when the process stalls
at the last address (115 for me) there is no more data received, and I have to
manually close the window. (First, I tried to wait for 3 minutes but nothing else
was happening)
For your info, I currently have about 250 entries/transactions in my history.
at the last address (115 for me) there is no more data received, and I have to
manually close the window. (First, I tried to wait for 3 minutes but nothing else
was happening)
For your info, I currently have about 250 entries/transactions in my history.
ok, if it stalls then there might be another bug.
it could be related to the large size of your wallet;
right after you close the window, does the client display "synchronizing", or is it immediately ready?
It displays "synchronizing", but it seems that I do have to kill and restart it before it actually synchronizes.
My wallet file is approximately 500KB.
EDIT: I tried again, this time all went fine with no hiccups, and I found out that I actually have
152 addresses, not 115. So for some reason, it sometimes hangs at or around 115 for me.
Jump to: