|
I used a self signed one and as far as I know it's working fine. Good question though Thomas will probably enlighten us.
|
|
|
|
|
This is a new addition in the latest server updates. It means you can run a connection from the client to the server over SSL. Just generate a self-signed certificate and add the config option to /etc/electrum.conf
|
|
|
|
I don't know if it has been said already. But in Mac OSX Mountain Lion when you install Homebrew, you also need to have Xcode installed with the Command Line Tool added.
It also ask for a new git version, but you need to set all the things above first.
I'm waiting for the Xcode to download and install. I'll write here with updates.
Sorry about that, since I have that installed all the time it's hard to find out what's needed exactly. I've build you a binary 1.5.6 release in case you or others don't want to bother with all that: Electrum 1.5.6. Edit: I've added the binary to the offical download page. If you use it please let me know on which versions of OS X it works and which not. My last build environment could only build for 10.7 and up. Wondering if these build also work on 10.6. |
|
|
|
|
Which server is it connecting to now? I think the response from the server is not as expected, at least that looks to be case.
|
|
|
|
I somehow got a corrupted electrum.dat file today. I restored from a backup of two days ago and started electrum from cmd line. It gave me this error even though this file worked fine a couple days ago, and electrum worked fine this morning (hours ago). I'm using kind of an old version, 1.0 I believe but with some of my patches. Is there some reason that today the wallet would get corrupted by a new server version or something? Apparently I'm using electrum.bytesized-hosting.com but when I ran just now it would not sync and I tried to change servers, and restart. That's when it would not start any more. After restoring the screen opens and says "synchronizing" but this traceback is spit out in terminal. electrum
Install zbar package to enable QR scans
No servers loaded yet.
Connected to electrum.bytesized-hosting.com:50001
Servers loaded.
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 551, in __bootstrap_inner
self.run()
File "/usr/local/lib/python2.7/dist-packages/electrum/interface.py", line 456, in run
self.handle_response(response)
File "/usr/local/lib/python2.7/dist-packages/electrum/interface.py", line 406, in handle_response
self.wallet.receive_history_callback(addr, result)
File "/usr/local/lib/python2.7/dist-packages/electrum/wallet.py", line 886, in receive_history_callback
self.update_tx_history()
File "/usr/local/lib/python2.7/dist-packages/electrum/wallet.py", line 906, in update_tx_history
line['value'] += tx['value']
KeyError: 'value'
That server should not even be online, it's not running Electrum bitcoin server anymore. The server got moved to electrum.bysh.me. That IP is still running a old version of the Electrum Litecoin server. Perhaps somehow you got Litecoin data in your Bitcoin wallet? |
|
|
|
I love this software! It works fast and has the exact set of features I need!
Just one question: why would one want to run a public Electrum server, is there any incentive to do so?
For the moment there is no financial incentive to do so. But I guess this could change in the future; servers operators could charge a small fee for the service they provide. I think it's very hard to offer something on a paid server that a non-paid server can't do. There has to be an incentive to pay for the server, something that differs from the free servers. |
|
|
|
I love this software! It works fast and has the exact set of features I need!
Just one question: why would one want to run a public Electrum server, is there any incentive to do so?
There is no incentive except supporting Electrum. |
|
|
|
|
Is /usr/local/bin/electrum a symlink and if so, where does it link to?
Did you install the initial version via git as well or via pip?
|
|
|
|
|
Then the only logical conclusion is that the "sudo python setup.py install" command failed.
|
|
|
|
|
Does it run if you issue ./electrum from the source folder?
|
|
|
|
|
I'm going to assume you are on Ubuntu. Try an apt-get install gettext and running all the commands again. If you don't install it system wide be sure to launch it with ./electrum from your source folder.
|
|
|
|
Sending transactions can take up to 30 seconds in my experience. I don't know what could have happened but it could be that your wallet is damaged. Thomas might have a better clue  |
|
|
|
I've made binary release of 1.5 for those of you on OS X. It will most likely work from 10.7 and on but feel free to test it and let me know. |
|
|
|
this is a major protocol change and 1.3 clients cannot use old servers; if you use the recent git version you will notice that the client does not even report the old servers).
What about the "old" servers? Can we still use the old clients? Old clients can use new and old servers as far as I am aware. |
|
|
|
|
I'm shutting it down for now. I don't have the time I need at the moment to finish it properly. If I find the time I will put it back online.
|
|
|
|
The script picks up all running servers, my guess is he did not close down his old one yet as I did remove it from eyelectrum.
That's strange. When I run slushs script ( http://pastebin.com/UsBWCU4n) "uncle-enzo" is only displayed once. Two other things/questions: - I subscribed to my server on 'eyelectrum' but didn't get any notification when the server failed. - I restarted the server about 90 minutes ago and it's running fine now. On 'eyelectrum' it is still listed as lagging. What's the update frequency on 'eyelectrum'? Slush's script doesn't pick up servers that come back, for me at least. Thomas created a new version and I will probably start using that one. You should get an email as soon as you are three blocks behind. |
|
|
|
|
The script picks up all running servers, my guess is he did not close down his old one yet as I did remove it from eyelectrum.
|
|
|
|
No offense but why would you start an argument on the bitcoin-development mailing list about a client that has a specific thread on the bitcoin forums. I for one am on no mailing list simply because I hate even more mail then I already get. If you want a serious argument gmaxwell should have taken it here. Besides I think that you Thomas are the only one who can really answer those questions since you wrote all the cryptography bits anyway Can anybody point me in the direction of some documentation about this SPV? I couldn't find anything substancial but it sounds interesting. |
|
|
|
How so? If you use -g it overrides the gui just for one run. If you use -w it uses the wallet you specify but doesn't change the default. It's pretty normal for a cmd line option not to alter default configs. Until recent changes there wasn't even a saved config outside the wallet. I don't think that the cmd line options should be used to alter the saved config permanently. Unless it's explicit, like a -save option. IMO.
I totally agree that the command line option should not alter the setting. this is not what I meant. my point is, if the user opens the "network" window and then clicks "ok", they might expect the setting that is displayed to be saved. I think I'm misunderstanding the problem you lined out. What happens right now is the following: 1. If you supply the --proxy argument and don't open the server window it's handled as a one time off parameter. 2. If you supply the --proxy argument and open the server window and press ok it gets saved to the config. Which of those situations should be different? The commit that disabled the Gui when no proxy option is selected can be found here, I would appreciate a review. |
|
|
|
|
Show Posts
