tMerge pull request #125 from Sosthene00/disableprivatekeys - electrum-personal-server - Maximally lightweight electrum server for a single user
HTML git clone https://git.parazyd.org/electrum-personal-server
DIR Log
DIR Files
DIR Refs
DIR README
---
DIR commit 19f9a00b3223505dd80d06febf2a1e433087b855
DIR parent 679312275139460976c56b7534aad4e61cb6deba
HTML Author: chris-belcher <belcher@riseup.net>
Date: Mon, 2 Dec 2019 20:17:21 +0000
Merge pull request #125 from Sosthene00/disableprivatekeys
add createwallet disable_private_key=true in README
Diffstat:
M README.md | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
---
DIR diff --git a/README.md b/README.md
t@@ -42,7 +42,7 @@ on [full nodes](https://en.bitcoin.it/wiki/Full_node).
[verify the digital signatures](https://bitcoin.stackexchange.com/questions/50185/how-to-verify-bitcoin-core-release-signing-keys)
of any binaries before running them, or compile from source. The Bitcoin node
must have wallet enabled, and must have the RPC server switched on (`server=1`
- in bitcoin.conf).
+ in bitcoin.conf). On first run, it is recommended to create a wallet dedicated to Electrum Personal Server using the command line argument `bitcoin-cli createwallet EPS true`.
* If you dont already have it, download and install
[Electrum bitcoin wallet](https://electrum.org/), and set up your Electrum
t@@ -67,6 +67,10 @@ on [full nodes](https://en.bitcoin.it/wiki/Full_node).
wallet1 = xpub661MyMwAqRbcF...
wallet2 = xpub7712KLsfsg46G...
+* If you created a wallet dedicated to Electrum Personal Server in Bitcoin Core,
+ you have to modify the line `wallet_filename` in the `[bitcoin-rpc]` section
+ with the name of the wallet, for example `EPS`.
+
* If using the windows packaged binary release, drag the file `config.ini` onto
the file `electrum-personal-server.exe` to run the server, or on the command
line run `electrum-personal-server config.ini`.