0ccdf44181
This commits contains fixes to merklization function arguments and return types. New hash type system from bitcoin crate does not cover all cases for merkle values; and the same function may be applied to different hash types. Thus, I have used generic types to abstract the logic. `Txid` merklization operates with TxMerkleNode type; `BlockHash` merklization does not introduce a new type: the same design decision was made in the original work on new bitcoin crate type system since it is used in a single case, and there is no point in introducing a special designated hash type. Script hashes (used in RPC queries) are left of Sha256dHash type since there is no corresponding type defined in bitcoin crate; this type is specific to Electrum X protocol. Corresponding new type can be implemented in the project later with `hash_newtype!` macro in the same way it was done in bitcoin crate. |
||
|---|---|---|
| .circleci | ||
| .github/workflows | ||
| 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)
txindexis 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.