Topic: Electrum server discussion thread - page 11. (Read 61443 times)

Here's the format change which makes the foundry full tree version (from Feb 17th) unusable:
https://github.com/spesmilo/electrum-server/commit/7164e2928d341fe197b68a9966542e7be1e26709
https://github.com/spesmilo/electrum-server/commit/2a8c19f5f3bdae38e9ef89bf7515dc10a7bb1893

And there's already somebody building a 10k db. I guess you'll be better of if you just wait for his db.

Just in case someone is having the same trouble as me.  When I ran the foundry fulltree version from Feb I got an error saying it was deprecated.  I imagine something in the format changed.  Anyways, I am building a db with 10000 pruning limit with fulltree.  It is going and when it is done I'll tar it up and post it for others.  I only have it going at an acceptable speed by using a high memory Google Compute Engine node and having it all in RAM.  Even so, it is not fast.

If someone wants me to, I can continue to tar and make available these snapshots.

[04/03/2014-16:28:35] catch_up: block 187000 (6.610s 399.142s) d14d45e45081f4cc72ecce4d0e6ca2f3a038f8e2a3d61e63c7a9646ceef225d3

Cool.

Is turning on irc in the config the thing to do to advertise your node?

Will there be foundry release of fulltree with a pruning limit of greater than 100? 

please note that the branch "fulltree" was merged to "master".
this means that if you pull, you will need to recreate your database, or import it from the foundry.
you will also need to install plyvel.
use the 'start' and 'stop' scripts to start and stop the server.

Hello i have sucessfully instaled and around two months testing our electrum server
electrum.psko.net
network:IPv4
ports: 8081,8082,50001,50002
location: Modra,Slovakia

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Important: The onion address for electrum.icetwy.re has changed. This is a purely cosmetic modification, in order to have an onion address starting with "electrum".

New address: electrum2vikbmxv.onion
Previous address: 2aspcrrdseyvlaod.onion

The change has already been in effect for a few weeks now. Thanks to the user who reminded me of this!

I've signed this message and the original one with my PGP key, 0x029F116A (see my blog).
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQQcBAEBCgAGBQJSthZbAAoJED6/9j8CnxFqUsIf/2mswGD6vFMiYEumgHIDjBKi
JWj3iUGRzHpB3dU+aj4RMXX8Y/Ix/yVDxAz7SACg3ABbK2iZmsxSJ2TTXE9f4v3/
foB6cfQYwWfEcB6gAYfwtz//2fEjgpgKAZnHZUlDhFUz9Yw3tel5w/hvmovXkm9w
s32UegVAmL6xhhgZ1TQW2RHAOkQrQPRESXDekOrDT+oK6rndwbxs3VboQsDZWit/
pySVJoGhq7oidj4qJzSEqqsTs0gU0sZXGj//++NvymStiTfiMKPsZ1ZobJvtK9jX
458N5LI/d/iK8tNW8xWxlHv+rdEoBQb3pzK5MyoHqdKjpK08TWv4B/pNiUGdZqr7
JC1T1TFAqqZE9lwSXoWom24y7IScA3xQgzl6YYgVKGBE/q5Gb8ATjIiBfsUJGh3z
W41oJZr2TdGlfm9NRp5VBlCboFW77ZGaesCScOnV3EA4AfYDzh2qDoi7A2cD18zo
WwJLx1/3pCwkysZIn71EATMUxrAWZGp54sQ4qTYNtM0rcgyrjxeAExafAV6GinoU
u4dIzQS/wbCtIEfXX+6EDjGZcDYL20/pElXNuT32sXaaSWQLuPWWPOyMrKfuosYM
Jem1e4a1eUwwXrZRl0SbzHJBrdxukJlPSL7jXha+8UYxcmGNEu9UlL4NqszTJR7z
oCBhgByJfs+7yeTHIj0fIRBMkHc2PLlReUKG6KjKtFtFxNOGcOVSl8nnuN2U0lm2
XQ2Z4HJH9EtEm/ovnR0UKCr63O+bSKC9pe4FP97ygZSX8ihuOUPieaUfvy7PaAHW
tFTMlC8vcUPqiwM45J7Kcc/M+cl7vjz4Axs+lkANI/2I04jtDP8dI1mofg33vJwk
phZbhfsctz18rzFzeeeRGCTK3LG4LwADVKjq6l/5hX9I4JzODfsZMc7jq4coFXXS
pNEFbfBdAzGZuFkKDDGgfkB1zJdFkHyKNY39GPCgkxTo+QGZ1fZo3TF/YPy9q7Dg
NEspnQWYdOzaXXD5mz7Eu37D/GoH+Dr/A04WPWRN1jio7/rUS3jsl7HVxt7HxdPT
VxLl8CaAJlDj5OhyfAR0WaLejn0qngFmJEbsxXhiz1pEP20xSGUPln1quc/a7eZu
+ne07ooUmpXSPmkMpuUg2bUpGoIMmvugkErb14dPcDQE46VPdfU3iBcczS981hQm
rVRfct4DKkG4IRvjSkv/Xsfc0T+uq2YEGE8fKQGe6mshH3cbPDbJ50qcPtRfnJ8P
RTIjUMb8sO4uuiLGByc/Ah5Gf3phCYHxX9OGuWCOUM1krBRGuFXPfLNnyRjiUMk3
uU2Lf+XshJRqYNoWQv6m97SgfDpVmwocE41HZF+t4p4qtpRf0OuzogwSfaeadlE=
=tx2b
-----END PGP SIGNATURE-----

There were quite a few more improvements to the server code in the past week! OPs are encouraged to git pull.

If you haven't pulled in a while: The server does no longer require bitcoind to be patched. You need run bitcoind with txindex=1 instead and may need to reindex once if you're adding the setting. Please see the HOWTO which is up2date: https://github.com/spesmilo/electrum-server/blob/master/HOWTO.md

I have setup a public server to help out.

hostname: electrum.cryptopush.com
network: IPv4 and IPv6
ports: 8081,8082,50001,50002
prune: 10000
location: NY,NY USA

I have also subscribed to this thread to keep up with new server developments.

Enjoy!

What are the average disk, cpu load and bandwidth requirements?

Someone said about 1gb of memory is used, I guess the block chain is what it is currently. So what about bandwidth and cpu?

OT:

After getting hit with the bitcoin-qt OSX block database corruption bugs, for months, with no obvious solution or even acknowledgement on the forums, and having the same corruption issues in a ubuntu VM if it wasn't treated with kid gloves, then switching to multi-bit and getting a little concerned over the Issues list on github, and the "magic" involved that apparently means it can ignore the full block chain, then using blockchain.info but watching how the reward for hacking these online wallets rises almost exponentially. Finally I'm on electrum and feel instantly comfortable with it!

Two memory leaks were fixed sunday and yesterday.
These leaks had been there for a long time, but were revealed by the release of the 1.9 client and its multiple connections.

Please git pull!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hey, I've just finished setting up my own Electrum server. It will remain public.

The server is electrum.icetwy.re. Onion address for Tor users: electrum2vikbmxv.onion

Ports: 8081 (HTTP), 8082 (HTTPS), 50001 (TCP), 50002 (TCP+SSL).

More info is available in the console upon connecting to the server. Enjoy

(Edited on Dec. 21st 2013: 2aspcrrdseyvlaod.onion => electrum2vikbmxv.onion, see here)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQQcBAEBCgAGBQJSthYBAAoJED6/9j8CnxFqDK0f/jsJ0oehVwTsiLmk37GZdgq3
F8/gtA2V3Ridvy032rl1UDSMpTYUfTTAuiLC9iAAsK2rCZd2ww99NurHi/PK9puC
lfVSBuFJx24X9n6kONWvnahYHjUeoIhujiVRhLo+9mNHCfW/eeODKgIS2y0Hff/r
8F5NX/tf4GtNA8TuuQoeR24a/7dWbP/+nZI1favYcdyoSj4gG6hPbBsu3RN3FITC
ko+VuCMn+vbeKjA+3QEqh3VFWvXKE/KQQQeuliZVKo5E9uA15+fMq9+JH4u0bfat
VpwVX8ZO6hDiHPO9f2Smj/W/gc4a+dvLFYphYLQE2uUf6zoe1lp8lgDZm2zoV20y
/9p3rKpO1Icb4fk5qIG9GsrAnuGlqET+koWPWOOxrIfWUmXr3p3jktapSqsvWiNn
4sfbTSAZi5RWMqNZ0o92gsctT8WQtwWiCklPl+Ufl5mNGq+0/Nojwr0HRKl+KP1H
pKgVLNVGhTTV+WR9JHKUYDYFvrmSDpxTvGzVd+by2eMe4I3DrWZEsvSo77wVwamx
KB2TqWBlZE+lJ9fzjfRHA1TmhzSXoUtYhwZpMAmCX1de20jUYHpFXMb0HSi10Kor
9fswbL05ia8IfgGAQ0OeVQA+dJexmPmxE4/JtSGK8PRaQwcB97CJmDC0l5jBm3VS
i8FtBLaD+SA9KVpydu/IcSWRecNbWt2Yc2QEJJz9Fll+y1/GO3xhz0es+OG4ngZJ
ahZzUs9YQOav5sWWZLkBmS2mdon1WfrSv3z98sAyZml3xPtDRc7qhrwwZ0i0FJ92
Osj3cT6492Zxxiloy1pB/dNDqghZ3QR/wuqBZehsvPwHLwTPR+yeL/4lbAfl21Rc
ND7an2wMiUCDm10fSiKCt3bUUpUFOtwPDe41eCGJ4kznfN8urNhmh3ObLPj36pHX
ZjU+Yv7SZ2JpnHVMFQJStGmogNe0gQIvjjZHcwYMx8xYLQGz5bSrMvb/g1CS57aC
uECjieTeRxdExFF/WSKCZLDazYh1C9X7667U+sN8QgjABD48VYF2aHdlhd54en2v
fLBk3fC9429tOTVwFxpPT3n9Jgl4X9jrrkx9ooQMVtksLlErpgGM6yg3gutBkTyT
Zl2C7yjSaTNpxdCMbB7QzuaYHNL8C+/H7rZLE0S7JYxidqXRy0j5aYlb5EULoZ1/
vX93qF0UwC0pvG+5ODGVY68RF5C3XkZqDFaW+qe/J/63o3YUY9666/7vlO8TBrHJ
XSXM0K0hBcvH4UcXSyu4TBTii+2gSc7rLOjT+Uh6FEQUXZhNB1MAbSHHHJBpEzx6
ZLlerm2IQodKwfjSrHC+GBd158u7EIpCjron/PaVWSLN3wy1ZG78ImwT8ehU7RY=
=kicY
-----END PGP SIGNATURE-----

Hello, im trying to setup my own electrum server, everything seems to be ok. I downloaded the leveldb database file and synchronized to current. Server has started, but if I try to connect to it with my wallet, it got stuck on Synchronizing.
In the server log I can see:
But my local wallet got frozen and displays "Synchronizing..." on the status bar. There is not much load on the server, so I dont know what went wrong? When I connect to any other public server with my wallet, everything is ok.
The server is running further and processing blocks, but wallet is still saying "Synchronizing..."
Can anyone help, please?

we just detected and fixed a bug with the servers:
https://github.com/spesmilo/electrum-server/commit/4a82994032a48db0fc4be814091215c69891ab17

if you are running an Electrum server, please do a git pull;
(servers that have not updated their code are stuck at block 265457).

Hello,

I just introduced SSL certificate validation in the client code.
The client does accepts self-signed certificates.
However, it rejects expired certificates.

I noticed that a few servers have expired certificates, and are rejected by the client.
If that is your case, please create a new certificate for your server; you may set its expiration date in 10 years.

It's python, no compile AFAIK. (I haven't tried running server on Windows though...)

Does anyone have a Windows compile of the latest Electrum server?

Yeah! I've just got my server to work on a linux VM with the help from the IRC channel and now I was wondering if I can make it run on windows.
Is there anything that will prevent me from compiling and running the electrum server on a windows machine?

To server ops: You can upgrade to bitcoind 0.8.4 without any problems with the current electrum-server code. Just apply the known patch and compile.

I've updated the howto accordingly: https://github.com/spesmilo/electrum-server/blob/master/HOWTO.md

Thank you! I think that solved it. I changed from 'host=localhost' to 'host=0.0.0.0', and I commented out the 'password=secret'. This isn't the bitcoind section, so I don't think it's the bitcoin password. I DO have the bitcoin password set in the bitcoind section.

Anyway, now I can connect REMOTELY using TCP, SSL, HTTP, and HTTPS.

Cool... If this works, I'll be running another public electrum server soon. Electrum is really the ONLY wallet that doesn't suck in some way.
[I hope Thomas doesn't take offense to this. This is my highest compliment.]