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. |
|
|
|
that's nice, thanks! please note that the list of messages is not up to date anymore; new ones are missing. |
|
|
|
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.
and how do you deal with the ugly column width and wasted screen real estate that this will create? |
|
|
|
|
I just pushed another important update with a new bitcoind patch.
it fixes memorypool issues.
|
|
|
|
This is more a question about the design philosophy of the server than specifics;
Why SQL database?
because I use abe. |
|
|
|
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?
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 just added a very basic DOS protection to the server code:
addresses with more than 200 inputs or output transactions will raise an error.
this means protection agains requests of the history of popular addresses (eg Satoshi Dice)
|
|
|
|
I would be good to make the documentation more comprehensible to the "normal" user.
sure. you are welcome to join the effort. my point is that the "normal" user should not import keys. |
|
|
|
I dont understand it:
The .seed file contains the private keys of imported addresses but they can't be restored from the seed?
Exactly. The .seed file does not only contain the seed. it also contains imported private keys. Importing keys is not a feature that I recommend to newbies. I was not very enthusiastic about adding that capability to Electrum, I did it because it was requested by some users. Please do not complain if it leads to confusion. |
|
|
|
Maybe I was wrong. So you can reseed imported addresses?
yes, the .seed file contains your seed and the private keys of imported addresses. -> reseedIs this information wrong? no, this information is not wrong. what is terribly misleadind is the use of the verb "reseed" with "imported addresses". |
|
|
|
will you loose any coins?
can you explain your question? When I update it, will I still have my coins afterword? Why would anyone put out an update to anything that caused directly or indirectly a loss of data or coins for any reason? That's absurd. I got confused to what he wrote..got the new version and it's working well. The new version of what? the client or the server? This thread is about the server, and the server does not manage your coins; the client does. This is why your question did not make sense to me. Please clarify. do you run an Electrum server? |
|
|
|
will you loose any coins?
can you explain your question? |
|
|
|
|
today I fixed a major performance issue with the server.
if you upgrade, please note that I updated the bitcoind patch. (for 0.6.2)
you need to recompile bitcoind with this new patch in order to complete the upgrade.
|
|
|
|
I see that bitcoin-abe and electrum/server have been updated. Should I go ahead an upgrade or should I wait until everything is stable?
Well, I went ahead and upgraded (after making a backup of the database). The server is outputting messages like those below. Should I be worried/should I restore from backup and downgrade? block number: 184242
WARNING: missing tx_in for tx 3977349
WARNING: missing tx_out for tx 3977349
block number: 184243
WARNING: missing tx_in for tx 3977352
block number: 184244
WARNING: missing tx_in for tx 3977356
block number: 184245
WARNING: missing tx_in for tx 3977404
block number: 184246
WARNING: missing tx_in for tx 3977413
block number: 184247
WARNING: missing tx_in for tx 3977461
block number: 184248
no, don't worry. I added these warnings after the last schema change in abe, but they seem to be harmless. |
|
|
|
All servers are up, I just checked.
btcback.com is down (bitcoind crashed) electrum.bitcoins.sk is broken (wrong number of blocks) that being said, I cannot reproduce vuce's problem |
|
|
|
@flatfly: did you finally fix the menu bug?
By the way, another thing that is somewhat related, but I'm not sure if it is Windows-specific or not: On Linux, what happens if you double-click on the balance of a transaction? For me, the context menu pops up, but at the very beginning of the line, not where the mouse pointer is. Anyway, not very important... it's normal. I just did not expect users to bring the menu that way...  |
|
|
|
|
version 0.58 is out.
main changes:
* the commands signmessage and verifymessages are compatible with the new compressed key format (thanks to nanotube for the patch)
* help buttons have been added in the settings dialog. gap limit setting moved back there.
|
|
|
|
|
Electrum has a 'watch_address' script that you can easily adapt to your needs
|
|
|
|
|
@flatfly: did you finally fix the menu bug?
could you make public all the modifications that you made to the code? I may want to merge that fix into the main branch.
I would like to see is a set of compilation instructions, so that independent reviewers can generate exactly the same build and check that they obtain the same sha1 hash
(I believe the bitcoin-qt client is verified that way)
|
|
|
|
I'm using electrum as a command line for a java application I wrote so I can't really use the GUI as an answer. Also what does it mean when i use a payto command it it gives me the following error: "Error: transaction rejected by memory pool
Then i get a long sequence of seemingly random letters and numbers.? the answer is on the previous page. in order to avoid answering several times the same question, I have started to update the documentation on the wiki, and I answered you there |
|
|
|
|
Show Posts
