aljaz/bitcoin-tutorials
1
1
Fork 0
mirror of https://github.com/openoms/bitcoin-tutorials.git synced 2025-12-20 21:34:19 +01:00
Code Issues Packages Projects Releases Wiki Activity

formatting

Browse Source
This commit is contained in:
openoms
2019-09-09 08:11:19 +01:00
parent aa41afe640
commit 43f7045d8b
1 changed files with 35 additions and 33 deletions
Download Patch File Download Diff File Expand all files Collapse all files

66
electrs/README.md
View File

@@ -4,19 +4,15 @@
![electrum](/electrs/images/electrum.png) ![electrum](/electrs/images/electrum.png)
## Install Electrs Tested on:
Based on https://github.com/romanz/electrs/blob/master/doc/usage.md
Shared experiences here: https://github.com/rootzoll/raspiblitz/issues/123 and https://github.com/openoms/bitcoin-tutorials/issues/2
Tested on the
* Odroid HC1 and XU4 (~18 hours) * Odroid HC1 and XU4 (~18 hours)
* Raspberry Pi 3 B+ (~two days to build the database from scratch) * Raspberry Pi 3 B+ (~two days to build the database from scratch)
* Raspberry Pi 4
Requires 47 Gb diskpace (March 2019). Requires 47 Gb diskpace (March 2019).
## Install Electrs
The install instructions are adapted to the RaspiBlitz are in this script, take a look: [1_electrs_on_RaspiBlitz.sh](1_electrs_on_RaspiBlitz.sh) The install instructions are adapted to the RaspiBlitz are in this script, take a look: [1_electrs_on_RaspiBlitz.sh](1_electrs_on_RaspiBlitz.sh)
To download and run on the RaspiBlitz (logged in as the user `admin`): To download and run on the RaspiBlitz (logged in as the user `admin`):
@@ -44,6 +40,30 @@ To stop running on boot:
`$ sudo systemctl disable electrs` `$ sudo systemctl disable electrs`
(To re-enable and start use the `enable` and `start`commands) (To re-enable and start use the `enable` and `start`commands)
---
## Check if Electrs is working:
Electrs will only start serving on the port 50001 when it has finished indexing.
To check if the indexing is running run in the RaspiBlitz terminal:
`$ sudo systemctl status electrs`
Example output when running afte indexing has finished:
![electrs status](/electrs/images/electrs_status.png)
Find electrs between running processes with:
`htop`
Cheack if it is serving on the port 50001:
`$ lsof -i`
Look for the output:
```
electrs 2532 admin 17u IPv4 32885 0t0 TCP *:50001 (LISTEN)
```
--- ---
## Install Electrum wallet on your desktop ## Install Electrum wallet on your desktop
@@ -69,30 +89,6 @@ For an unencrypted TCP connection (suitable inside a secure LAN):
To connect through SSL (requires setting up the Nginx server): To connect through SSL (requires setting up the Nginx server):
`electrum --oneserver --server YOUR_DOMAIN:50002:s` `electrum --oneserver --server YOUR_DOMAIN:50002:s`
### Check if Electrs is working:
Electrs will only start serving on the port 50001 when it has finished indexing.
To check if the indexing is running run in the RaspiBlitz terminal:
`$ sudo systemctl status electrs`
Example output when running afte indexing has finished:
![electrs status](/electrs/images/electrs_status.png)
Find electrs between running processes with:
`htop`
Cheack if it is serving on the port 50001:
`$ lsof -i`
Look for the output:
```
electrs 2532 admin 17u IPv4 32885 0t0 TCP *:50001 (LISTEN)
```
--- ---
## Remote connection options to Electrs ## Remote connection options to Electrs
@@ -134,6 +130,12 @@ To download and run on the RaspiBlitz:
The script is a collection of commands. The whole setup has multiple components and dependencies which can change when updated or modified by the maintainers. The script is a collection of commands. The whole setup has multiple components and dependencies which can change when updated or modified by the maintainers.
Based on:
* https://github.com/romanz/electrs/blob/master/doc/usage.md
Shared experiences:
* https://github.com/rootzoll/raspiblitz/issues/123
* https://github.com/openoms/bitcoin-tutorials/issues/2
If you run into problems: If you run into problems:
* try to run the commands manually one-by-one, spot which is causing the problem and copy the output * try to run the commands manually one-by-one, spot which is causing the problem and copy the output
* open an issue here with the details and I will be happy to help to solve it * open an issue here with the details and I will be happy to help to solve it