Electrum server discussion thread

[ThomasV]

Today I updated the server source again, with a slight modification of the protocol (spv-related calls)
The current version of the protocol is 0.4 (visible in your server's irc "real name")
Please upgrade your server if you have not done so.

[1714489695]

1714489695

[1714489695]

1714489695

[1714489695]

1714489695

[1714489695]

1714489695

[1714489695]

1714489695

[ThomasV]

I pushed another server update: version 0.5

This version requires the latest version of bitcoind (currently in git head), compiled with a new patch that is in the directory "patch"

This new protocol sends serialized transactions directly to the client, and will be required by electrum 1.3 clients.
So, please update your servers; I know it is a pain to have to patch bitcoind again, but this is necessary for spv.

[Raize]

Is the HOWTO located below still accurate?
https://gitorious.org/electrum/server/blobs/master/HOWTO

Thanks.

[ThomasV]

Is the HOWTO located below still accurate?
https://gitorious.org/electrum/server/blobs/master/HOWTO

Thanks.

not really.
the best source of feedback is IRC

I have been working on a new sever backend, that uses only bitcoind and not Abe.
it is almost ready. I'll catch up with the docs after that

[Red Emerald]

Is the HOWTO located below still accurate?
https://gitorious.org/electrum/server/blobs/master/HOWTO

Thanks.

not really.
the best source of feedback is IRC

I have been working on a new sever backend, that uses only bitcoind and not Abe.
it is almost ready. I'll catch up with the docs after that

I'll test this the moment it's out! No libbitcoin or Abe?

[ThomasV]

I'll test this the moment it's out! No libbitcoin or Abe?

no libbitcoin, no abe
you can already test it, it is in the repo.

you need to 'backend=bitcoind' to your configuration file, and to update it frequently, because I am still making changes to it

[ThomasV]

we now have two pruning servers up and running:

ecdsa.org and electrum.novit.ro

if you restore your wallet from seed on one of those servers, your history will be pruned.
the 1.4 client does not display correctly the pruned history, but the version of the client in github does.
I will make a new release soon, to include this change.

[Red Emerald]

I'm still playing with this with my local VMs.

Hopefully I'll have a real server soon.

[Pontius]

ThomasV, a few questions:

Code:

./server.py info
type    address        sub  version  time
 TCP    <ip>           280      1.5  6.89
 TCP    <ip>             6      1.4  40529.56
 TCP    <ip>             7      1.4  9.17
 TCP    <ip>             9      1.4  9.19
 TCP    <my own ip>      0  unknown  0.00

First, could you explain what the column "sub" represents?
Second, any idea about tha last line? What is that?
And last - see the time value on the second line? I have such clients on a regular basis. Sometimes multiple at once. Any chance to limit the resources for a single client?

[ThomasV]

ThomasV, a few questions:

Code:

./server.py info
type    address        sub  version  time
 TCP    <ip>           280      1.5  6.89
 TCP    <ip>             6      1.4  40529.56
 TCP    <ip>             7      1.4  9.17
 TCP    <ip>             9      1.4  9.19
 TCP    <my own ip>      0  unknown  0.00

First, could you explain what the column "sub" represents?
Second, any idea about tha last line? What is that?
And last - see the time value on the second line? I have such clients on a regular basis. Sometimes multiple at once. Any chance to limit the resources for a single client?

sub = number of subscriptions
last line = the connection you make when you run the 'info' command
time is a ping time. the client sends a ping every minute. there is no timeout server side atm.

[Pontius]

time is a ping time. the client sends a ping every minute. there is no timeout server side atm.

Ah, I thought "time" would be "cpu time".  
Then they heavy load on the system it was just coincidence.

Btw, the new "leveldb" backend is just great. Nice work!

[slush]

Electrum server made great progress. I'm running latest version on electrum.bitcoin.cz for few days and everything works perfectly, plus RAM requirement dropped to half...

[BkkCoins]

I've been trying to setup and run an electrum server using the leveldb backend. I've followed the README.levedb and some details from the HOWTO.md but having a problem that seems to not be explained in anything I've read.

Code:

Warning: it looks like you are using a 32bit system. You may experience crashes caused by mmap
Traceback (most recent call last):
  File "/bin/electrum", line 113, in <module>
    ssl_certfile = config.get('server', 'ssl_certfile')
  File "/usr/lib/python2.7/ConfigParser.py", line 618, in get
    raise NoOptionError(option, section)
ConfigParser.NoOptionError: No option 'ssl_certfile' in section: 'server'

Obviously it's looking for a certificate but this is the only mention of that I've come across.

I'd like to just test it out first before dealing with a cert if possible. If not I can create a self signed one but where can I get real info, that isn't missing stuff like this, on how to get the server running.

[Tachikoma]

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

[BkkCoins]

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

Will a self signed one work? Presumably the client would need a root cert as well to verify or is it only used for encryption and not identity?

I manage my own root authority with TinyCA so it's easy enough for me to create one but generally in my web apps I always need to give my root to the app so it will accept it.

[Tachikoma]

I used a self signed one and as far as I know it's working fine. Good question though Thomas will probably enlighten us.

[BkkCoins]

Ok. So I created a cert/key and that seems to be working. No errors yet.

But now when I start electrum (server) it asks me for

Enter username for jsonrpc at localhost:8332: electrum
Enter password for electrum in jsonrpc at localhost:8332:

I've already configured this in /etc/electrum.conf so why is it asking? I also have the same values in bitcoin.conf.

Anyway, when I type in the values again it just keeps asking again... wha?

edit - forget it. I see the problem.

electrum didn't accept a blank user so I made one up and edited bitcoin.conf.
Didn't realize had to stop bitdoind first so it could start with new user name.
Now done and started fine. Now playing catch up.
I can see this will take a while... la di da.

[StatelessSweety]

My electrum bitcoin wallet 1.4 is saying "Not connected" and my balance isn't showing. I'm a newb to the technology, not transacting.

Can anyone suggest anything?

[BkkCoins]

My electrum bitcoin wallet 1.4 is saying "Not connected" and my balance isn't showing. I'm a newb to the technology, not transacting.

Can anyone suggest anything?

You can try connecting to a different server. On the "classic" gui there is a round icon bottom right. Try that. It's also fairly likely you will need to upgrade because many recent changes could cause an older version to not connect. Current now I think is 1.5.6.

After changing server you should expect in 5-10 seconds that it starts synchronizing. If not and several servers respond the same then I'd say upgrade.

[MoonShadow]

Okay, I've been trying out Electrum as a portable solution, but find I seem to be inhibited in many public places.  I presume due to firewalls that prohibit high number/non-standard ports.  Is there a public server that can fake being a standard webserver using port 80?  Can this even ben done?