This change allows the user to specify a custom cookie file, which is then used instead of `~/.bitcoin/.cookie`. This resolves situations when the user wants to have the cookie file in non-standard path. Aside from that, the code now pre-computes the default path, improving the performance by avoiding allocation (and copying). Unfortunately, due to limitations of Rust, the code doesn't print out cookie configuration anymore. This however might be safer, since the cookie isn't printed, and thus doesn't end up in some readable logs by accident. Closes #176 Closes #189 |
||
---|---|---|
.circleci | ||
contrib | ||
doc | ||
examples | ||
scripts | ||
src | ||
.dockerignore | ||
.gitignore | ||
.travis.yml | ||
build.rs | ||
Cargo.lock | ||
Cargo.toml | ||
config_spec.toml | ||
Dockerfile | ||
LICENSE | ||
README.md | ||
RELEASE-NOTES.md | ||
TODO.md |
Electrum Server in Rust
An efficient re-implementation of Electrum Server, inspired by ElectrumX, Electrum Personal Server and bitcoincore-indexd.
The motivation behind this project is to enable a user to run his own Electrum server, with required hardware resources not much beyond those of a full node. The server indexes the entire Bitcoin blockchain, and the resulting index enables fast queries for any given user wallet, allowing the user to keep real-time track of his balances and his transaction history using the Electrum wallet. Since it runs on the user's own machine, there is no need for the wallet to communicate with external Electrum servers, thus preserving the privacy of the user's addresses and balances.
Features
- Supports Electrum protocol v1.4
- Maintains an index over transaction inputs and outputs, allowing fast balance queries
- Fast synchronization of the Bitcoin blockchain (~2 hours for ~187GB @ July 2018) on modest hardware
- Low index storage overhead (~20%), relying on a local full node for transaction retrieval
- Efficient mempool tracker (allowing better fee estimation)
- Low CPU & memory usage (after initial indexing)
txindex
is not required for the Bitcoin node- Uses a single RocksDB database, for better consistency and crash recovery
Usage
See here for installation, build and usage instructions.
Index database
The database schema is described here.