Topic: [ANNOUNCE] Electrum - Lightweight Bitcoin Client - page 55. (Read 274562 times)
Works now, thanks!
I released version 0.59
novelties:
- russian translation
- help buttons in send tab
- use_change is now a preference stored in the wallet
- new script: get_history
- minor fixes
novelties:
- russian translation
- help buttons in send tab
- use_change is now a preference stored in the wallet
- new script: get_history
- minor fixes
On Windows I get:
python-ecdsa does not seem to be installed. Try 'sudo pip install ecdsa'
Any tips?
sorry, the zip file was incomplete. try again now.
I released version 0.59
novelties:
- russian translation
- help buttons in send tab
- use_change is now a preference stored in the wallet
- new script: get_history
- minor fixes
novelties:
- russian translation
- help buttons in send tab
- use_change is now a preference stored in the wallet
- new script: get_history
- minor fixes
On Windows I get:
python-ecdsa does not seem to be installed. Try 'sudo pip install ecdsa'
Any tips?
I was following those instructions. But it turns out that the address I was trying to use was frozen. 
Figured it out now.
Figured it out now. I'm having a bit of trouble figuring out offline transactions. When I tried it with electrum -w wallet mktx I got an error that says I don't have enough funds. Indeed, if I use -o balance, it says my wallet has 0 balance. How can I get Electrum to recognize my true wallet balance when it is offline? The wallet I'm using does contain all the transaction history so it should know its most recent balance...
you have to follow the steps explained here: https://en.bitcoin.it/wiki/Electrum#Offline_wallet
I released version 0.59
novelties:
- russian translation
- help buttons in send tab
- use_change is now a preference stored in the wallet
- new script: get_history
- minor fixes
novelties:
- russian translation
- help buttons in send tab
- use_change is now a preference stored in the wallet
- new script: get_history
- minor fixes
I'm having a bit of trouble figuring out offline transactions. When I tried it with electrum -w wallet mktx I got an error that says I don't have enough funds. Indeed, if I use -o balance, it says my wallet has 0 balance. How can I get Electrum to recognize my true wallet balance when it is offline? The wallet I'm using does contain all the transaction history so it should know its most recent balance...
There seems to be a little bug in the history command: notice the "1e+12" at the end.
Running 0.58, and the wallet has 509 transactions. Not sure what other details to give.
2012-06-15 10:33:26 95517207518270a0d183e480e4360b5279a8d8f7c861a75bed7dcd6a7d2cacb7 -0.153 5.433
2012-06-15 10:33:26 54d8e141d140e286ca21f41ed6c7172ed848b100b8dff58be89de080860e822b -0.153 5.28
2012-06-15 10:50:56 6e5b824bcf993144cef7c5d88cfe8954e778e30302623186ac6fdf2a4cc12ed2 -0.148 5.132
2012-06-15 10:50:56 a0cca5600d3166f7e1cf5139e01b18909e7301681ef71b9270cb8acb575ba71e -0.128 5.004
2012-06-15 19:40:02 53c5f2fd77c44fed491a63e3516470def7db23e8dc707b86df6b293cbf5f4540 -0.329 4.675
2012-06-15 19:45:06 5c014afc0593d7f08e1593cd7826e03c900f2d9dcd9bb2c74d2dd5ddb74ac181 0.163 4.838
1e+12
pending d2bf12d6ccb27831277d3e9bca32c4a94f1a43294cab25155b98aa3848beca11 -0.329 4.509
# balance: 4.509
Running 0.58, and the wallet has 509 transactions. Not sure what other details to give.
Quote
2012-06-15 10:33:26 95517207518270a0d183e480e4360b5279a8d8f7c861a75bed7dcd6a7d2cacb7 -0.153 5.433
2012-06-15 10:33:26 54d8e141d140e286ca21f41ed6c7172ed848b100b8dff58be89de080860e822b -0.153 5.28
2012-06-15 10:50:56 6e5b824bcf993144cef7c5d88cfe8954e778e30302623186ac6fdf2a4cc12ed2 -0.148 5.132
2012-06-15 10:50:56 a0cca5600d3166f7e1cf5139e01b18909e7301681ef71b9270cb8acb575ba71e -0.128 5.004
2012-06-15 19:40:02 53c5f2fd77c44fed491a63e3516470def7db23e8dc707b86df6b293cbf5f4540 -0.329 4.675
2012-06-15 19:45:06 5c014afc0593d7f08e1593cd7826e03c900f2d9dcd9bb2c74d2dd5ddb74ac181 0.163 4.838
1e+12
pending d2bf12d6ccb27831277d3e9bca32c4a94f1a43294cab25155b98aa3848beca11 -0.329 4.509
# balance: 4.509
The change you made for seedless wallets wasn't strictly necessary, as my fix had already taken that into account (even though that wasn't easily apparent, I admit).
does that mean that a single call to setCurrentIndex would have been sufficient?
please explain things; do not assume others have information you do not share.
No, a single call doesn't fix it, but switching to the contacts tab (index 3 for seeded wallets) then back to history does.
And then I added the setCurrentIndex(2) to account for the seedless mode.
that means that a single call to setCurrentIndex() is sufficient.
No, I've tested that, it's 2 calls, in each case. (setCurrentIndex(0) is always needed at the end to make the fix transparent to the user)
this is what I meant: https://gitorious.org/electrum/electrum/commit/3d9eb32b50bf55b54d74e52dd86bd106325a802e
Oh yeah, indeed that's perfect now.
The change you made for seedless wallets wasn't strictly necessary, as my fix had already taken that into account (even though that wasn't easily apparent, I admit).
does that mean that a single call to setCurrentIndex would have been sufficient?
please explain things; do not assume others have information you do not share.
No, a single call doesn't fix it, but switching to the contacts tab (index 3 for seeded wallets) then back to history does.
And then I added the setCurrentIndex(2) to account for the seedless mode.
that means that a single call to setCurrentIndex() is sufficient.
No, I've tested that, it's 2 calls, in each case. (setCurrentIndex(0) is always needed at the end to make the fix transparent to the user)
this is what I meant: https://gitorious.org/electrum/electrum/commit/3d9eb32b50bf55b54d74e52dd86bd106325a802e
The change you made for seedless wallets wasn't strictly necessary, as my fix had already taken that into account (even though that wasn't easily apparent, I admit).
does that mean that a single call to setCurrentIndex would have been sufficient?
please explain things; do not assume others have information you do not share.
No, a single call doesn't fix it, but switching to the contacts tab (index 3 for seeded wallets) then back to history does.
And then I added the setCurrentIndex(2) to account for the seedless mode.
that means that a single call to setCurrentIndex() is sufficient.
No, I've tested that, it's 2 calls, in each case. (setCurrentIndex(0) is always needed at the end to make the fix transparent to the user)
The change you made for seedless wallets wasn't strictly necessary, as my fix had already taken that into account (even though that wasn't easily apparent, I admit).
does that mean that a single call to setCurrentIndex would have been sufficient?
please explain things; do not assume others have information you do not share.
No, a single call doesn't fix it, but switching to the contacts tab (index 3 for seeded wallets) then back to history does.
And then I added the setCurrentIndex(2) to account for the seedless mode.
that means that a single call to setCurrentIndex() is sufficient.
The change you made for seedless wallets wasn't strictly necessary, as my fix had already taken that into account (even though that wasn't easily apparent, I admit).
does that mean that a single call to setCurrentIndex would have been sufficient?
please explain things; do not assume others have information you do not share.
No, a single call doesn't fix it, but switching to the contacts tab (index 3 for seeded wallets) then back to history does.
And then I added the setCurrentIndex(2) to account for the seedless mode.
Exactly why this works, I have no idea - I'm currently not a Python coder at all, so that was just a quick hack, found through experimenting.
The root cause of the issue could be a bug in the Windows implementation of PyQt, but I'm not sure.
I have received 109 transactions on one specific address and about ~120 in total. And now I get the error all the time. What should I do in order to be able to access the coins connected to that address? And what happens if more transactions are sent to that address now when I have reached the limit?
Which server are you using?
I recently raised the limit to 500 on ecdsa.org, and I did not see any request rejection since then.
The limit on sql requests is an experimental feature; please understand that this is not its final form.
Future versions of the client will handle this limit more gracefully; the server will send its policy to
the client, and the client will be able to detect that it needs to use another server.
My goal is to make a distinction between users who do not use a lot of resources, and heavy users, who
will be redirected to other (possibly commercial) servers.
The electrum service will remain free at ecdsa.org, and that server will keep running on donations;
however, this free service will come with limitations on the request that your client can do.
Other server operators will be free to decide what their sql limit policy is, and whether they want to
run on donations or to charge a small fee. I expect this to have a load-balancing effect, and to create
an incentive to run more servers.
It is not possible at the moment to tell you how high the final limit will be at ecdsa.org.
There are various software and protocol improvements that we need to investigate, and
that are likely to offset that limit.
When I run Electrum I get the following error:
Connected to ecdsa.org:50001
received error: {u'id': 4, u'error': u'limit reached'}
What in the what now?
Connected to ecdsa.org:50001
received error: {u'id': 4, u'error': u'limit reached'}
What in the what now?
I added a limit on the number of transactions that can be returned on requested addresses.
it is a DOS prevention measure.
the limit is probably too low. I will raise it if necessary.
I have received 109 transactions on one specific address and about ~120 in total. And now I get the error all the time. What should I do in order to be able to access the coins connected to that address? And what happens if more transactions are sent to that address now when I have reached the limit?
The change you made for seedless wallets wasn't strictly necessary, as my fix had already taken that into account (even though that wasn't easily apparent, I admit).
does that mean that a single call to setCurrentIndex would have been sufficient?
please explain things; do not assume others have information you do not share.
I added Russian translation for client into https://en.bitcoin.it/wiki/Electrum/Translation
that's nice, thanks!please note that the list of messages is not up to date anymore; new ones are missing.
I added Russian translation for client into https://en.bitcoin.it/wiki/Electrum/Translation
Just a little suggestion: renaming the column to "Payments received" rather than "Received"?
That way, you can keep using numbers as values, as for the Tx column, and easily avoid dealing with the ugly "1 times" case.
That way, you can keep using numbers as values, as for the Tx column, and easily avoid dealing with the ugly "1 times" case.
and how do you deal with the ugly column width and wasted screen real estate that this will create?
Yes you're right... Or just "Payments" as title, then? Or you can leave it like now, not such a big deal. (even though I don't like to see "1 times" but OK...)
Or another option: "Rx" (short for "received", the natural opposite of "Tx")
By the way, thanks for merging my magic fix
. The change you made for seedless wallets wasn't strictly necessary, as my fix had already taken that into account (even though that wasn't easily apparent, I admit). Anyway, I can confirm it works fine. Just a little suggestion: renaming the column to "Payments received" rather than "Received"?
That way, you can keep using numbers as values, as for the Tx column, and easily avoid dealing with the ugly "1 times" case.
That way, you can keep using numbers as values, as for the Tx column, and easily avoid dealing with the ugly "1 times" case.
and how do you deal with the ugly column width and wasted screen real estate that this will create?
Jump to: