issue so you can continue following this howto.
**Software.** A recent Linux distribution with the following software
-installed: `python`, `easy_install`, `git`, a SQL server, standard C/C++
+installed: `python`, `easy_install`, `git`, standard C/C++
build chain. You will need root access in order to install other software or
-Python libraries. You will need access to the SQL server to create users and
-databases.
-
-**Hardware.** Running a Bitcoin node and Electrum server is
-resource-intensive. At the time of this writing, the Bitcoin blockchain is
-3.5 GB large. The corresponding SQL database is about 4 time larger, so you
-should have a minimum of 14 GB free space. You should expect the total size
-to grow with time. CPU speed is also important, mostly for the initial block
-chain import, but also if you plan to run a public Electrum server, which
-could serve tens of concurrent requests. See step 6 below for some initial
-import benchmarks.
+Python libraries.
+
+**Hardware.** The lightest setup is a pruning server with diskspace
+requirements well under 1 GB growing very moderately and less taxing
+on I/O and CPU once it's up and running. However note that you also need
+to run bitcoind and keep a copy of the full blockchain, which is roughly
+9 GB in April 2013. If you have less than 2 GB of RAM make sure you limit
+bitcoind to 8 concurrent connections. If you have more ressources to
+spare you can run the server with a higher limit of historic transactions
+per address. CPU speed is also important, mostly for the initial block
+chain import, but also if you plan to run a public Electrum server, which
+could serve tens of concurrent requests. Any multi-core x86 CPU ~2009 or
+newer other than Atom should do for good performance.
Instructions
------------
-### Step 0. Create a user for running bitcoind and Electrum server
+### Step 1. Create a user for running bitcoind and Electrum server
This step is optional, but for better security and resource separation I
suggest you create a separate user just for running `bitcoind` and Electrum.
PATH="$HOME/bin:$PATH"
-### Step 1. Download and install Electrum
+### Step 2. Download and install Electrum
We will download the latest git snapshot for Electrum and 'install' it in
our ~/bin directory:
$ chmod +x ~/src/electrum/server/server.py
$ ln -s ~/src/electrum/server/server.py ~/bin/electrum
-### Step 2. Donwnload Bitcoind from git & patch it
+### Step 3. Download Bitcoind stable from git & patch it
-In order for the latest versions of Electrum to work properly we will need to use the latest
-build from Git and also patch it with an electrum specific patch.
+In order for the latest versions of Electrum to work properly we will need to use
+bitcoind 0.8.1 stable or higher. It can be downloaded from github and
+it needs to be patched with an electrum specific patch.
- $ cd src && git clone git://github.com/bitcoin/bitcoin.git
- $ cd bitcoin
- $ patch -p2 < ~/src/electrum/server/patch/patch
- $ cd src && make -f makefile.unix
+ $ cd src && wget http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.1/bitcoin-0.8.1-linux.tar.gz
+ $ tar xfz bitcoin-0.8.1-linux.tar.gz
+ $ cd bitcoin-0.8.1-linux
+ $ patch -p1 < ~/src/electrum/server/patch/patch
+ $ cd src && make USE_UPNP= -f makefile.unix
-### Step 3. Configure and start bitcoind
+### Step 4. Configure and start bitcoind
In order to allow Electrum to "talk" to `bitcoind`, we need to set up a RPC
username and password for `bitcoind`. We will then start `bitcoind` and
time, running as the 'bitcoin' user. Check your system documentation to
find out the best way to do this.
-### Step 4. Install Electrum dependencies
+### Step 5. Install Electrum dependencies
Electrum server depends on various standard Python libraries. These will be
already installed on your distribution, or can be installed with your
-package manager. Electrum also depends on two Python libraries which we wil
-l need to install "by hand": `Abe` and `JSONRPClib`.
+package manager. Electrum also depends on two Python libraries which we will
+need to install "by hand": `JSONRPClib`.
$ sudo easy_install jsonrpclib
- $ cd ~/src
- $ git clone git://github.com/jtobey/bitcoin-abe.git
- $ cd bitcoin-abe
- $ sudo python setup.py install
+ $ sudo apt-get install python-openssl
-Please note that the path below might be slightly different on your system,
-for example python2.6 or 2.8.
+### Step 6. Install leveldb
- $ sudo chmod +x /usr/local/lib/python2.7/dist-packages/Abe/abe.py
- $ ln -s /usr/local/lib/python2.7/dist-packages/Abe/abe.py ~/bin/abe
+ $ sudo apt-get install python-leveldb
+
+See the steps in README.leveldb for further details, especially if your system
+doesn't have the python-leveldb package.
-### Step 5. Configure the database
+### Step 7. Select your limit
-Electrum server uses a SQL database to store the blockchain data. In theory,
-it supports all databases supported by Abe. At the time of this writing,
-MySQL and PostgreSQL are tested and work ok, SQLite was tested and *does not
-work* with Electrum server.
+Electrum server uses leveldb to store transactions. You can choose
+how many spent transactions per address you want to store on the server.
+The default is 100, but there are also servers with 1000 or even 10000.
+Very few addresses have more than 10000 transactions. A limit this high
+can be considered to be equivalent to a "full" server. Full servers previously
+used abe to store the blockchain. The use of abe for electrum servers is now
+deprecated.
-For MySQL:
+The pruning server uses leveldb and keeps a smaller and
+faster database by pruning spent transactions. It's a lot quicker to get up
+and running and requires less maintenance and diskspace than abe.
- $ mysql -u root -p
- mysql> create user 'electrum'@'localhost' identified by '<db-password>';
- mysql> create database electrum;
- mysql> grant all on electrum.* to 'electrum'@'localhost';
- mysql> exit
+The section in the configuration file looks like this:
-For PostgreSQL:
+ [leveldb]
+ path = /path/to/your/database
+ # for each address, history will be pruned if it is longer than this limit
+ pruning_limit = 100
- TBW!
+### Step 8. Import blockchain into the database or download it
-### Step 6. Configure Abe and import blockchain into the database
+As of April 2013 it takes between 6-24 hours to import 230k of blocks, depending
+on CPU speed, I/O speed and selected pruning limit.
-When you run Electrum server for the first time, it will automatically
-import the blockchain into the database, so it is safe to skip this step.
-However, our tests showed that, at the time of this writing, importing the
-blockchain via Abe is much faster (about 20-30 times faster) than
-allowing Electrum to do it.
+It's considerably faster to index in memory. You can use /dev/shm or indexing in RAM
+or create a tmpfs which will also use swap if you run out of memory:
- $ cp ~/src/bitcoin-abe/abe.conf ~/abe.conf
- $ $EDITOR ~/abe.conf
+ $ sudo mount -t tmpfs -o rw,nodev,nosuid,noatime,size=6000M,mode=0777 none /tmpfs
-For MySQL, you need these lines:
+At limit 100 the database comes to 2,6 GB with 230k blocks and takes roughly 6h to import in /dev/shm.
+At limit 1000 the database comes to 3,0 GB with 230k blocks and takes roughly 10h to import in /dev/shm.
+At limit 10000 the database comes to 3,5 GB with 230k blocks and takes roughly 24h to import in /dev/shm.
- dbtype MySQLdb
- connect-args = { "db" : "electrum", "user" : "electrum" , "passwd" : "<database-password>" }
+Alternatively you can fetch a pre-processed leveldb from the net
-For PostgreSQL, you need these lines:
+You can fetch recent copies of electrum leveldb databases and further instructions
+from the Electrum full archival server foundry at:
+http://electrum-foundry.no-ip.org/
- TBD!
-
-Start Abe:
-
- $ abe --config ~/abe.conf
-
-Abe will now start to import blocks. You will see a lot of lines like this:
-
- 'block_tx <block-number> <tx-number>'
-
-You should wait until you see this message on the screen:
-
- Listening on http://localhost:2750
-
-It means the blockchain is imported and you can exit Abe by pressing CTRL-C.
-You will not need to run Abe again after this step, Electrum server will
-update the blockchain by itself. We only used Abe because it is much faster
-for the initial import.
-
-Important notice: This is a *very* long process. Even on fast machines,
-expect it to take hours. Here are some benchmarks for importing
-~196K blocks (size of the Bitcoin blockchain at the time of this writing):
-
- * System 1: ~9 hours.
- * CPU: Intel Core i7 Q740 @ 1.73GHz
- * HDD: very fast SSD
- * System 2: ~55 hours.
- * CPU: Intel Xeon X3430 @ 2.40GHz
- * HDD: 2 x SATA in a RAID1.
-
-### Step 7. Configure Electrum server
+### Step 9. Configure Electrum server
Electrum reads a config file (/etc/electrum.conf) when starting up. This
file includes the database setup, bitcoind RPC setup, and a few other
$ sudo cp ~/src/electrum/server/electrum.conf.sample /etc/electrum.conf
$ sudo $EDITOR /etc/electrum.conf
-Write this in `electrum.conf`:
-
- # sample config for a public Electrum server
- [server]
- host = host-fqdn
- native_port = 50000
- stratum_tcp_port:50001
- stratum_http_port:8081
- password = <electrum-server-password>
- banner = Welcome to Electrum server!
- irc = yes
- cache = yes
-
- # sample config for a private server (does not advertise on IRC)
- [server]
- host = localhost
- native_port = 50000
- stratum_tcp_port:50001
- stratum_http_port:8081
- password = <electrum-server-password>
- banner = Welcome to my private Electrum server!
- irc = no
- cache = yes
-
- # database setup - MySQL
- [database]
- type = MySQLdb
- database = electrum
- username = electrum
- password = <database-password>
-
- # database setup - PostgreSQL
- TBD!
-
- # bitcoind RPC setup
- [bitcoind]
- host = localhost
- port = 8332
- user = <rpc-username>
- password = <rpc-password>
-
-### Step 8. (Finally!) Run Electrum server
+Go through the sample config options and set them to your liking.
+If you intend to run the server publicly have a look at README-IRC.md
+
+If you're looking to run SSL / HTTPS you need to generate a self-signed certificate
+using openssl. Otherwise you can just comment out the SSL / HTTPS ports and run
+without.
+
+### Step 10. (Finally!) Run Electrum server
The magic moment has come: you can now start your Electrum server:
`~/src/electrum/server`. You can use them as a starting point to create a
init script for your system.
-### 9. Test the Electrum server
+### Step 11. Test the Electrum server
We will assume you have a working Electrum client, a wallet and some
transactions history. You should start the client and click on the green
addresses and transactions history. You can see the number of blocks and
response time in the Server selection window. You should send/receive some
bitcoins to confirm that everything is working properly.
+
+### Step 12. Join us on IRC, subscribe to the server thread
+
+Say hi to the dev crew, other server operators and fans on
+irc.freenode.net #electrum and we'll try to congratulate you
+on supporting the community by running an Electrum node
+
+If you're operating a public Electrum server please subscribe
+to or regulary check the following thread:
+https://bitcointalk.org/index.php?topic=85475.0
+It'll contain announcements about important updates to Electrum
+server required for a smooth user experience.
git://git.novaco.in / electrum-server.git / blobdiff