You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

299 lines
11 KiB

8 years ago
.. image:: https://travis-ci.org/kyuupichan/electrumx.svg?branch=master
:target: https://travis-ci.org/kyuupichan/electrumx
.. image:: https://coveralls.io/repos/github/kyuupichan/electrumx/badge.svg
:target: https://coveralls.io/github/kyuupichan/electrumx
8 years ago
===============================================
ElectrumX - Reimplementation of electrum-server
8 years ago
===============================================
8 years ago
For a future network with bigger blocks.
:Licence: MIT
:Language: Python (>= 3.5.3)
:Author: Neil Booth
8 years ago
Getting Started
===============
8 years ago
See `docs/HOWTO.rst`_.
There is also an `installer`_ available that simplifies the installation on various Linux-based distributions.
There is also an `Dockerfile`_ available .
.. _installer: https://github.com/bauerj/electrumx-installer
.. _Dockerfile: https://github.com/followtheart/electrumx-docker
8 years ago
Features
========
- Efficient, lightweight reimplementation of electrum-server
8 years ago
- Fast synchronization of bitcoin mainnet from Genesis. Recent
8 years ago
hardware should synchronize in well under 24 hours. The fastest
time to height 448k (mid January 2017) reported is under 4h 30m. On
the same hardware JElectrum would take around 4 days and
electrum-server probably around 1 month.
- The full Electrum protocol is implemented. The only exception is
the blockchain.address.get_proof RPC call, which is not used by
Electrum GUI clients, and can only be invoked from the command line.
- Various configurable means of controlling resource consumption and
handling denial of service attacks. These include maximum
connection counts, subscription limits per-connection and across all
connections, maximum response size, per-session bandwidth limits,
and session timeouts.
- Minimal resource usage once caught up and serving clients; tracking the
transaction mempool appears to be the most expensive part.
- Fully asynchronous processing of new blocks, mempool updates, and
client requests. Busy clients should not noticeably impede other
clients' requests and notifications, nor the processing of incoming
blocks and mempool updates.
- Daemon failover. More than one daemon can be specified, and
ElectrumX will failover round-robin style if the current one fails
for any reason.
8 years ago
- Peer discovery protocol removes need for IRC
8 years ago
- Coin abstraction makes compatible altcoin and testnet support easy.
8 years ago
Motivation
==========
8 years ago
Mainly for privacy reasons, I have long wanted to run my own Electrum
server, but I struggled to set it up or get it to work on my
DragonFlyBSD system and lost interest for over a year.
8 years ago
8 years ago
In September 2016 I heard that electrum-server databases were getting
8 years ago
large (35-45GB when gzipped), and it would take several weeks to sync
from Genesis (and was sufficiently painful that no one seems to have
done it for about a year). This made me curious about improvements
and after taking a look at the code I decided to try a different
approach.
8 years ago
I prefer Python3 over Python2, and the fact that Electrum is stuck on
Python2 has been frustrating for a while. It's easier to change the
8 years ago
server to Python3 than the client, so I decided to write my effort in
Python3.
8 years ago
8 years ago
It also seemed like a good opportunity to learn about asyncio, a
wonderful and powerful feature introduced in Python 3.4.
Incidentally, asyncio would also make a much better way to implement
8 years ago
the Electrum client.
Finally though no fan of most altcoins I wanted to write a codebase
that could easily be reused for those alts that are reasonably
compatible with Bitcoin. Such an abstraction is also useful for
8 years ago
testnets.
8 years ago
Implementation
==============
8 years ago
ElectrumX does not do any pruning or throwing away of history. I want
to retain this property for as long as it is feasible, and it appears
efficiently achievable for the forseeable future with plain Python.
8 years ago
8 years ago
The following all play a part in making ElectrumX very efficient as a
Python blockchain indexer:
8 years ago
- aggressive caching and batching of DB writes
- more compact and efficient representation of UTXOs, address index,
and history. Electrum Server stores full transaction hash and
height for each UTXO, and does the same in its pruned history. In
contrast ElectrumX just stores the transaction number in the linear
history of transactions. For at least another 5 years this
transaction number will fit in a 4-byte integer, and when necessary
expanding to 5 or 6 bytes is trivial. ElectrumX can determine block
height from a simple binary search of tx counts stored on disk.
ElectrumX stores historical transaction hashes in a linear array on
disk.
- placing static append-only metadata indexable by position on disk
rather than in levelDB. It would be nice to do this for histories
but I cannot think of a way.
- avoiding unnecessary or redundant computations, such as converting
address hashes to human-readable ASCII strings with expensive bignum
arithmetic, and then back again.
- better choice of Python data structures giving lower memory usage as
well as faster traversal
- leveraging asyncio for asynchronous prefetch of blocks to mostly
eliminate CPU idling. As a Python program ElectrumX is unavoidably
single-threaded in its essence; we must keep that CPU core busy.
8 years ago
Python's ``asyncio`` means ElectrumX has no (direct) use for threads
and associated complications.
8 years ago
Roadmap
=======
8 years ago
- Require Python 3.6, which has several performance improvements
relevant to ElectrumX
- offloading more work to synchronize to the client
- supporting better client privacy
- wallet server engine
8 years ago
- new features such as possibly adding label server functionality
- potentially move some functionality to C or C++
8 years ago
8 years ago
ChangeLog
=========
7 years ago
Version 1.2
-----------
IMPORTANT: this release changes script hash indexing in the database,
so you will need to rebuild your databases from scratch. Running this
version will refuse to open the DB and not corrupt it, so you can
revert to 1.1.x if you wish. The initial synchronisation process
should be around 10-15% faster than 1.1, owing to this change and
Justin Arthur's optimisations from 1.1.1.
- separate P2PKH from P2PK entries in the history and UTXO databases.
These were previously amalgamated by address as that is what
electrum-server used to do. However Electrum didn't handle P2PK
spends correctly and now the protocol admits subscriptions by script
hash there is no need to have these merged any more.
7 years ago
Version 1.1.2
-------------
7 years ago
- PEER_DISCOVERY environment variable is now tri-state (fixes
`#287`_). Please check your setting as its meaning has changed
slightly.
- fix listunspent protocol methods to remove in-mempool spends (fixes
`#277`_).
7 years ago
- improved environment variable handling
- EMC2 update (cipig), Monacoin update (cryptocoin-junkey),
Canada Ecoin (koad)
- typo fixes, Bitcoin testnet peers updates (SomberNight)
7 years ago
Version 1.1.1
-------------
- various refactorings, improvement of env var handling
- update docs to match
- various optimizations mainly affecting initial sync (Justin Arthur)
- Dash fixes (cipig)
- Add ALLOW_ROOT option (Luke Childs)
- Add BitZeny support, update Monacoin (cryptocoin-junkey)
8 years ago
Version 1.1
-----------
See the changelogs below for recent changes. The most important is
that for mainnet bitcoin **NET** must now be *mainnet* and you must
choose a **COIN** from *BitcoinCash* and *BitcoinSegwit*. Similarly
for testnets. These coins will likely diverge further in future so
it's best they become separate coins now.
- no longer persist peers, rediscover on restart
- onion peers only reported if can connect; hard-coded exception removed
- small fix for blockchain.transaction.broadcast
8 years ago
Version 1.1pre2
---------------
- peerdisc: handle protocol 1.1 server replies
- issue `#251`_: fix protocol version reported in server.peers.subscribe
- fix handling of failed transaction broadcast
- fix typos (SomberNight)
- doc and test updates
- dash: return errors in JSON error field for protocol 1.1
8 years ago
Version 1.1pre1
---------------
Many changes, mostly to prepare for support of Electrum protocol 1.1
which the next Electrum client release will use.
*NOTE*: the **COIN** environment variable is now mandatory, and if you
were running for any bitcoin flavour (Cash, Segwit, mainnet or
8 years ago
testnet) you will need to update your **COIN** and **NET** environment
variable settings as the old ones will no longer work.
8 years ago
- implement protocol version 1.1 and update protocol documentation
- rework lib/coins.py for the various bitcoin flavours
- show protocol version in "sessions" ElectrumX RPC call
8 years ago
- permit **HOST** envvar to be a comma-separated list
- daemon abstraction refactoring (erasmospunk)
- permit alternative event loop policies (based on suggestion / work
of JustinTArthur)
- misc configuration updates (SubPar)
- add Neblio support (neblioteam) and Bitbay (anoxxxy)
- HOWTO.rst update for running on privileged port (EagleTM)
8 years ago
- issues closed: exclude test dirs from installation (`#223`_).
8 years ago
Version 1.0.17
--------------
- fix #227 introduced in 1.0.16
8 years ago
Version 1.0.16
--------------
- updated server lists for post-fork. If you are on the Segwit chain
you should have NET be "bitcoin-segwit", and if on the Bitcoin Cash chain
continue to use "mainnet".
8 years ago
- binding address fix for multi-homed machines (mmouse)
- listen to IPv4 and IPv6 local interfaces
- add Fujicoin (fujicoin), Crown (Extreemist), RegTest (RCasatta),
Monacoin (cryptocoin-junkey)
- bug fixes and updates (Kefkius, mmouse, thesamesam, cryptocoin-junkey,
jtarthur)
8 years ago
Version 1.0.15
--------------
- split server networks faster if a fork is detected
- minor speedup
- add Vertcoin support (erasmospunk)
- update Faircoin (thokon00)
8 years ago
Version 1.0.14
--------------
- revert the changes to mempool handling of 1.0.13; I think they introduced
a notification bug
8 years ago
Version 1.0.13
--------------
- improve mempool handling and height notifications
- add bitcoin-segwit as a new COIN
8 years ago
Version 1.0.12
--------------
- handle legacy daemons, add support for Blackcoin and Peercoin (erasmospunk)
- implement history compression; can currently only be done from a script
with the server down
- Add dockerfile reference (followtheart)
- doc, runfile fixes (Henry, emilrus)
- add bip32 implementation, currently unused
- daemon compatibility improvements (erasmospunk)
- permit underscores in hostnames, updated Bitcoin server list
8 years ago
Version 1.0.11
--------------
- disable IRC for bitcoin mainnet
- remove dead code, allow custom Daemon & BlockProcessor classes (erasmospunk)
- add SERVER_(SUB)VERSION to banner metavariables (LaoDC)
- masternode methods for Dash (TheLazier)
- allow multiple P2SH address versions, implement for Litecoin (pooler)
- update Bitcoin's TX_COUNT and block height (JWU42)
- update BU nolnet parameters
- fix diagnostic typo (anduck)
- Issues fixed: `#180`_
8 years ago
**Neil Booth** kyuupichan@gmail.com https://github.com/kyuupichan
8 years ago
1BWwXJH3q6PRsizBkSGm2Uw4Sz1urZ5sCj
8 years ago
8 years ago
.. _#180: https://github.com/kyuupichan/electrumx/issues/180
8 years ago
.. _#223: https://github.com/kyuupichan/electrumx/issues/223
8 years ago
.. _#251: https://github.com/kyuupichan/electrumx/issues/251
7 years ago
.. _#251: https://github.com/kyuupichan/electrumx/issues/277
.. _#251: https://github.com/kyuupichan/electrumx/issues/287
8 years ago
.. _docs/HOWTO.rst: https://github.com/kyuupichan/electrumx/blob/master/docs/HOWTO.rst
8 years ago
.. _docs/ENVIRONMENT.rst: https://github.com/kyuupichan/electrumx/blob/master/docs/ENVIRONMENT.rst
7 years ago
.. _docs/PROTOCOL.rst: https://github.com/kyuupichan/electrumx/blob/master/docs/PROTOCOL.rst