diff --git a/.gitbook/assets/PostgreSQL-Logo-white.png b/.gitbook/assets/PostgreSQL-Logo-white.png
new file mode 100644
index 00000000..bf9a512d
Binary files /dev/null and b/.gitbook/assets/PostgreSQL-Logo-white.png differ
diff --git a/.gitbook/assets/bonus-logo.png b/.gitbook/assets/bonus-logo.png
new file mode 100644
index 00000000..fcebf68f
Binary files /dev/null and b/.gitbook/assets/bonus-logo.png differ
diff --git a/.gitbook/assets/core_logo.png b/.gitbook/assets/core_logo.png
new file mode 100644
index 00000000..5dfe1152
Binary files /dev/null and b/.gitbook/assets/core_logo.png differ
diff --git a/.gitbook/assets/golang.png b/.gitbook/assets/golang.png
new file mode 100644
index 00000000..0b7e8a1d
Binary files /dev/null and b/.gitbook/assets/golang.png differ
diff --git a/README.md b/README.md
index b3999ee0..c8e49ec7 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@ Build your own "do-everything-yourself" Bitcoin full node on a personal computer
No need to trust anyone else. Don't trust, verify!
-### What is the MiniBolt?
+## What is the MiniBolt?
With this guide, you can set up a Bitcoin and Lightning node on a personal computer from scratch, doing everything yourself. You will learn about Linux, Bitcoin, and Lightning. As a result, you'll have your very own Bitcoin node, built by you and no one else.
@@ -28,11 +28,11 @@ There are many reasons why you should run your own Bitcoin node:
⚡️ **Be part of Lightning.** Run your Lightning node for everyday payments and help build a robust, decentralized Bitcoin Lightning network.
-### MiniBolt overview
+## MiniBolt overview
This guide explains how to set up your own Bitcoin node on a Personal Computer. But it works on most hardware platforms because it only uses standard Debian Linux commands.
-#### Features
+### Features
Your Bitcoin node will offer the following functionality:
@@ -48,52 +48,37 @@ Your Bitcoin node will offer the following functionality:
🌐 **Reachable from anywhere**: connect to all your services through the Tor network and Wireguard VPN
-#### Target audience
+### Target audience
-We strive to give foolproof instructions. But the goal is also to do everything ourselves.
+* [x] We strive to give foolproof instructions. But the goal is also to do everything ourselves.
+* [x] Shortcuts that involve trusting someone else are not allowed. This makes this guide quite technical, but we try to make it as straightforward as possible.
+* [x] You'll gain a basic understanding of the how and why.
+* [x] If you like to learn about Linux, Bitcoin, and Lightning, then this guide is for you.
-Shortcuts that involve trusting someone else are not allowed. This makes this guide quite technical, but we try to make it as straightforward as possible.
-
-You'll gain a basic understanding of the how and why.
-
-If you like to learn about Linux, Bitcoin, and Lightning, then this guide is for you.
-
-#### Structure
+### Structure
We aim to keep the core of this guide well-maintained and up-to-date:
-1. [System](system/): prepare the hardware and set up the operating system
-2. [Bitcoin](bitcoin/): sync your own Bitcoin full node, Electrum server, Blockchain Explorer, and connect a desktop wallet to the Electrum server
-3. [Lightning](lightning/): run your Lightning client with web-based node management, connect a mobile app, and save safely your SCB backup
-
-➕ Bonus guides: the bonus section contains more specific guides that build on top of the main section. More fun, lots of knowledge, but with lesser maintenance guarantees. Everything is optional.
+
The bonus section contains more specific guides that build on top of the main section. More fun, lots of knowledge, but with lesser maintenance guarantees. Everything is optional.
+\
Feel free to join the many other contributors if you see something that can be improved!
-### Rating
+## Rating
All guides are rated with labels to help you assess the difficulty of each guide, and if it is tested against the most recent version of the main guide.
-* Difficulty: indicates how difficult the bonus guide is in terms of installation procedure or usage.
+* **Difficulty:** indicates how difficult the bonus guide is in terms of installation procedure or usage
{% hint style="success" %}
Difficulty: Easy
@@ -107,7 +92,7 @@ Difficulty: Medium
Difficulty: Hard
{% endhint %}
-* Paid service: indicates if the service used in the guide is free or paid.
+* **Paid service:** indicates if the service used in the guide is free or paid
{% hint style="warning" %}
Cost: Paid service
diff --git a/SUMMARY.md b/SUMMARY.md
index 7ae9c1c4..402607e7 100644
--- a/SUMMARY.md
+++ b/SUMMARY.md
@@ -4,7 +4,7 @@
* [MiniBolt](README.md)
-## System
+## 🖥️ System
* [1. System](system/README.md)
* [1.1 Preparations](index-1/preparations.md)
@@ -14,15 +14,15 @@
* [1.5 Security](index-1/security.md)
* [1.6 Privacy](index-1/privacy.md)
-## Bitcoin
+## 🟠 ₿itcoin
-* [2. Bitcoin](bitcoin/README.md)
- * [2.1 Bitcoin client: Bitcoin Core](index-2/bitcoin-client.md)
- * [2.2 Electrum Server: Fulcrum](bitcoin/electrum-server.md)
- * [2.3 Blockchain explorer: BTC RPC Explorer](bitcoin/blockchain-explorer.md)
- * [2.4 Desktop wallet: Sparrow wallet](bitcoin/desktop-wallet.md)
+* [2. ₿itcoin](itcoin/bitcoin/README.md)
+ * [2.1 Bitcoin client: Bitcoin Core](itcoin/bitcoin/bitcoin-client.md)
+ * [2.2 Electrum Server: Fulcrum](itcoin/bitcoin/electrum-server.md)
+ * [2.3 Blockchain explorer: BTC RPC Explorer](itcoin/bitcoin/blockchain-explorer.md)
+ * [2.4 Desktop wallet: Sparrow wallet](itcoin/bitcoin/desktop-wallet.md)
-## Lightning
+## ⚡ Lightning
* [3. Lightning](lightning/README.md)
* [3.1 Lightning client: LND](lightning/lightning-client.md)
@@ -30,21 +30,23 @@
* [3.3 Web app: ThunderHub](lightning/web-app.md)
* [3.4 Mobile app: Zeus](lightning/mobile-app.md)
-## Bonus guides
+## ➕ Bonus guides
-* [System](bonus/system/README.md)
+* [🖥️ System](bonus/system/README.md)
* [Pimp the command line](bonus/system/command-line.md)
* [Aliases](bonus/system/aliases.md)
* [Static IP & custom DNS servers](bonus-guides/system/static-ip-and-custom-dns-servers.md)
* [Node + NPM](bonus/system/nodejs-npm.md)
* [Rustup + Cargo](bonus-guides/system/rustup-+-cargo.md)
+ * [Go!](bonus-guides/system/go.md)
+ * [PostgreSQL](bonus-guides/system/postgresql.md)
* [Login with SSH keys](bonus/system/ssh-keys.md)
* [WireGuard: a simple yet fast VPN](bonus/system/wireguard-vpn.md)
* [Cloudflare tunnel](bonus-guides/system/cloudflare-tunnel.md)
* [Tor obfs4 bridge](index-4/index/tor-bridge.md)
* [NYM mixnet](bonus-guides/system/nym-mixnet.md)
* [Store data in a secondary disk](bonus/system/store-data-secondary-disk.md)
-* [Bitcoin](bonus/bitcoin/README.md)
+* [🟠 ₿itcoin](bonus/bitcoin/README.md)
* [Electrs](bonus/bitcoin/electrs.md)
* [Electrum Wallet Desktop](bonus/bitcoin/electrum-wallet-desktop.md)
* [Sparrow Server](bonus/bitcoin/sparrow-server.md)
diff --git a/bitcoin/README.md b/bitcoin/README.md
deleted file mode 100644
index d075c6df..00000000
--- a/bitcoin/README.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Bitcoin
-nav_order: 30
-has_children: true
-layout:
- title:
- visible: true
- description:
- visible: false
- tableOfContents:
- visible: true
- outline:
- visible: true
- pagination:
- visible: true
----
-
-# 2. Bitcoin
-
-
-
-The base of a sovereign Bitcoin node is a fully validating [Bitcoin client](../index-2/bitcoin-client.md). It will download the whole blockchain and validate every single transaction that ever happened. After this verification, the client can check the validity of all future transactions.
-
-Your [Bitcoin client](../index-2/bitcoin-client.md) also acts as a data source for other applications, like the [Electrum server](electrum-server.md) (to use with your software and hardware wallets), blockchain explorer, or Lightning client.
-
-We first install [Bitcoin Core](../index-2/bitcoin-client.md) and [Fulcrum](electrum-server.md) on the node. We then set up the powerful Sparrow desktop wallet on your computer and connect it to your Fulcrum server for secure and private base layer operations, such as sending and receiving payments from and to your hardware wallet. Finally, we install [BTC RPC Explorer](blockchain-explorer.md) on the node, a lite blockchain explorer with a clean web UI for privately checking your transactions and the mempool.
diff --git a/bonus-guides/bitcoin/btcpay-server.md b/bonus-guides/bitcoin/btcpay-server.md
index 22c56e2c..7f1b09db 100644
--- a/bonus-guides/bitcoin/btcpay-server.md
+++ b/bonus-guides/bitcoin/btcpay-server.md
@@ -30,7 +30,7 @@ More information can be found in its [documentation](https://docs.btcpayserver.o
## Requirements
-* [Bitcoin Core](../../index-2/bitcoin-client.md)
+* [Bitcoin Core](../../itcoin/bitcoin/bitcoin-client.md)
* [LND](../../lightning/lightning-client.md) (optional)
* Others
* PostgreSQL
@@ -191,42 +191,7 @@ exit
### Install PostgreSQL
-* With user `admin`, create the file repository configuration
-
-{% code overflow="wrap" %}
-```bash
-sudo sh -c 'echo "deb http://apt.postgresql.org/pub/repos/apt $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/pgdg.list'
-```
-{% endcode %}
-
-* Import the repository signing key
-
-{% code overflow="wrap" %}
-```bash
-wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo apt-key add -
-```
-{% endcode %}
-
-Expected output:
-
-```
-> Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
-OK
-```
-
-* Update the package lists. You can ignore the `W: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8))` message
-
-```bash
-sudo apt update
-```
-
-* Install the latest version of PostgreSQL
-
-```bash
-sudo apt install postgresql postgresql-contrib
-```
-
-* Check the correct installation
+* With user `admin`, check if you have already installed PostgreSQL
```bash
psql -V
@@ -235,64 +200,22 @@ psql -V
**Example** of expected output:
```
-> psql (PostgreSQL) 15.3 (Ubuntu 15.3-1.pgdg22.04+1)
-```
-
-* Ensure PostgreSQL is running and listening on the default port `5432`
-
-```bash
-sudo ss -tulpn | grep LISTEN | grep postgres
-```
-
-Expected output:
-
-
-
-### Create PostgreSQL databases
-
-* With user `admin`, change to the automatically created user for the PostgreSQL installation called `postgres`
-
-```bash
-sudo su - postgres
-```
-
-* Create a new database user
-
-```bash
-createuser --pwprompt --interactive
+> psql (PostgreSQL) 16.3 (Ubuntu 16.3-1.pgdg22.04+1)
```
-Type in the following:
-
-> > Enter name of role to add: **admin**
->
-> > Enter password for new role: **admin**
->
-> > Enter it again: **admin**
->
-> > Shall the new role be a superuser? (y/n) **n**
->
-> > Shall the new role be allowed to create databases? (y/n) **y**
->
-> > Shall the new role be allowed to create more new roles? (y/n) **n**
-
-* Create 2 new databases
-
-```bash
-createdb -O admin btcpayserver
-```
+{% hint style="info" %}
+If PostgreSQL is not installed (output: Command 'psql' not found), follow this [PostgreSQL](../system/postgresql.md) guide to install it
+{% endhint %}
-```bash
-createdb -O admin nbxplorer
-```
+#### Create PostgreSQL databases
-* Go back to the `admin` user
+* With user `admin`, create 2 new databases with the `postgres` user
+{% code overflow="wrap" %}
```bash
-exit
+sudo -u postgres createdb -O admin btcpayserver && sudo -u postgres createdb -O admin nbxplorer
```
+{% endcode %}
## Installation, Configuration & Run
@@ -306,14 +229,10 @@ exit
sudo su - btcpay
```
-* Create a "src" directory and enter the folder
+* Create a `src` directory and enter the folder
```bash
-mkdir src
-```
-
-```bash
-cd src
+mkdir src && cd src
```
* Set the environment variable version
@@ -506,8 +425,8 @@ sudo nano /etc/systemd/system/nbxplorer.service
[Unit]
Description=NBXplorer
-Wants=bitcoind.service
-After=bitcoind.service
+Requires=bitcoind.service postgresql.service
+After=bitcoind.service postgresql.service
[Service]
WorkingDirectory=/home/btcpay/src/NBXplorer
@@ -539,7 +458,7 @@ WantedBy=multi-user.target
sudo systemctl enable nbxplorer
```
-* Prepare “`nbxplorer`” monitoring by the systemd journal and checking the logging output. You can exit monitoring at any time with Ctrl-C
+* Prepare `nbxplorer` monitoring by the systemd journal and checking the logging output. You can exit monitoring at any time with Ctrl-C
```bash
journalctl -fu nbxplorer
@@ -821,8 +740,8 @@ sudo nano /etc/systemd/system/btcpay.service
[Unit]
Description=BTCPay Server
-Wants=nbxplorer.service
-After=nbxplorer.service
+Requires=nbxplorer.service postgresql.service
+After=nbxplorer.service postgresql.service
[Service]
WorkingDirectory=/home/btcpay/src/btcpayserver
@@ -907,13 +826,13 @@ sudo ss -tulpn | grep LISTEN | grep 23000
Expected output:
```
-> tcp LISTEN 0 512 127.0.0.1:23000 0.0.0.0:* users:(("dotnet",pid=2811744,fd=320))
+> tcp LISTEN 0 512 0.0.0.0:23000 0.0.0.0:* users:(("dotnet",pid=2811744,fd=320))
```
-Now point your browser, `"http://minibolt.local:23000"` (or your node IP address) like `"http://192.168.0.20:23000"`.
+Now point your browser, `"http://minibolt.local:23000"` (or your node IP address) like `"http://192.168.0.20:23000"`
{% hint style="info" %}
-You can now create the first account to access the dashboard using a real (recommended) or a dummy email, and password
+You can now create the first account to access the dashboard using a real (recommended) or a dummy email + password
{% endhint %}
{% hint style="success" %}
@@ -983,7 +902,7 @@ restlisten=0.0.0.0:8080
sudo systemctl restart lnd
```
-* Ensure the REST port is now binding to the `0.0.0.0` host instead of `127.0.0.1`
+* Ensure the REST port is now binding to the `0.0.0.0` host instead of `127.0.0.1`
```bash
sudo ss -tulpn | grep LISTEN | grep lnd | grep 8080
@@ -1000,6 +919,8 @@ Expected output:
sudo systemctl stop btcpay
```
+#### Modify BTCPay Server configuration
+
* Change to the `btcpay` user
```bash
@@ -1025,6 +946,21 @@ BTC.lightning=type=lnd-rest;server=https://127.0.0.1:8080/;macaroonfilepath=/dat
exit
```
+#### Modify the BTCPay Server systemd service
+
+* Modify the next lines of the systemd service file by following [this section](btcpay-server.md#create-btcpay-server-systemd-service)
+
+```
+Requires=nbxplorer.service lnd.service
+After=nbxplorer.service lnd.service
+```
+
+* Reload the systemd daemon
+
+```bash
+sudo systemctl daemon-reload
+```
+
* Start the BTCPay Server again
```bash
@@ -1439,6 +1375,6 @@ sudo systemctl reload tor
| Port | Protocol | Use |
| :---: | :------: | :------------------------: |
-| 5432 | TCP | PostgreSQL default port |
+| 5432 | TCP | PostgreSQL default port |
| 24444 | TCP | NBXplorer default port |
| 23000 | TCP | BTCPay Server default port |
diff --git a/bonus-guides/bitcoin/nostr-relay.md b/bonus-guides/bitcoin/nostr-relay.md
index bd58c36b..3888ea6b 100644
--- a/bonus-guides/bitcoin/nostr-relay.md
+++ b/bonus-guides/bitcoin/nostr-relay.md
@@ -45,20 +45,27 @@ You can obtain more info about nostr on these additional resources:
* [Cloudflare tunnel](../system/cloudflare-tunnel.md)
* Others
+ * [PostgreSQL](../system/postgresql.md)
* [Rustup + Cargo](../system/rustup-+-cargo.md)
## Preparations
### Install dependencies
-* With user `admin`, make sure that all necessary software packages are installed (pending to concrete)
+* With user `admin`, make sure that all necessary software packages are installed
{% code overflow="wrap" %}
```bash
-sudo apt install build-essential cmake protobuf-compiler pkg-config libssl-dev build-essential sqlite3 libsqlite3-dev
+sudo apt install build-essential cmake protobuf-compiler pkg-config libssl-dev
```
{% endcode %}
+{% hint style="info" %}
+If you want to use the default SQLite database backend, go to the [Use the default SQLite database backend extra section](nostr-relay.md#use-the-default-sqlite-database-backend) to install the additional SQLite dependency packages
+{% endhint %}
+
+### Install Rustup + Cargo
+
* Check if you already have Rustup installed
```bash
@@ -84,9 +91,39 @@ cargo -V
```
{% hint style="info" %}
-If you obtain "**command not found**" outputs, you need to follow the [Rustup + Cargo bonus section](../system/rustup-+-cargo.md) to install it and then come back to continue with the guide
+If you obtain "**command not found**" output, you need to follow the [Rustup + Cargo bonus guide](../system/rustup-+-cargo.md) to install it and then come back to continue with the guide
+{% endhint %}
+
+### Install PostgreSQL
+
+{% hint style="info" %}
+Skip this step if you want to use the SQLite database, go directly to the [next section](nostr-relay.md#installation)
{% endhint %}
+* Check if you already have PostgreSQL installed
+
+```bash
+psql -V
+```
+
+**Example** of expected output:
+
+```
+> psql (PostgreSQL) 15.3 (Ubuntu 15.3-1.pgdg22.04+1)
+```
+
+{% hint style="info" %}
+If you obtain "**command not found**" outputs, you need to follow the [PostgreSQL bonus guide](../system/postgresql.md) to install it and then come back to continue with the guide
+{% endhint %}
+
+#### Create PostgreSQL database
+
+* With user `admin`, create a new database with the `postgres` user
+
+```bash
+sudo -u postgres createdb -O admin nostrelay
+```
+
## Installation
* With user `admin`, go to the temporary folder
@@ -180,7 +217,7 @@ nostr-rs-relay -V
```
{% hint style="info" %}
-If you come to update this is the final step, continue with the indications of the [Update section](nostr-relay.md#for-the-future-nostr-relay-upgrade)
+If you come to update this is the final step, continue with the indications of the [Upgrade section](nostr-relay.md#upgrade)
{% endhint %}
### Create the nostr user
@@ -201,12 +238,6 @@ Creating home directory `/home/nostr' ...
Copying files from `/etc/skel' ...
```
-* Create the `rs-relay` and `db` folder
-
-```bash
-mkdir -p /data/nostr/rs-relay/db
-```
-
* Change to the home `nostr` user folder
```bash
@@ -221,30 +252,30 @@ wget https://raw.githubusercontent.com/minibolt-guide/minibolt/main/resources/fa
```
{% endcode %}
-* Exit to the `admin` user
+* Create the `rs-relay` folder
```bash
-exit
+mkdir rs-relay
```
-## Configuration
-
-* With user `admin`, copy-paste the configuration file
+* Exit to the `admin` user
```bash
-sudo cp /tmp/nostr-rs-relay/config.toml /data/nostr/rs-relay/
+exit
```
-* Assign as the owner to the `nostr` user
+## Configuration
+
+* Copy-paste the configuration file template to the before-created folder
```bash
-sudo chown -R nostr:nostr /data/nostr
+sudo cp /tmp/nostr-rs-relay/config.toml /home/nostr/rs-relay/
```
-* Return to the home folder
+* Assign the owner of the file to the `nostr` user
```bash
-cd
+sudo chown nostr:nostr /home/nostr/rs-relay/config.toml
```
* Delete the `nostr-rs-relay` folder to be ready for the next update
@@ -256,24 +287,38 @@ sudo rm -r /tmp/nostr-rs-relay
* Edit the config file, uncomment, and replace the needed information on the next parameters. Save and exit
```bash
-sudo nano /data/nostr/rs-relay/config.toml
+sudo nano /home/nostr/rs-relay/config.toml
```
+{% hint style="info" %}
+Pay attention to not include the next lines:
+
+> engine = "postgres"[^1]
+
+> connection = "postgresql://admin:admin@localhost:5432/nostrelay"[^2]
+
+Include the uncomment, and replace the next line:
+
+> data\_directory = "/data/nostr/rs-relay/db"
+
+If you want to use the default SQLite database backend. More details and additional steps on the exclusive [extra section](nostr-relay.md#use-the-default-sqlite-database-backend)
+{% endhint %}
+
> > **Customize this with your own info (\*):**
> >
-> > **(\*)** click on parameter to get an example/explanation)
-> >
-> > > relay\_url = "[``](#user-content-fn-1)[^1]"
-> >
-> > > name = "``"
-> >
-> > > description = "[``](#user-content-fn-2)[^2]"
-> >
-> > > pubkey = "``"
-> >
-> > > contact = "[``](#user-content-fn-3)[^3]"
-> >
-> > > relay\_icon = "``"
+> > **(\*)** Click on parameter to get an example/explanation
+>
+> > relay\_url = "\[^3]"
+>
+> > name = "\"
+>
+> > description = "\[^4]"
+>
+> > pubkey = "\"
+>
+> > contact = "\[^5]"
+>
+> > relay\_icon = "\[^6]"
{% hint style="info" %}
If you don't have pubkey generated yet, you can follow the [Create your nostr key pair](nostr-relay.md#create-your-nostr-key-pair) section and then continue with this.
@@ -283,17 +328,19 @@ You can use [this tool](https://nostrdebug.com/converter/) to convert your "npub
> > **Required same as next (\*):**
> >
-> > **(\*)** click on the parameter to get action to do (\ or \)
-> >
-> > [favicon = "favicon.ico"](#user-content-fn-4)[^4]
+> > **(\*)** click on the parameter to get action to do **(\** or **\**)
+>
+> > favicon = "favicon.ico"[^7]
>
-> > data\_directory = "/data/nostr/rs-relay/db"
+> > engine = "postgres"[^8]
>
-> > [address = "127.0.0.1"](#user-content-fn-5)[^5]
+> > connection = "postgresql://admin:admin@localhost:5432/nostrelay"[^9]
>
-> > port = 8880
+> > address = "127.0.0.1"[^10]
>
-> > [remote\_ip\_header = "cf-connecting-ip"](#user-content-fn-6)[^6]
+> > port = 8880[^11]
+>
+> > remote\_ip\_header = "cf-connecting-ip"[^12]
{% hint style="info" %}
If you want, use the same [`favicon.ico`](https://raw.githubusercontent.com/minibolt-guide/minibolt/nostr-relay-PR/resources/favicon.ico) file downloaded before (the relay's icon of MiniBolt) and the value `relay_icon` parameter (URL), or replace it with your own, downloading it instead
@@ -316,12 +363,12 @@ The system needs to run the nostr relay daemon automatically in the background,
[Unit]
Description=Nostr relay
-Wants=network-online.target
-After=network-online.target
+Requires=network-online.target postgresql.service
+After=network-online.target postgresql.service
[Service]
WorkingDirectory=/home/nostr
-ExecStart=/usr/local/bin/nostr-rs-relay -c /data/nostr/rs-relay/config.toml
+ExecStart=/usr/local/bin/nostr-rs-relay -c /home/nostr/rs-relay/config.toml
Environment=RUST_LOG=info,nostr_rs_relay=info
User=nostr
@@ -412,7 +459,7 @@ credentials-file: /home/admin/.cloudflared/<UUID>.json
ingress:
# Nostr relay
- - hostname: relay.<domain.com>
+ - hostname: relay.<domain.com>
service: ws://localhost:8880
- service: http_status:404
@@ -436,39 +483,101 @@ journalctl -fu cloudflared
### Check relay connection
-3 different methods:
+\-> 3 different methods ⬇️
-1. Go to the [nostr.watch](https://nostr.watch) website to check and test the relay connection
-
-Access to the URL, replacing `` with your Nostr relay URL: `https://nostr.watch/relay/relay.domain.com,` example: [https://nostr.watch/relay/relay.damus.io](https://nostr.watch/relay/relay.damus.io)
+{% tabs %}
+{% tab title="Method 1" %}
+* Go to the [nostr.watch](https://nostr.watch) website to check and test the relay connection
+* Access to the URL, replacing `` with your Nostr relay URL: `https://nostr.watch/relay/relay.domain.com,` example: [https://nostr.watch/relay/relay.damus.io](https://nostr.watch/relay/relay.damus.io)
Expected output:
+{% endtab %}
-2. Go to the [websocketking.com](https://websocketking.com/) website, type in the WebSocket URL box your Nostr relay URL e.g. `wss://relay.domain.com`, and click on the **\[Connect]** button
+{% tab title="Method 2" %}
+Go to the [websocketking.com](https://websocketking.com/) website, type in the WebSocket URL box your Nostr relay URL e.g. `wss://relay.domain.com`, and click on the **\[Connect]** button
**Example** of expected output:
+{% endtab %}
-3. Go to the [https://nostrdebug.com/relay](https://nostrdebug.com/relay) website, type in the box your Nostr relay URL e.g. `wss://relay.domain.com`, and click on the **\[Connect]** button. You should see the status "✅ Connected" on the history
+{% tab title="Method 3" %}
+Go to the [https://nostrdebug.com/relay](https://nostrdebug.com/relay) website, type in the box your Nostr relay URL e.g. `wss://relay.domain.com`, and click on the **\[Connect]** button. You should see the status "✅ **Connected**" on the history
+{% endtab %}
+{% endtabs %}
## Extras (optional)
+### Use the default SQLite database backend
+
+* With user `admin`, install the next additional dependencies
+
+{% code overflow="wrap" %}
+```bash
+sudo apt install sqlite3 libsqlite3-dev
+```
+{% endcode %}
+
+* Create the `rs-relay` and `db` folder
+
+```bash
+mkdir -p /data/nostr/rs-relay/db
+```
+
+* Assign as the owner to the `nostr` user
+
+```bash
+sudo chown -R nostr:nostr /data/nostr
+```
+
+* Edit the config file
+
+```bash
+sudo nano /data/nostr/rs-relay/config.toml
+```
+
+* Uncomment, and replace the needed information on the next parameters. Save and exit
+
+```
+data_directory = "/data/nostr/rs-relay/db"
+```
+
+{% hint style="info" %}
+Ignore the next lines related to the PostgreSQL (not uncomment or edit):
+
+```
+engine = "postgres"
+
+connection = "postgresql://admin:admin@localhost:5432/nostrelay"
+```
+{% endhint %}
+
+* Delete `postgres.service` of the systemd service lines
+
+```
+Requires=network-online.target
+After=network-online.target
+```
+
+{% hint style="info" %}
+[Continue](nostr-relay.md#run) with the guide, the rest of the steps are the same as PostgreSQL use
+{% endhint %}
+
### Create your nostr key pair
* Download and install the Alby Browser extension:
* For Firefox-based browser:
* [Mozilla Firefox](https://addons.mozilla.org/en-US/firefox/addon/alby/)
* [Librewolf](https://addons.mozilla.org/en-US/firefox/addon/alby/)
- * [Tor browser](https://addons.mozilla.org/en-US/firefox/addon/alby/) <-- Follow [this guide](https://guides.getalby.com/alby-guides/alby-browser-extension/faqs/can-i-use-alby-with-the-tor-browser) to enable the Alby extension using the Tor browser
+ * [Tor browser](https://addons.mozilla.org/en-US/firefox/addon/alby/) <- Follow [this guide](https://guides.getalby.com/alby-guides/alby-browser-extension/faqs/can-i-use-alby-with-the-tor-browser) to enable the Alby extension using the Tor browser
* For Chromium based-browser:
* [Chrome](https://chrome.google.com/webstore/detail/alby-bitcoin-lightning-wa/iokeahhehimjnekafflcihljlcjccdbe)
* [Brave](https://chrome.google.com/webstore/detail/alby-bitcoin-lightning-wa/iokeahhehimjnekafflcihljlcjccdbe)
-* After installation, the browser will redirect automatically you to choose the password to unlock Alby. Click on the \[**Next]** button
+* After installation, the browser automatically redirects you to choose the password to unlock Alby. Click on the \[**Next]** button
@@ -504,7 +613,7 @@ Select a strong password for the Alby extension (this password is for encrypting
-* If you selected to **create a new one**, remember backup the seed shown on the screen, check the verification box, and click on the **\[Save Master Key]** box
+* If you selected to **create a new one**, remember to backup the seed shown on the screen, check the verification box, and click on the **\[Save Master Key]** box
@@ -529,7 +638,7 @@ Click on the **\[Nostr Settings]** box to **obtain your private key and backup o
* If you selected the Nostr private key, fill in the "**Nostr Private key**" box with your private key, it will derivate you the "**Nostr Public Key"**, check if correct
{% hint style="info" %}
-If you see this banner when you enter on "**Nostr Settings**" section, this means that you should backup carefully the private key, because the existing seeds that you have are not compatible with Alby only the private key
+If you see this banner when you enter the "**Nostr Settings**" section, this means that you should backup carefully the private key, because the existing seeds that you have are not compatible with Alby only the private key
{% endhint %}
@@ -576,7 +685,7 @@ If you want all your past events to be accessible through your new relay, you ca
{% hint style="info" %}
Please **wait patiently** until all processes are finished. This might take some time, depending on the number of events you've published on Nostr with that pubkey meaning the interactions you've had on Nostr.
-Optionally, you can also save a copy of all your events locally as you'll have the download option.
+Optionally, you can save a copy of all your events locally as you'll have the download option.
{% endhint %}
### Nostr clients
@@ -595,13 +704,13 @@ A nostr UI built with React aiming for speed and efficiency.
{% endtab %}
{% tab title="Zap stream" %}
-Nostr live streaming
+Nostr live streaming.
[Web](https://zap.stream/) | [GitHub](https://github.com/v0l/zap.stream)
{% endtab %}
{% tab title="Rana" %}
-Nostr public key mining tool
+Nostr public key mining tool.
[GitHub](https://github.com/grunch/rana)
{% endtab %}
@@ -615,7 +724,7 @@ A free URL shortener service enabled by the NOSTR protocol, that is fast and fus
{% tabs %}
{% tab title="Nostree" %}
-A Nostr-based application to create, manage and discover link lists, show notes and other stuff.
+A Nostr-based application to create, manage, and discover link lists, show notes, and other stuff.
[Web](https://nostree.me/) | [GitHub](https://github.com/gzuuus/linktr-nostr)
{% endtab %}
@@ -635,7 +744,7 @@ Pinstr is a decentralized, free, and open-source social network built on top of
{% endtab %}
{% tab title="Nostr nests" %}
-Nostr Nests is an audio space for chatting, brainstorming, debating, jamming, micro-conferences and more.
+Nostr Nests is an audio space for chatting, brainstorming, debating, jamming, micro-conferences, and more.
[Web](https://nostrnests.com) | [Git](https://gitlab.com/jam-systems/jam)
{% endtab %}
@@ -649,7 +758,7 @@ Pleb.to does NOSTR things... documents, links, graphs, maps, and more... Pleb.to
{% endtab %}
{% tab title="Nostrudel" %}
-"My half-baked personal nostr client"
+"My half-baked personal nostr client".
[Web](https://nostrudel.ninja) | [GitHub](https://github.com/hzrd149/nostrudel)
{% endtab %}
@@ -661,7 +770,7 @@ Habla allows you to read, write, curate and monetize long form content over Nost
{% endtab %}
{% tab title="Amethyst" %}
-Nostr client for Android
+Nostr client for Android.
Amethyst brings the best social network to your Android phone.
@@ -671,7 +780,7 @@ Amethyst brings the best social network to your Android phone.
{% tabs %}
{% tab title="Password Manager (Vault)" %}
-A free, open source, and decentralized password manager, powered by NOSTR
+A free, open source, and decentralized password manager, powered by NOSTR.
[Chrome-based extension](https://chrome.google.com/webstore/detail/vault/namadahddjnkmjgdnncdlhioopmjiflm) | [GitHub](nostr-relay.md#first-https-github.com-jinglescode-nostr-password-manager)
{% endtab %}
@@ -689,7 +798,7 @@ Tool for migrating your entire past Twitter activity to Nostr.
{% endtab %}
{% tab title="Nosy" %}
-Find the top relays of those who follow you or you follow
+Find the top relays of those who follow you or you follow.
[Web](https://nosy.tigerville.no/)
{% endtab %}
@@ -707,7 +816,7 @@ sudo systemctl stop nostr-relay
* Replace the `config.toml` file with the new one of the new version **(if needed)**
{% hint style="warning" %}
-**This step is only necessary if you see changes on the config file template from your current version until the current release (not common)**, you can display this on this [history link](https://github.com/scsibug/nostr-rs-relay/commits/master/config.toml). If no changes, jump directly to the next **"Start `nostr-rs-relay` service again" >**`sudo systemctl start nostr-relay`
+**This step is only necessary if you see changes on the config file template from your current version until the current release (not common)**, you can display this on this [history link](https://github.com/scsibug/nostr-rs-relay/commits/master/config.toml). If there are no changes, jump directly to the next **"Start `nostr-rs-relay` service again" >**`sudo systemctl start nostr-relay`
{% endhint %}
* Backup the `config.toml` file to keep a copy of your old configuration
@@ -826,16 +935,28 @@ sudo rm /usr/local/bin/nostr-rs-relay
| :--: | :------: | :----------: |
| 8880 | TCP | Default port |
-[^1]: **Example:** `"wss://relay.bitcoin.org/"`
+[^1]: \ & \
+
+[^2]: \
+
+[^3]: **Example:** `"wss://relay.bitcoin.org/"`
+
+[^4]: **Example:** `"The official nostr relay of the Bitcoin community"`
+
+[^5]: **Example:** `"hello@bitcoin.org"`
+
+[^6]: Example: [https://twofaktor.github.io/logo\_circle%2BB.png](https://twofaktor.github.io/logo\_circle%2BB.png)
+
+[^7]: \
-[^2]: **Example:** `"The official nostr relay of the Bitcoin community"`
+[^8]: \ & \
-[^3]: **Example:** `"hello@bitcoin.org"`
+[^9]: \
-[^4]: \
+[^10]: \
-[^5]: \ to `127.0.0.1`
+[^11]: \
-[^6]: \
+[^12]: \
-[^7]: Here your personal domain
+[^13]: Here your personal domain
diff --git a/bonus-guides/system/cloudflare-tunnel.md b/bonus-guides/system/cloudflare-tunnel.md
index 3a908ceb..77555605 100644
--- a/bonus-guides/system/cloudflare-tunnel.md
+++ b/bonus-guides/system/cloudflare-tunnel.md
@@ -97,7 +97,7 @@ cd /tmp
* Set a temporary version environment variable to the installation
```bash
-VERSION=2024.5.0
+VERSION=2024.6.0
```
* Download Cloudflare Tunnel Client (Cloudflared)
@@ -286,7 +286,7 @@ ingress:
> 1. Electrum server are not supported using Cloudflared
> 2. For security reasons, you shouldn't expose publically the administration access services using Cloudflared e.g SSH or Thunderhub, for these cases you should use [Wireguard VPN](../../bonus/system/wireguard-vpn.md)
-> 3. If you want to expose only a service, you can delete or comment the associated lines of other services, always maintaining the "`- service: http_status:404"` line at the end of the rules. Example, expose only BTCPay Server, the comment the associated lines for BTC RPC Explorer:
+> 3. If you want to expose only a service, you can delete or comment the associated lines of other services, always maintaining the "`- service: http_status:404"` line at the end of the rules. Example, expose only BTCPay Server, the comment the associated lines for BTC RPC Explorer:
>
> ```
> # BTC RPC Explorer
@@ -351,13 +351,13 @@ sudo nano /etc/systemd/system/cloudflared.service
[Unit]
Description=Cloudflared
-Wants=network-online.target
+Requires=network-online.target
After=network-online.target
[Service]
ExecStart=/usr/bin/cloudflared --no-autoupdate --config /home/admin/.cloudflared/config.yml tunnel run
-
-# Process management
+
+# Process management
####################
Type=notify
TimeoutStartSec=0
diff --git a/bonus-guides/system/go.md b/bonus-guides/system/go.md
new file mode 100644
index 00000000..194d14cb
--- /dev/null
+++ b/bonus-guides/system/go.md
@@ -0,0 +1,208 @@
+---
+layout:
+ title:
+ visible: true
+ description:
+ visible: false
+ tableOfContents:
+ visible: true
+ outline:
+ visible: true
+ pagination:
+ visible: true
+---
+
+# Go!
+
+[Go](https://github.com/golang/go)[!](https://github.com/golang/go) is an agent-based programming language in the tradition of logic-based programming languages like Prolog designed at Google.
+
+{% hint style="success" %}
+Difficulty: Easy
+{% endhint %}
+
+
+
+## Installation
+
+* With user `admin`, go to the temporary folder
+
+```bash
+cd /tmp
+```
+
+* Set a temporary version environment variable to the installation
+
+```bash
+VERSION=1.22.3
+```
+
+* Set a temporary SHA256 environment variable to the installation
+
+```bash
+SHA256=8920ea521bad8f6b7bc377b4824982e011c19af27df88a815e3586ea895f1b36
+```
+
+* Get the latest binary of the [official repository](https://go.dev/dl/)
+
+```bash
+wget https://go.dev/dl/go$VERSION.linux-amd64.tar.gz
+```
+
+* Check the checksum of the file
+
+```bash
+echo "$SHA256 go$VERSION.linux-amd64.tar.gz" | sha256sum --check
+```
+
+**Example** of expected output:
+
+
> go1.21.10.linux-amd64.tar.gz: OK
+
+
+* Extract and install Go in the `/usr/local` directory
+
+```bash
+sudo tar -C /usr/local -xvzf go$VERSION.linux-amd64.tar.gz
+```
+
+* Edit `/etc/profile` file
+
+```bash
+sudo nano /etc/profile
+```
+
+* Add the next line at the end of the file. Save and exit
+
+```bash
+export PATH=$PATH:/usr/local/go/bin
+```
+
+* Apply the changes immediately to the current session
+
+```bash
+source /etc/profile
+```
+
+* Verify that you've installed Go by typing the following command
+
+```bash
+go version
+```
+
+**Example** of expected output:
+
+```
+> go version go1.21.10 linux/amd64
+```
+
+* **(Optional)** Delete the file of the temporary folder to be immediately ready for the next update
+
+```bash
+rm go$VERSION.linux-amd64.tar.gz
+```
+
+## Upgrade
+
+* With user `admin`, remove any previous Go installation
+
+```bash
+sudo rm -rf /usr/local/go
+```
+
+* Go to the temporary folder
+
+```bash
+cd /tmp
+```
+
+* Set a temporary version environment variable with the new value, to the installation
+
+```bash
+VERSION=1.22.3
+```
+
+* Set the new temporary SHA256 environment variable to the installation
+
+```bash
+SHA256=8920ea521bad8f6b7bc377b4824982e011c19af27df88a815e3586ea895f1b36
+```
+
+* Get the latest binary of the [official repository](https://go.dev/dl/)
+
+```bash
+wget https://go.dev/dl/go$VERSION.linux-amd64.tar.gz
+```
+
+* Check the checksum of the file
+
+```bash
+echo "$SHA256 go$VERSION.linux-amd64.tar.gz" | sha256sum --check
+```
+
+**Example** of expected output:
+
+```
+> go1.22.3.linux-amd64.tar.gz: OK
+```
+
+* Extract and install Go in the `/usr/local` directory
+
+```bash
+sudo tar -C /usr/local -xvzf go$VERSION.linux-amd64.tar.gz
+```
+
+* Verify that you've updated Go by typing the following command
+
+```
+go version
+```
+
+**Example** of expected output:
+
+```
+go version go1.22.3 linux/amd64
+```
+
+* **(Optional)** Delete the file of the temporary folder to be immediately ready for the next update
+
+```bash
+rm go$VERSION.linux-amd64.tar.gz
+```
+
+## Uninstall
+
+* Delete go folder
+
+```bash
+sudo rm -rf /usr/local/go
+```
+
+* Edit `/etc/profile` file and delete the complete `export PATH=$PATH:/usr/local/go/bin` line at the end of the file. Save and exit
+
+```bash
+sudo nano /etc/profile
+```
+
+* Apply the changes immediately to the current session
+
+```bash
+source /etc/profile
+```
+
+* Ensure you are uninstalled Go definitely
+
+```bash
+go version
+```
+
+Expected output:
+
+```
+> -bash: /usr/local/go/bin/go: No such file or directory
+```
+
+Next new session you will obtain this command when you try `go version` command:
+
+```
+Command 'go' not found..
+```
diff --git a/bonus-guides/system/nym-mixnet.md b/bonus-guides/system/nym-mixnet.md
index c005f4e1..e4ce0430 100644
--- a/bonus-guides/system/nym-mixnet.md
+++ b/bonus-guides/system/nym-mixnet.md
@@ -248,7 +248,7 @@ The system needs to run the network requester daemon automatically in the backgr
[Unit]
Description=Nym Network Requester
-Wants=network-online.target
+Requires=network-online.target
After=network-online.target
StartLimitInterval=350
@@ -439,7 +439,7 @@ sudo nano /etc/systemd/system/nym-socks5-client.service
[Unit]
Description=Nym Socks5 client
-Wants=network-online.target
+Requires=network-online.target
After=network-online.target
StartLimitInterval=350
@@ -715,7 +715,7 @@ If you have installed the NYM socks5 client installed in a machine inside of you
#### Sparrow desktop
-Follow the [Desktop wallet: Sparrow Wallet](../../bitcoin/desktop-wallet.md) until the [(Optional) Set up a Tor proxy for external services](../../bitcoin/desktop-wallet.md#optional-set-up-a-tor-proxy-for-external-services), which could be used for these 2 cases of uses:
+Follow the [Desktop wallet: Sparrow Wallet](../../itcoin/bitcoin/desktop-wallet.md) until the [(Optional) Set up a Tor proxy for external services](../../itcoin/bitcoin/desktop-wallet.md#optional-set-up-a-tor-proxy-for-external-services), which could be used for these 2 cases of uses:
1. If you don't have your node and you want to **proxy** all connections (**The Electrum Servers** of the wallet & **third-party server connections**) using the NYM mixnet
diff --git a/bonus-guides/system/postgresql.md b/bonus-guides/system/postgresql.md
new file mode 100644
index 00000000..74412d52
--- /dev/null
+++ b/bonus-guides/system/postgresql.md
@@ -0,0 +1,559 @@
+---
+layout:
+ title:
+ visible: true
+ description:
+ visible: false
+ tableOfContents:
+ visible: true
+ outline:
+ visible: true
+ pagination:
+ visible: true
+---
+
+# PostgreSQL
+
+PostgreSQL is a powerful, open source object-relational database system that uses and extends the SQL language combined with many features that safely store and scale the most complicated data workloads.
+
+{% hint style="warning" %}
+Difficulty: Medium
+{% endhint %}
+
+
+
+## Installation
+
+### Install PostgreSQL using the apt package manager
+
+* With user `admin`, create the file repository configuration
+
+{% code overflow="wrap" %}
+```bash
+sudo sh -c 'echo "deb http://apt.postgresql.org/pub/repos/apt $(lsb_release -cs)-pgdg main" > /etc/apt/sources.list.d/pgdg.list'
+```
+{% endcode %}
+
+* Import the repository signing key
+
+{% code overflow="wrap" %}
+```bash
+wget --quiet -O - https://www.postgresql.org/media/keys/ACCC4CF8.asc | sudo apt-key add -
+```
+{% endcode %}
+
+Expected output:
+
+```
+> Warning: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8)).
+OK
+```
+
+{% hint style="info" %}
+You can ignore the `W: apt-key is deprecated. Manage keyring files in trusted.gpg.d instead (see apt-key(8))` message
+{% endhint %}
+
+* Update the package lists and install the latest version of PostgreSQL. Press "**y**" and `enter` or directly `enter` when the prompt asks you
+
+```bash
+sudo apt update && sudo apt install postgresql postgresql-contrib
+```
+
+* Check the correct installation of the PostgreSQL
+
+```bash
+psql -V
+```
+
+**Example** of expected output:
+
+```
+> psql (PostgreSQL) 15.3 (Ubuntu 15.3-1.pgdg22.04+1)
+```
+
+* Ensure PostgreSQL is running and listening on the default port `5432`
+
+```bash
+sudo ss -tulpn | grep LISTEN | grep postgres
+```
+
+Expected output:
+
+
+
+* You can monitor general logs by the systemd journal. You can exit monitoring at any time with `Ctrl-C`
+
+```bash
+journalctl -fu postgresql
+```
+
+**Example** of expected output:
+
+```
+May 31 13:51:11 minibolt systemd[1]: Finished PostgreSQL RDBMS.
+```
+
+* And the sub-instance and specific cluster logs. You can exit monitoring at any time with `Ctrl-C`
+
+```bash
+journalctl -fu postgresql@16-main
+```
+
+**Example** of expected output:
+
+```
+May 31 13:51:18 minibolt systemd[1]: Starting PostgreSQL Cluster 16-main...
+May 31 13:51:21 minibolt systemd[1]: Started PostgreSQL Cluster 16-main.
+```
+
+### Create data folder
+
+* Create the dedicated PostgreSQL data folder
+
+```bash
+sudo mkdir /data/postgresdb
+```
+
+* Assign as the owner to the `postgres` user
+
+
sudo chown postgres:postgres /data/postgresdb
+
+
+* Assign permissions of the data folder only to the `postgres` user
+
+
sudo chmod -R 700 /data/postgresdb
+
+
+* With user `postgres`, create a new cluster on the dedicated folder
+
+```bash
+sudo -u postgres /usr/lib/postgresql/16/bin/initdb -D /data/postgresdb
+```
+
+
+
+Example of expected output ⬇️
+
+```
+The files belonging to this database system will be owned by user "postgres".
+This user must also own the server process.
+
+The database cluster will be initialized with locale "en_GB.UTF-8".
+The default database encoding has accordingly been set to "UTF8".
+The default text search configuration will be set to "english".
+
+Data page checksums are disabled.
+
+fixing permissions on existing directory /data/postgresdb ... ok
+creating subdirectories ... ok
+selecting dynamic shared memory implementation ... posix
+selecting default max_connections ... 100
+selecting default shared_buffers ... 128MB
+selecting default time zone ... Europe/Madrid
+creating configuration files ... ok
+running bootstrap script ... ok
+performing post-bootstrap initialization ... ok
+syncing data to disk ... ok
+
+initdb: warning: enabling "trust" authentication for local connections
+initdb: hint: You can change this by editing pg_hba.conf or using the option -A, or --auth-local and --auth-host, the next time you run initdb.
+
+Success. You can now start the database server using:
+
+ /usr/lib/postgresql/16/bin/pg_ctl -D /data/postgresdb -l logfile start
+```
+
+
+
+* Edit the PostgreSQL data directory on configuration, to redirect the store to the new location
+
+```bash
+sudo nano /etc/postgresql/16/main/postgresql.conf --linenumbers
+```
+
+* Replace the `line 42` to this. Save and exit
+
+
data_directory = '/data/postgresdb'
+
+
+* Restart PostgreSQL to apply changes and monitor the correct status of the main instance and sub-instance monitoring sessions before
+
+
sudo systemctl restart postgresql
+
+
+* You can monitor the PostgreSQL main instance by the systemd journal and check the log output. You can exit the monitoring at any time with `Ctrl-C`
+
+```bash
+journalctl -fu postgresql
+```
+
+Expected output:
+
+```
+Nov 08 11:51:10 minibolt systemd[1]: Stopped PostgreSQL RDBMS.
+Nov 08 11:51:10 minibolt systemd[1]: Stopping PostgreSQL RDBMS...
+Nov 08 11:51:13 minibolt systemd[1]: Starting PostgreSQL RDBMS...
+Nov 08 11:51:13 minibolt systemd[1]: Finished PostgreSQL RDBMS.
+```
+
+* You can monitor the PostgreSQL sub-instance by the systemd journal and check log output. You can exit monitoring at any time with `Ctrl-C`
+
+```bash
+journalctl -fu postgresql@16-main
+```
+
+**Example** of the expected output:
+
+```
+Nov 08 11:51:10 minibolt systemd[1]: Stopping PostgreSQL Cluster 16-main...
+Nov 08 11:51:11 minibolt systemd[1]: postgresql@16-main.service: Succeeded.
+Nov 08 11:51:11 minibolt systemd[1]: Stopped PostgreSQL Cluster 16-main.
+Nov 08 11:51:11 minibolt systemd[1]: postgresql@16-main.service: Consumed 1h 10min 8.677s CPU time.
+Nov 08 11:51:11 minibolt systemd[1]: Starting PostgreSQL Cluster 16-main...
+Nov 08 11:51:13 minibolt systemd[1]: Started PostgreSQL Cluster 16-main.
+```
+
+{% hint style="info" %}
+**(Optional)** -> If you want, you can **disable the autoboot** option for PostgreSQL **(not recommended)** using:
+
+```bash
+sudo systemctl disable postgresql
+```
+
+Expected output:
+
+```
+Synchronizing state of postgresql.service with SysV service script with /lib/systemd/systemd-sysv-install.
+Executing: /lib/systemd/systemd-sysv-install disable postgresql
+Removed /etc/systemd/system/multi-user.target.wants/postgresql.service.
+```
+{% endhint %}
+
+### Create a PostgreSQL user account
+
+* With user `admin`, change to the automatically created user for the PostgreSQL installation called `postgres`
+
+```bash
+sudo su - postgres
+```
+
+* Create a new database user
+
+```bash
+createuser -d admin
+```
+
+* Assign the password "`admin`" to the new user
+
+```bash
+psql -c "ALTER ROLE admin WITH PASSWORD 'admin';"
+```
+
+* Come back to the `admin` user
+
+```bash
+exit
+```
+
+## Extras (optional)
+
+### Some useful PostgreSQL commands
+
+* With user `admin`, enter the PostgreSQL CLI with the user `postgres`. The prompt should change to `postgres=#`
+
+```bash
+sudo -u postgres psql
+```
+
+**Example** of expected output:
+
+```
+psql (16.3 (Ubuntu 16.3-1.pgdg22.04+1))
+Type "help" for help.
+
+postgres=#
+```
+
+{% hint style="info" %}
+Type `\q` command and enter to exit PostgreSQL CLI and exit to come back to the `admin` user
+{% endhint %}
+
+#### List the global existing users and roles associated
+
+* Type the next command and enter
+
+```bash
+\du
+```
+
+**Example** of expected output:
+
+```
+ List of roles
+ Role name | Attributes
+-----------+------------------------------------------------------------
+ admin | Create DB
+ postgres | Superuser, Create role, Create DB, Replication, Bypass RLS
+```
+
+#### List the global existing databases
+
+* Type the next command and enter
+
+```bash
+\l
+```
+
+**Example** of expected output:
+
+```
+ Name | Owner | Encoding | Locale Provider | Collate | Ctype | ICU Locale | ICU Rules | Access privileges
+--------------+----------+----------+-----------------+-------------+-------------+------------+-----------+-----------------------
+ btcpayserver | admin | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | |
+ lndb | admin | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | |
+ nbxplorer | admin | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | |
+ nostrelay | admin | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | |
+ postgres | postgres | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | |
+ template0 | postgres | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | | =c/postgres +
+ | | | | | | | | postgres=CTc/postgres
+ template1 | postgres | UTF8 | libc | en_US.UTF-8 | en_US.UTF-8 | | | =c/postgres +
+ | | | | | | | | postgres=CTc/postgres
+(8 rows)
+```
+
+#### List tables inside of a specific database
+
+* Connect to a specific database, type the next command, and enter. The prompt should change to the name of the database. Example: `lndb=#`
+
+```bash
+\c
+```
+
+{% hint style="info" %}
+Replace ` to the specific name of the database
+{% endhint %}
+
+**Example:**
+
+```bash
+\c lndb
+```
+
+**Expected output:**
+
+```
+> You are now connected to database "lndb" as user "postgres".
+```
+
+* List tables
+
+```bash
+\dt
+```
+
+**Example of expected output:**
+
+```
+ List of relations
+ Schema | Name | Type | Owner
+--------+------------------+-------+-------
+ public | channeldb_kv | table | admin
+ public | decayedlogdb_kv | table | admin
+ public | macaroondb_kv | table | admin
+ public | towerclientdb_kv | table | admin
+ public | towerserverdb_kv | table | admin
+ public | walletdb_kv | table | admin
+(6 rows)
+```
+
+#### **View the size of a specific database**
+
+* Type the next command and enter
+
+```bash
+SELECT pg_size_pretty(pg_database_size(''));
+```
+
+{% hint style="info" %}
+Replace ` to the specific name of the database
+{% endhint %}
+
+**Example:**
+
+```bash
+SELECT pg_size_pretty(pg_database_size('lndb'));
+```
+
+**Example** of expected output:
+
+```
+ pg_size_pretty
+----------------
+ 546 MB
+(1 row)
+```
+
+#### **View the size of a specific table inside a database**
+
+* Enter a specific database with
+
+```bash
+\c
+```
+
+{% hint style="info" %}
+Replace `` to the specific name of the database
+{% endhint %}
+
+**Example:**
+
+```bash
+\c lndb
+```
+
+* View the size of a specific table
+
+```bash
+SELECT pg_size_pretty(pg_total_relation_size(''));
+```
+
+{% hint style="info" %}
+Replace `` to the specific name of the database
+{% endhint %}
+
+**Example:**
+
+```bash
+SELECT pg_size_pretty(pg_total_relation_size('channeldb_kv'));
+```
+
+**Example** of expected output:
+
+```
+ pg_size_pretty
+----------------
+ 457 MB
+(1 row)
+```
+
+#### **Detele** a specific database
+
+* Type the next command and enter
+
+```bash
+DROP DATABASE ;
+```
+
+{% hint style="info" %}
+Replace `` to the specific name of the table
+{% endhint %}
+
+Example:
+
+```bash
+DROP DATABASE lndb;
+```
+
+#### Expected output:
+
+```
+> DROP DATABASE
+```
+
+#### Delete a table inside of a specific database
+
+{% hint style="warning" %}
+Stop the service related to this database before the action, i.e: `sudo systemctl stop lnd`
+{% endhint %}
+
+* Enter a specific database with
+
+```bash
+\c
+```
+
+{% hint style="info" %}
+Replace `` to the specific name of the database
+{% endhint %}
+
+**Example:**
+
+```bash
+\c lndb
+```
+
+* Delete a specific table
+
+{% hint style="warning" %}
+Stop the service related to this table and database before the action, i.e: `sudo systemctl stop lnd`
+{% endhint %}
+
+```bash
+DROP TABLE ;
+```
+
+{% hint style="info" %}
+Replace `` to the specific name of the table
+{% endhint %}
+
+Example:
+
+```bash
+DROP TABLE towerclientdb_kv;
+```
+
+## Upgrade
+
+The latest release can be found on the [official PostgreSQL web page](https://www.postgresql.org/ftp/source/).
+
+* To upgrade, type this command
+
+```bash
+sudo apt update && sudo apt full-upgrade
+```
+
+## Uninstall
+
+### Uninstall PostgreSQL package and configuration
+
+* With user `admin`, stop and disable postgres service
+
+```bash
+sudo systemctl stop postgresql && sudo systemctl disable postgresql
+```
+
+* Uninstall PostgreSQL using the apt package manager
+
+```bash
+sudo apt remove postgresql postgresql-* --purge
+```
+
+* Uninstall possible unnecessary dependencies
+
+```bash
+sudo apt autoremove
+```
+
+* Delete configuration files and data
+
+{% code overflow="wrap" %}
+```bash
+sudo rm -rf /etc/postgresql/ && sudo rm -rf /etc/postgresql-common/ && sudo rm -rf /var/lib/postgresql/ && sudo rm -rf /var/log/postgresql/ && sudo rm -rf /usr/lib/postgresql/ && sudo rm -rf /usr/share/postgresql/
+```
+{% endcode %}
+
+### Uninstall postgres user
+
+* Delete the postgres user. Don't worry about `userdel: bitcoind mail spool (/var/mail/bitcoind) not found` output, the uninstall has been successful
+
+```bash
+sudo userdel -rf postgres
+```
+
+* Delete the complete `PostgreSQL` directory
+
+```bash
+sudo rm -rf /data/postgresdb
+```
diff --git a/bonus-guides/system/rustup-+-cargo.md b/bonus-guides/system/rustup-+-cargo.md
index f72636ea..44d37131 100644
--- a/bonus-guides/system/rustup-+-cargo.md
+++ b/bonus-guides/system/rustup-+-cargo.md
@@ -32,6 +32,10 @@ Rustup is an installer for the systems programming language [Rust](https://www.r
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
```
+{% hint style="warning" %}
+When the prompt asks you to choose an option, type **"`1`"** and press **enter** or press **enter** directly to "**Proceed with installation**"
+{% endhint %}
+
Expected output 🔽
@@ -86,13 +90,9 @@ Current installation options:
-{% hint style="warning" %}
-When the prompt asks you to choose an option, type **"`1`"** and press **enter** or press **enter** directly to "Proceed with installation"
-{% endhint %}
-
-Example of expected output 🔽
+Example of installation expected output 🔽
```
info: profile set to 'default'
@@ -167,7 +167,7 @@ cargo -V
## Upgrade
-* With user `admin` type the appropriate command to get that
+* With user `admin` type the appropriate command to get that
```bash
rustup update
@@ -183,7 +183,7 @@ info: checking for self-update
## Uninstall
-* With user `admin` type the appropriate command to get that
+* With user `admin` type the appropriate command to get that
```bash
rustup self uninstall
@@ -212,4 +212,4 @@ info: removing rustup binaries
info: rustup is uninstalled
```
-[^1]: Type "`1`" and press enter
+[^1]: Type "`1`" and press enter
diff --git a/bonus/bitcoin/README.md b/bonus/bitcoin/README.md
index 62314761..d2850244 100644
--- a/bonus/bitcoin/README.md
+++ b/bonus/bitcoin/README.md
@@ -17,9 +17,9 @@ layout:
visible: true
---
-# Bitcoin
+# 🟠 ₿itcoin
-## Bonus Section: Bitcoin guides
+## Bonus Section: ₿itcoin guides
### Electrum servers
@@ -55,4 +55,4 @@ layout:
### Payment processors
-* [**BTCPay Server**](../../bonus-guides/bitcoin/btcpay-server.md) - a free and open-source Bitcoin payment processor which allows you to accept Bitcoin without fees or intermediaries
+* [**BTCPay Server**](../../bonus-guides/bitcoin/btcpay-server.md) - a free and open-source Bitcoin payment processor that allows you to accept Bitcoin without fees or intermediaries
diff --git a/bonus/bitcoin/bisq.md b/bonus/bitcoin/bisq.md
index fa2b425f..69ee43c1 100644
--- a/bonus/bitcoin/bisq.md
+++ b/bonus/bitcoin/bisq.md
@@ -30,7 +30,7 @@ Difficulty: Easy
## Requirements
-* [Bitcoin Core](../../index-2/bitcoin-client.md)
+* [Bitcoin Core](../../itcoin/bitcoin/bitcoin-client.md)
## Introduction
diff --git a/bonus/bitcoin/electrs.md b/bonus/bitcoin/electrs.md
index f0dc566e..87fc1ab4 100644
--- a/bonus/bitcoin/electrs.md
+++ b/bonus/bitcoin/electrs.md
@@ -30,15 +30,15 @@ Difficulty: Medium
## Requirements
-* [Bitcoin Core](../../index-2/bitcoin-client.md)
+* [Bitcoin Core](../../itcoin/bitcoin/bitcoin-client.md)
* Others
* [Rustup + Cargo](../../bonus-guides/system/rustup-+-cargo.md)
## Preparations
-Make sure that you have [reduced the database cache of Bitcoin Core](../../index-2/bitcoin-client.md#activate-mempool--reduce-dbcache-after-a-full-sync) after a full sync.
+Make sure that you have [reduced the database cache of Bitcoin Core](../../itcoin/bitcoin/bitcoin-client.md#activate-mempool--reduce-dbcache-after-a-full-sync) after a full sync.
-Electrs is a replacement for a [Fulcrum](../../bitcoin/electrum-server.md), these two services cannot be run at the same time (due to the same standard ports used), remember to stop or [uninstall](../../bitcoin/electrum-server.md#uninstall) Fulcrum by doing `"sudo systemctl stop fulcrum"`.
+Electrs is a replacement for a [Fulcrum](../../itcoin/bitcoin/electrum-server.md), these two services cannot be run at the same time (due to the same standard ports used), remember to stop or [uninstall](../../itcoin/bitcoin/electrum-server.md#uninstall) Fulcrum by doing `"sudo systemctl stop fulcrum"`.
### Install dependencies
@@ -481,7 +481,7 @@ sudo nano /etc/systemd/system/electrs.service
[Unit]
Description=Electrs
-Wants=bitcoind.service
+Requires=bitcoind.service
After=bitcoind.service
[Service]
@@ -597,7 +597,7 @@ Expected output:
```
{% hint style="info" %}
-Electrs must first fully index the blockchain and compact its database before you can connect to it with your wallets. This can take a few hours. Only proceed with the [next section](../../bitcoin/desktop-wallet.md) once Electrs is ready
+Electrs must first fully index the blockchain and compact its database before you can connect to it with your wallets. This can take a few hours. Only proceed with the [next section](../../itcoin/bitcoin/desktop-wallet.md) once Electrs is ready
{% endhint %}
## Extras (optional)
@@ -606,7 +606,7 @@ Electrs must first fully index the blockchain and compact its database before yo
To use your Electrum server when you're on the go, you can easily create a Tor hidden service. This way, you can connect the BitBoxApp or Electrum wallet remotely, or even share the connection details with friends and family. Note that the remote device needs to have Tor installed as well.
-* Ensure that you are logged in with the user `admin`, edit the `torrc` file
+* Ensure that you are logged in with the user `admin`, edit the `torrc` file
```sh
sudo nano /etc/tor/torrc
@@ -746,7 +746,7 @@ sudo rm -rf /data/electrs/
### Uninstall Tor hidden service
-* Ensure that you are logged in with the user `admin` , edit the `torrc` config file
+* Ensure that you are logged in with the user `admin` , edit the `torrc` config file
```bash
sudo nano /etc/tor/torrc
diff --git a/bonus/bitcoin/electrum-wallet-desktop.md b/bonus/bitcoin/electrum-wallet-desktop.md
index fa588e38..e0fc8fc5 100644
--- a/bonus/bitcoin/electrum-wallet-desktop.md
+++ b/bonus/bitcoin/electrum-wallet-desktop.md
@@ -29,8 +29,8 @@ Difficulty: Easy
## Requirements
-* [Bitcoin Core](../../index-2/bitcoin-client.md)
-* Electrum server:[ Fulcrum](../../bitcoin/electrum-server.md) or [Electrs](electrs.md)
+* [Bitcoin Core](../../itcoin/bitcoin/bitcoin-client.md)
+* Electrum server:[ Fulcrum](../../itcoin/bitcoin/electrum-server.md) or [Electrs](electrs.md)
## Installation
diff --git a/bonus/bitcoin/minibolt-on-testnet.md b/bonus/bitcoin/minibolt-on-testnet.md
index eb3365f9..673b35c2 100644
--- a/bonus/bitcoin/minibolt-on-testnet.md
+++ b/bonus/bitcoin/minibolt-on-testnet.md
@@ -38,9 +38,9 @@ The great news is that most of the MiniBolt guide can be used as-is. The small a
## Bitcoin
-### [Bitcoin client: Bitcoin Core](../../index-2/bitcoin-client.md)
+### [Bitcoin client: Bitcoin Core](../../itcoin/bitcoin/bitcoin-client.md)
-* Follow the complete MiniBolt guide from the beginning [(Bitcoin client included)](../../index-2/bitcoin-client.md), when you arrive at the ["Configuration section"](../../index-2/bitcoin-client.md#configuration), stay tuned to replace and add the next lines on the `"bitcoin.conf"` file
+* Follow the complete MiniBolt guide from the beginning [(Bitcoin client included)](../../itcoin/bitcoin/bitcoin-client.md), when you arrive at the ["Configuration section"](../../itcoin/bitcoin/bitcoin-client.md#configuration), stay tuned to replace and add the next lines on the `"bitcoin.conf"` file
```sh
nano /home/bitcoin/.bitcoin/bitcoin.conf
@@ -53,7 +53,7 @@ startupnotify=chmod g+r /home/bitcoin/.bitcoin/testnet3/.cookie
testnet=1
```
-* When you finish the [Running Bitcoin](../../index-2/bitcoin-client.md#running-bitcoind) section, with the user `admin` provide read and execute permissions to the Bitcoin group for the testnet folder
+* When you finish the [Running Bitcoin](../../itcoin/bitcoin/bitcoin-client.md#running-bitcoind) section, with the user `admin` provide read and execute permissions to the Bitcoin group for the testnet folder
```bash
sudo chmod g+rx /data/bitcoin/testnet3
@@ -64,14 +64,14 @@ sudo chmod g+rx /data/bitcoin/testnet3
{% endhint %}
{% hint style="success" %}
-The rest of the Bitcoin client guide is the same as the mainnet mode. Note that the seeds nodes of the ["Reject non-privacy networks"](../../index-2/bitcoin-client.md#reject-non-private-networks) section will be different, being correct those on this [list](https://github.com/bitcoin/bitcoin/blob/master/contrib/seeds/nodes\_test.txt). Only exist Tor and I2P seed nodes, not clearnet nodes.
+The rest of the Bitcoin client guide is the same as the mainnet mode. Note that the seeds nodes of the ["Reject non-privacy networks"](../../itcoin/bitcoin/bitcoin-client.md#reject-non-private-networks) section will be different, being correct those on this [list](https://github.com/bitcoin/bitcoin/blob/master/contrib/seeds/nodes\_test.txt). Only exist Tor and I2P seed nodes, not clearnet nodes.
{% endhint %}
-### [Electrum server: Fulcrum](../../bitcoin/electrum-server.md)
+### [Electrum server: Fulcrum](../../itcoin/bitcoin/electrum-server.md)
-Follow the complete Electrum server guide from the beginning, when you arrive at the ["Configure Firewall"](../../bitcoin/electrum-server.md#configure-firewall) section:
+Follow the complete Electrum server guide from the beginning, when you arrive at the ["Configure Firewall"](../../itcoin/bitcoin/electrum-server.md#configure-firewall) section:
-[Configure Firewall](../../bitcoin/electrum-server.md#configure-firewall)
+[Configure Firewall](../../itcoin/bitcoin/electrum-server.md#configure-firewall)
* Replace the next lines to 60001/60002 ports, to match with the Testnet mode
@@ -83,7 +83,7 @@ sudo ufw allow 60001/tcp comment 'allow Fulcrum Testnet TCP from anywhere'
sudo ufw allow 60002/tcp comment 'allow Fulcrum Testnet SSL from anywhere'
```
-* When you arrive at the ["Data directory"](../../bitcoin/electrum-server.md#data-directory) section on the _"Download the custom Fulcrum banner based on MiniBolt..." step_. Download the Fulcrum testnet banner instead of the mainnet banner
+* When you arrive at the ["Data directory"](../../itcoin/bitcoin/electrum-server.md#data-directory) section on the _"Download the custom Fulcrum banner based on MiniBolt..." step_. Download the Fulcrum testnet banner instead of the mainnet banner
{% code overflow="wrap" %}
```bash
@@ -91,9 +91,9 @@ wget https://raw.githubusercontent.com/minibolt-guide/minibolt/main/resources/fu
```
{% endcode %}
-[Configuration](../../bitcoin/electrum-server.md#configuration)
+[Configuration](../../itcoin/bitcoin/electrum-server.md#configuration)
-* In the next [Configuration](../../bitcoin/electrum-server.md#configuration) step, stay tuned to replace the next lines on the `fulcrum.conf` file, to match with the testnet mode
+* In the next [Configuration](../../itcoin/bitcoin/electrum-server.md#configuration) step, stay tuned to replace the next lines on the `fulcrum.conf` file, to match with the testnet mode
```sh
nano /data/fulcrum/fulcrum.conf
@@ -112,9 +112,9 @@ tcp = 0.0.0.0:60001
banner = /data/fulcrum/fulcrum-banner-testnet.txt
```
-[Remote access over Tor](../../bitcoin/electrum-server.md#remote-access-over-tor)
+[Remote access over Tor](../../itcoin/bitcoin/electrum-server.md#remote-access-over-tor)
-* When you arrive at the[ remote access over the Tor section](../../bitcoin/electrum-server.md#remote-access-over-tor), edit torrc file
+* When you arrive at the[ remote access over the Tor section](../../itcoin/bitcoin/electrum-server.md#remote-access-over-tor), edit torrc file
```sh
sudo nano /etc/tor/torrc
@@ -156,9 +156,9 @@ You should now be able to connect to your Fulcrum server remotely via Tor using
The rest of the **Fulcrum** guide is exactly the same as the mainnet mode
{% endhint %}
-### [Blockchain Explorer: BTC RPC Explorer](../../bitcoin/blockchain-explorer.md)
+### [Blockchain Explorer: BTC RPC Explorer](../../itcoin/bitcoin/blockchain-explorer.md)
-* Follow the complete guide from the beginning, when you arrive at the [Configuration section](../../bitcoin/blockchain-explorer.md#configuration), set the next lines with the next values instead of the existing ones for mainnet. Edit **`.env`** file
+* Follow the complete guide from the beginning, when you arrive at the [Configuration section](../../itcoin/bitcoin/blockchain-explorer.md#configuration), set the next lines with the next values instead of the existing ones for mainnet. Edit **`.env`** file
```sh
nano /home/btcrpcexplorer/btc-rpc-explorer/.env
@@ -197,7 +197,8 @@ If you use [Ordirespector](ordisrespector.md) on testnet, add the next lines at
```
# Use external fee estimator
-feeurl=https://nodes.lightning.computer/fees/v1/btctestnet-fee-estimates.json
+[fee]
+fee.url=https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json
```
* When you arrive at the [Create systemd service](../../lightning/lightning-client.md#create-systemd-service) section, edit the `lnd.service` file and replace `ExecStop` parameter to this
diff --git a/bonus/bitcoin/ordisrespector.md b/bonus/bitcoin/ordisrespector.md
index e8706f67..eff6b07e 100644
--- a/bonus/bitcoin/ordisrespector.md
+++ b/bonus/bitcoin/ordisrespector.md
@@ -300,7 +300,7 @@ The following output is just an **example** of one of the versions:
```
{% hint style="info" %}
-Now you can continue with the installation progress of the Bitcoin Client following the [Create the bitcoin user](../../index-2/bitcoin-client.md#create-the-bitcoin-user) section or if you already had it installed, only continue with the next steps
+Now you can continue with the installation progress of the Bitcoin Client following the [Create the bitcoin user](../../itcoin/bitcoin/bitcoin-client.md#create-the-bitcoin-user) section or if you already had it installed, only continue with the next steps
{% endhint %}
* Return to the `tmp` folder
@@ -427,12 +427,12 @@ sudo systemctl stop lnd
sudo nano /data/lnd/lnd.conf
```
-* Add the next lines inside of `[Application Options]` section
+* Add the next lines at the end of the file
-```
-# Use external fee estimator
-feeurl=https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json
-```
+
# Use external fee estimator
+[fee]
+fee.url=https://nodes.lightning.computer/fees/v1/btc-fee-estimates.json
+
* Start LND again
@@ -452,8 +452,8 @@ Remember to restart the Bitcoin Core to apply the new version with `$ sudo syste
## Uninstall
-To uninstall Bitcoin Core with the Ordisrespector patch applied, follow the entire Bitcoin Core [uninstall section](../../index-2/bitcoin-client.md#uninstall)
+To uninstall Bitcoin Core with the Ordisrespector patch applied, follow the entire Bitcoin Core [uninstall section](../../itcoin/bitcoin/bitcoin-client.md#uninstall)
## Port reference
-Same as the [Bitcoin Core section](../../index-2/bitcoin-client.md#port-reference)
+Same as the [Bitcoin Core section](../../itcoin/bitcoin/bitcoin-client.md#port-reference)
diff --git a/bonus/bitcoin/sparrow-server.md b/bonus/bitcoin/sparrow-server.md
index 5b987e0f..ae6bdc6b 100644
--- a/bonus/bitcoin/sparrow-server.md
+++ b/bonus/bitcoin/sparrow-server.md
@@ -30,8 +30,8 @@ Difficulty: Medium
## Requirements
-* [Bitcoin Core](../../index-2/bitcoin-client.md)
-* Electrum server: [Fulcrum](../../bitcoin/electrum-server.md) or [Electrs](electrs.md)
+* [Bitcoin Core](../../itcoin/bitcoin/bitcoin-client.md)
+* Electrum server: [Fulcrum](../../itcoin/bitcoin/electrum-server.md) or [Electrs](electrs.md)
## Installation
diff --git a/bonus/system/README.md b/bonus/system/README.md
index 78ae72d6..cc8ffff5 100644
--- a/bonus/system/README.md
+++ b/bonus/system/README.md
@@ -17,7 +17,7 @@ layout:
visible: true
---
-# System
+# 🖥️ System
## Bonus Section: System guides
@@ -30,10 +30,15 @@ layout:
* [**Aliases**](aliases.md) - set up CLI command shortcuts to simplify your node management experienc**e**
* [**Static IP & custom DNS servers**](../../bonus-guides/system/static-ip-and-custom-dns-servers.md) - set a static IP local address and customize the DNS servers
-### Install / Update / Uninstall common languages
+### Common programming languages
-* [**Node + NPM**](nodejs-npm.md) - Install/Update/Uninstall Node + NPM
-* [**Rustup + Cargo**](../../bonus-guides/system/rustup-+-cargo.md) - Install/ Update/Uninstall Rustup + Cargo
+* [**Node + NPM**](nodejs-npm.md) - Install / Update / Uninstall Node + NPM
+* [**Rustup + Cargo**](../../bonus-guides/system/rustup-+-cargo.md) - Install / Update / Uninstall Rustup + Cargo
+* [**Go!**](https://github.com/golang/go) - Install / Update / Uninstall Go
+
+### Databases
+
+* [**PostgreSQL**](../../bonus-guides/system/postgresql.md) - Install / Update / Uninstall PostgreSQL database
### Security
diff --git a/index-1/privacy.md b/index-1/privacy.md
index 037bcc1e..0bbb74c7 100644
--- a/index-1/privacy.md
+++ b/index-1/privacy.md
@@ -204,23 +204,6 @@ Not all network traffic is routed over the Tor network, by default some services
```
{% endhint %}
-### Uninstall Tor
-
-* With user `admin`, enter the next command and "`y`" when the prompt asks you if you want to continue
-
-```bash
-sudo apt autoremove tor deb.torproject.org-keyring && sudo apt purge tor
-```
-
-Expected output:
-
-```
-[...]
-The following packages will be REMOVED:
- deb.torproject.org-keyring tor tor-geoipdb torsocks
-[...]
-```
-
## I2P Project
@@ -250,7 +233,7 @@ Importing signing key
Adding APT repository
```
-* Update the apt repository and Install i2pd as any other software package. Press "y" and "enter"
+* Update the apt repository and install i2pd as any other software package. Press "y" and "enter"
```sh
sudo apt update && sudo apt install i2pd
@@ -330,31 +313,6 @@ sudo systemctl disable i2pd
```
{% endhint %}
-### Uninstall I2P
-
-* With user `admin`, enter the next command, and "`y`" when the prompt asks you if you want to continue
-
-```bash
-sudo apt autoremove i2pd && sudo apt purge i2pd
-```
-
-Expected output:
-
-```
-[...]
-The following packages will be REMOVED:
- i2pd libminiupnpc17
-[...]
-```
-
-## Upgrade Tor and I2P
-
-The latest release can be found on the [official Tor web page](https://gitweb.torproject.org/tor.git/plain/ChangeLog) or the [unofficial GitHub page](https://github.com/torproject/tor/tags) and for I2P on the [PPA page](https://launchpad.net/\~purplei2p/+archive/ubuntu/i2pd). To upgrade simply type this command:
-
-```sh
-sudo apt update && sudo apt upgrade
-```
-
## Extras (optional)
### **SSH remote access through Tor**
@@ -405,7 +363,7 @@ You also need to have Tor installed on your regular computer where you start the
* **Windows**:
-To enable Tor in the background follow the same instructions for the [preparations](../bitcoin/desktop-wallet.md#preparations-on-your-computer) section of the Desktop Wallet guide.
+To enable Tor in the background follow the same instructions for the [preparations](../itcoin/bitcoin/desktop-wallet.md#preparations-on-your-computer) section of the Desktop Wallet guide.
* PuTTy:
* Follow the same instructions of the [remote access section](remote-access.md#access-with-secure-shell) for Putty, but this time type the `.onion` address on the hostname.
@@ -530,7 +488,51 @@ Edit the screen to match with this, replacing SOCKS Host, with your node local I
Click on the OK button, and try to navigate to some clearnet domain like [https://minibolt.info](https://minibolt.info), if it resolves, you are OK.\
Or simply go to this [website](https://check.torproject.org/), and you should see "_Congratulations. This browser is configured to use Tor."_
-Also, you can use the Tor proxy connection to reach clearnet or third-party address connection on Sparrow wallet. Check out the [Desktop wallet: Sparrow wallet](../bitcoin/desktop-wallet.md) guide to get instructions.
+Also, you can use the Tor proxy connection to reach clearnet or third-party address connection on Sparrow wallet. Check out the [Desktop wallet: Sparrow wallet](../itcoin/bitcoin/desktop-wallet.md) guide to get instructions.
+
+## Upgrade Tor and I2P
+
+The latest release can be found on the [official Tor web page](https://gitweb.torproject.org/tor.git/plain/ChangeLog) or the [unofficial GitHub page](https://github.com/torproject/tor/tags) and for I2P on the [PPA page](https://launchpad.net/\~purplei2p/+archive/ubuntu/i2pd). To upgrade type this command:
+
+```sh
+sudo apt update && sudo apt upgrade
+```
+
+## Uninstall
+
+### Uninstall Tor
+
+* With user `admin`, enter the next command and "`y`" when the prompt asks you if you want to continue
+
+```bash
+sudo apt autoremove tor deb.torproject.org-keyring && sudo apt purge tor
+```
+
+Expected output:
+
+```
+[...]
+The following packages will be REMOVED:
+ deb.torproject.org-keyring tor tor-geoipdb torsocks
+[...]
+```
+
+### Uninstall I2P
+
+* With user `admin`, enter the next command, and "`y`" when the prompt asks you if you want to continue
+
+```bash
+sudo apt autoremove i2pd && sudo apt purge i2pd
+```
+
+Expected output:
+
+```
+[...]
+The following packages will be REMOVED:
+ i2pd libminiupnpc17
+[...]
+```
## **Troubleshooting**
@@ -556,7 +558,7 @@ sudo rm /var/lib/tor/state
sudo systemctl start tor
```
-If your new set of entry guards still produces the stream error, try connecting to the internet using a cable if you're using Wireless. If that doesn't help, I'd suggest downloading [Wireshark](https://www.wireshark.org/) and seeing if you're getting drowned in TCP transmission errors for non-Tor traffic. If yes, your ISP is who you need to talk to.
+If your new set of entry guards still produces the stream error, try connecting to the internet using a cable if you're using Wireless. If that doesn't help, I'd suggest downloading [Wireshark](https://www.wireshark.org/) and seeing if you're getting drowned in TCP transmission errors for non-Tor traffic. If yes, your ISP is who you need to talk to.
If not, try using [obfs bridges](../index-4/index/tor-bridge.md#add-bridge-to-tor-daemon) and see if that helps. Your ISP, the company's network, your country, etc, could be censoring completely your Tor access, use of obfs bridges could help to avoid this censorship.
@@ -578,7 +580,7 @@ If this happens, usually this fix only with restarting the i2pd service
sudo systemctl restart i2pd
```
-* Check again Bitcoin Core logs to ensure that the errors don't appear anymore
+* Check again the Bitcoin Core logs to ensure that the errors don't appear anymore
## Port reference
diff --git a/index-1/security.md b/index-1/security.md
index 4cc0363a..11165d28 100644
--- a/index-1/security.md
+++ b/index-1/security.md
@@ -20,7 +20,7 @@ The MiniBolt needs to be secured against online attacks using various methods.
-## Uncomplicated Firewall (enable & configure)
+## Uncomplicated Firewall
A firewall controls what kind of outside traffic your machine accepts and which applications can send data out. By default, many network ports are open and listening for incoming connections. Closing unnecessary ports can mitigate many potential system vulnerabilities.
@@ -38,8 +38,17 @@ ping6 -c2 2001:858:2:2:aabb:0:563b:1526 && ping6 -c2 2620:13:4000:6000::1000:118
2 options:
-1. If you obtain the `"OK."` output, you have IPv6 availability, additionally, you can obtain your IPv6 with: `curl -s ipv6.icanhazip.com` you are OK, continue the guide without modifications
-2. If you obtain `ping6: connect: Network is unreachable`, you don't have IPv6 availability, don't worry, the IPv6 adoption is new, you will use your internet connection using the common IPv4, additionally, you can obtain your IPv4 with: `curl -s ipv4.icanhazip.com`
+{% tabs %}
+{% tab title="First" %}
+If you obtain the `"OK."` output, you have IPv6 availability, additionally, you can obtain your IPv6 with: `curl -s ipv6.icanhazip.com` you are OK, continue the guide without modifications
+{% endtab %}
+
+{% tab title="Second" %}
+If you obtain `ping6: connect: Network is unreachable`, you don't have IPv6 availability, don't worry, the IPv6 adoption is new, you will use your internet connection using the common IPv4, additionally, you can obtain your IPv4 with: `curl -s ipv4.icanhazip.com`
+{% endtab %}
+{% endtabs %}
+
+### Configuration
If you don't have IPv6 availability, you can disable IPv6 on UFW to avoid the creation of rules related to it:
@@ -71,7 +80,9 @@ Attention! Don't forget the next step!
sudo ufw allow 22/tcp comment 'allow SSH from anywhere'
```
-* Enable ufw, when the prompt shows you `"Command may disrupt existing ssh connections. Proceed with operation (y|n)?"`, press `"y"` and enter
+### Enable
+
+* Enable the UFW, when the prompt shows you `"Command may disrupt existing ssh connections. Proceed with operation (y|n)?"`, press `"y"` and enter
```sh
sudo ufw enable
@@ -108,7 +119,9 @@ sudo ufw status verbose
{% hint style="info" %}
-If you find yourself locked out by mistake, you can connect a keyboard and screen to your PC to log in locally and fix these settings (especially for the SSH port 22). More: [UFW Essentials](https://www.digitalocean.com/community/tutorials/ufw-essentials-common-firewall-rules-and-commands)
+If you find it locked out by mistake, you can connect a keyboard and screen to your PC to log in locally and fix these settings (especially for the SSH port 22)
+
+More: [UFW Essentials](https://www.digitalocean.com/community/tutorials/ufw-essentials-common-firewall-rules-and-commands)
{% endhint %}
### Monitoring SSH authentication logs (optional)
@@ -125,7 +138,7 @@ sudo tail -f /var/log/auth.log
sudo tail --lines 500 /var/log/auth.log | grep sshd
```
-* With this command, you can show a listing of the last satisfactory logged-in users in your MiniBolt since 7 days ago. Change `-7days` option to whatever you want
+* With this command, you can show a listing of the last satisfactory logged-in users in your MiniBolt since 7 days ago. Change `-7days` option to do whatever you want
```sh
last -s -7days -t today
@@ -187,7 +200,7 @@ sudo mv /etc/nginx/nginx.conf /etc/nginx/nginx.conf.bak
sudo nano /etc/nginx/nginx.conf
```
-* Paste the following configuration into the `nginx.conf` file. Save and exit
+* Paste the following configuration into the `nginx.conf` file. Save and exit
```nginx
user www-data;
@@ -260,7 +273,7 @@ sudo systemctl reload nginx
```
{% hint style="info" %}
- You can monitor the Nginx logs by entering this command. Exit with Ctrl + C
+You can monitor the Nginx logs by entering this command. Exit with Ctrl + C
{% endhint %}
```bash
@@ -269,12 +282,14 @@ journalctl -fu nginx
Expected output:
-
> Nov 16 16:56:56 minibolt systemd[1]: Starting A high performance web server and a reverse proxy server...
-> Nov 16 16:56:56 minibolt systemd[1]: Started A high performance web server and a reverse proxy server.
+
> Jun 04 18:21:09 minibolt systemd[1]: Starting A high performance web server and a reverse proxy server...
+> Jun 04 18:21:09 minibolt systemd[1]: Started A high performance web server and a reverse proxy server.
+> Jun 04 18:25:18 minibolt systemd[1]: Reloading A high performance web server and a reverse proxy server...
+> Jun 04 18:25:18 minibol systemd[1]: Reloaded A high performance web server and a reverse proxy server.
{% hint style="info" %}
-You can monitor Nginx error logs by entering this command. Exit with Ctrl + C
+You can monitor Nginx error logs by entering this command. Exit with `Ctrl + C`
{% endhint %}
```bash
diff --git a/index-4/index/tor-bridge.md b/index-4/index/tor-bridge.md
index 90e826e0..d8cf434b 100644
--- a/index-4/index/tor-bridge.md
+++ b/index-4/index/tor-bridge.md
@@ -148,8 +148,6 @@ By default, Tor will advertise your bridge to users through various [mechanisms]
Currently valid, recognized options are: `none` | `any` | `https` | `email` | `moat`
-
-
If you don't specify this line, by default the method will be `any` , this means that you give the choice of whatever method it sees fit
{% endhint %}
@@ -168,9 +166,9 @@ sudo ufw allow /tcp comment 'allow obsf4 port Tor bridge from anywhere'
{% hint style="warning" %}
Note that both Tor's OR port and its obfs4 port must be reachable from outside.
-If your bridge is behind a NAT, make sure to open both ports. See [portforward.com](https://portforward.com/) for directions on how to port forward with your NAT/router device.
+If your bridge is behind a NAT, make sure to open both ports. See [portforward.com](https://portforward.com/) for directions on how to port forward with your NAT/router device.
-You can use our reachability [test](https://bridges.torproject.org/scan/) to see if your obfs4 port **``** is reachable from the Internet.
+You can use our reachability [test](https://bridges.torproject.org/scan/) to see if your obfs4 port **``** is reachable from the Internet.
Enter the website your public **"IP ADDRESS"** obtained with **`curl icanhazip.com`** or navigate directly with your regular browser to [icanhazip.com](https://icanhazip.com/) on your personal computer inside of the same local network, and put your **``** port.
{% endhint %}
@@ -196,7 +194,7 @@ NoNewPrivileges=no
sudo nano /lib/systemd/system/tor@.service
```
-* Change `"NoNewPrivileges=yes"` to `"NoNewPrivileges=no"`. Save and exit
+* Change `"NoNewPrivileges=yes"` to `"NoNewPrivileges=no"`. Save and exit
```
# Hardening
@@ -243,9 +241,24 @@ You can check the status of your bridge relay at https://bridges.torproject.org/
```
{% hint style="info" %}
-About **3 hours** after you start your relay, it should appear on [Relay Search](https://metrics.torproject.org/rs.html) on the Metrics portal. You can search for your relay using your nickname or IP address and can monitor your obfs4 bridge's usage on Relay Search. Just enter your bridge's **"HASHED FINGERPRINT"** in the form and click on "Search"
+About **3 hours** after you start your relay, it should appear on [Relay Search](https://metrics.torproject.org/rs.html) on the Metrics portal. You can search for your relay using your nickname or IP address and monitor your obfs4 bridge's usage on Relay Search. Just enter your bridge's **"HASHED FINGERPRINT"** in the form and click on "Search"
{% endhint %}
+* Ensure that the Tor port related to the bridge and the Obfs4proxy service are working and listening at the the ports selected
+
+```bash
+sudo ss -tulpn | grep 'LISTEN.*\(tor\|obfs4proxy\)'
+```
+
+**Example** of expected output:
+
+```
+tcp LISTEN 0 4096 0.0.0.0:2016 0.0.0.0:* users:(("tor",pid=1302348,fd=7))
+tcp LISTEN 0 4096 127.0.0.1:9051 0.0.0.0:* users:(("tor",pid=14899,fd=7))
+tcp LISTEN 0 4096 0.0.0.0:9050 0.0.0.0:* users:(("tor",pid=14899,fd=6))
+tcp LISTEN 0 4096 *:2008 *:* users:(("obfs4proxy",pid=1302349,fd=7))
+```
+
* If you want to connect to your bridge manually, you will need to know the bridge's obfs4 certificate. Open the file **"obfs4\_bridgeline.txt"** to obtain your bridge info
```sh
@@ -274,7 +287,7 @@ More info to connect the Tor browser to your own Tor bridge on this [website](ht
### **Enable automatic software updates**
-One of the most important things to keep your relay secure is to install security updates timely and ideally automatically so you can not forget about them. Follow the instructions to enable automatic software updates for your operating system.
+One of the most important things to keep your relay secure is to install security updates timely and ideally do it automatically, so you can not forget about them. Follow the instructions to enable automatic software updates for your operating system.
* Install dependencies
@@ -309,7 +322,7 @@ Unattended-Upgrade::Automatic-Reboot "true";
unattended-upgrade --debug
```
-* If you just want to see the debug output but don't change anything use
+* If you want to see the debug output but don't change anything use
```sh
unattended-upgrade --debug --dry-run
@@ -346,7 +359,7 @@ nyx
* Press the right -> navigation key to navigate to page 2/5 to show the traffic of your Tor instance
-
+
* Press `"q"` key **2 times** to exit
diff --git a/itcoin/bitcoin/README.md b/itcoin/bitcoin/README.md
new file mode 100644
index 00000000..cc6ab085
--- /dev/null
+++ b/itcoin/bitcoin/README.md
@@ -0,0 +1,26 @@
+---
+title: Bitcoin
+nav_order: 30
+has_children: true
+layout:
+ title:
+ visible: true
+ description:
+ visible: false
+ tableOfContents:
+ visible: true
+ outline:
+ visible: true
+ pagination:
+ visible: true
+---
+
+# 2. ₿itcoin
+
+
+
+The base of a sovereign Bitcoin node is a fully validating [Bitcoin client](bitcoin-client.md). It will download the whole blockchain and validate every single transaction that ever happened. After this verification, the client can check the validity of all future transactions.
+
+Your [Bitcoin client](bitcoin-client.md) also acts as a data source for other applications, like the [Electrum server](electrum-server.md) (to use with your software and hardware wallets), blockchain explorer, or Lightning client.
+
+We first install [Bitcoin Core](bitcoin-client.md) and [Fulcrum](electrum-server.md) on the node. We then set up the powerful Sparrow desktop wallet on your computer and connect it to your Fulcrum server for secure and private base layer operations, such as sending and receiving payments from and to your hardware wallet. Finally, we install [BTC RPC Explorer](blockchain-explorer.md) on the node, a lite blockchain explorer with a clean web UI for privately checking your transactions and the mempool.
diff --git a/index-2/bitcoin-client.md b/itcoin/bitcoin/bitcoin-client.md
similarity index 89%
rename from index-2/bitcoin-client.md
rename to itcoin/bitcoin/bitcoin-client.md
index 84870a02..f2d41248 100644
--- a/index-2/bitcoin-client.md
+++ b/itcoin/bitcoin/bitcoin-client.md
@@ -16,7 +16,7 @@ layout:
We install [Bitcoin Core](https://bitcoin.org/en/bitcoin-core/), the reference client implementation of the Bitcoin network.
-
+
## This may take some time
@@ -26,9 +26,9 @@ Bitcoin Core will download the full Bitcoin blockchain, and validate all transac
We download the latest Bitcoin Core binary (the application) and compare this file with the signed and timestamped checksum. This is a precaution to make sure that this is an official release and not a malicious version trying to steal our money.
-💡 If you want to install the Ordisrespector patch to reject the Ordinals of your mempool, follow the [Ordisrespector bonus guide](../bonus/bitcoin/ordisrespector.md#preparations) and come back to continue with the ["Create the bitcoin user"](bitcoin-client.md#create-the-bitcoin-user) section.
+💡 If you want to install the Ordisrespector patch to reject the Ordinals of your mempool, follow the [Ordisrespector bonus guide](../../bonus/bitcoin/ordisrespector.md#preparations) and come back to continue with the ["Create the bitcoin user"](bitcoin-client.md#create-the-bitcoin-user) section.
-💡 If you want to install Bitcoin Core from the source code but without the Ordisrespector patch, follow the [Ordisrespector bonus guide](../bonus/bitcoin/ordisrespector.md#preparations) skipping [Apply the patch “Ordisrespector”](../bonus/bitcoin/ordisrespector.md#apply-the-patch-ordisrespector) and come back to continue with the ["Create the bitcoin user"](bitcoin-client.md#create-the-bitcoin-user) section.
+💡 If you want to install Bitcoin Core from the source code but without the Ordisrespector patch, follow the [Ordisrespector bonus guide](../../bonus/bitcoin/ordisrespector.md#preparations) skipping [Apply the patch “Ordisrespector”](../../bonus/bitcoin/ordisrespector.md#apply-the-patch-ordisrespector) and come back to continue with the ["Create the bitcoin user"](bitcoin-client.md#create-the-bitcoin-user) section.
### Download binaries
@@ -122,7 +122,7 @@ gpg --verify SHA256SUMS.asc
The following screenshot is just an **example** of one of the versions:
-
+
* If you're satisfied with the checksum, signature, and timestamp checks, extract the Bitcoin Core binaries
@@ -130,6 +130,10 @@ The following screenshot is just an **example** of one of the versions:
tar -xvf bitcoin-$VERSION-x86_64-linux-gnu.tar.gz
```
+{% hint style="info" %}
+If you want to [generate a full bitcoin.conf file](bitcoin-client.md#generate-a-full-bitcoin.conf-example-file), follow the proper [extra section](bitcoin-client.md#generate-a-full-bitcoin.conf-example-file), and then come back to continue with the [next section](bitcoin-client.md#binaries-installation)
+{% endhint %}
+
### Binaries installation
* Install it
@@ -166,6 +170,8 @@ sudo rm -r bitcoin-$VERSION && sudo rm bitcoin-$VERSION-x86_64-linux-gnu.tar.gz
```
{% endcode %}
+
+
### Create the bitcoin user & group
The Bitcoin Core application will run in the background as a daemon and use the separate user “bitcoin” for security reasons. This user does not have admin rights and cannot change the system configuration.
@@ -347,7 +353,7 @@ blocksonly=1
```
{% hint style="info" %}
-If you checked on the "[Check IPv6 availability](../index-1/security.md#check-ipv6-availability)" section and don't have IPv6 available, you can discard the IPv6 network of the Bitcoin Core by adding the next lines at the end of the configuration file:
+If you checked on the [Check IPv6 availability](../../index-1/security.md#check-ipv6-availability) section and don't have IPv6 available, you can discard the IPv6 network of the Bitcoin Core by adding the next lines at the end of the configuration file:
```
# Disable IPv6 network
@@ -356,7 +362,7 @@ onlynet=i2p
onlynet=ipv4
```
-This is a standard configuration. Check this Bitcoin Core [sample-bitcoind.conf](https://gist.github.com/1ma/65751ba7f148612dfb39ff3527486a92) with all possible options
+This is a standard configuration. Check this [Bitcoin Core sample bitcoind.conf](https://gist.github.com/twofaktor/af6e2226e2861fa86874340f5315aa01) file with all possible options or generate one yourself following the proper [extra section](bitcoin-client.md#generate-a-full-bitcoin.conf-example-file)
{% endhint %}
* Set permissions: only the user `bitcoin` and members of the `bitcoin` group can read it (needed for LND to read the "`rpcauth`" line)
@@ -375,7 +381,7 @@ exit
### Create systemd service
-The system needs to run the bitcoin daemon automatically in the background, even when nobody is logged in. We use `"systemd"`, a daemon that controls the startup process using configuration files.
+The system needs to run the bitcoin daemon automatically in the background. We use `systemd`, a daemon that controls the startup process using configuration files
* Create the systemd configuration
@@ -391,7 +397,7 @@ sudo nano /etc/systemd/system/bitcoind.service
[Unit]
Description=Bitcoin Core Daemon
-Wants=network-online.target
+Requires=network-online.target
After=network-online.target
[Service]
@@ -447,7 +453,7 @@ Keep **this terminal open,** you'll need to come back here on the next step to m
## Run
-To keep an eye on the software movements, [start your SSH program](../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as "`admin`"
+To keep an eye on the software movements, [start your SSH program](../../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as "`admin`"
* Start the service
@@ -504,7 +510,7 @@ ln -s /data/bitcoin /home/admin/.bitcoin
exit
```
-* Log in again as a user `admin` [opening a new SSH session](../index-1/remote-access.md#access-with-secure-shell)
+* Log in again as a user `admin` [opening a new SSH session](../../index-1/remote-access.md#access-with-secure-shell)
* Check symbolic link have been created correctly
```bash
@@ -616,7 +622,7 @@ If everything is running smoothly, this is the perfect time to familiarize yours
* You definitely need to have a [real copy](https://bitcoinbook.info/) of this book!
* Read it online on [GitHub](https://github.com/bitcoinbook/bitcoinbook)
-
+
* [Learning Bitcoin from the Command Line](https://github.com/ChristopherA/Learning-Bitcoin-from-the-Command-Line/blob/master/README.md) by Christopher Allen gives a thorough deep dive into understanding the technical aspects of Bitcoin
* Also, check out the [bitcoin-cli reference](https://en.bitcoin.it/wiki/Original\_Bitcoin\_client/API\_calls\_list)
@@ -761,7 +767,7 @@ rpcworkqueue=256
```
{% hint style="info" %}
-Realize that with `maxuploadtarget` parameter enabled you will need whitelist the connection to [Electrs](../bonus/bitcoin/electrs.md) and [Bisq](../bonus/bitcoin/bisq.md) by adding these parameter to `bitcoin.conf`:
+Realize that with `maxuploadtarget` parameter enabled you will need whitelist the connection to [Electrs](../../bonus/bitcoin/electrs.md) and [Bisq](../../bonus/bitcoin/bisq.md) by adding these parameter to `bitcoin.conf`:
For Electrs:
@@ -776,12 +782,48 @@ whitelist=bloomfilter@192.168.0.0/16
```
{% endhint %}
-### Manual page for bitcoin-cli
+### Renovate your Bitcoin Core Tor and I2P addresses
+
+* With user `admin`, stop bitcoind and dependencies
+
+```bash
+sudo systemctl stop bitcoind
+```
+
+* Delete
+
+```bash
+sudo rm /data/bitcoin/onion_v3_private_key &&
+```
+
+* Start bitcoind again
+
+```bash
+sudo systemctl start bitcoind
+```
+
+* If you want to monitor the bitcoind logs and the starting progress, type `journalctl -fu bitcoind` in a separate SSH session
+* Wait a minute to identify your newly generated addresses with
+
+{% code overflow="wrap" %}
+```bash
+bitcoin-cli getnetworkinfo | grep address.*onion && bitcoin-cli getnetworkinfo | grep address.*i2p
+```
+{% endcode %}
+
+**Example** of expected output:
+
+```
+> "address": "vctk9tie5srguvz262xpyukkd7g4z2xxxy5xx5ccyg4f12fzop8hoiad.onion",
+> "address": "sesehks6xyh31nyjldpyeckk3ttpanivqhrzhsoracwqjxtk3apgq.b32.i2p",
+```
+
+### The manual page for bitcoin-cli
* For convenience, it might be useful to have the manual page for `bitcoin-cli` in the same machine so that they can be consulted offline, they can be installed from the directory
{% hint style="warning" %}
-This extra section is not valid if you compiled it from source code using the [Ordisrespector bonus guide](../bonus/bitcoin/ordisrespector.md)
+This extra section is not valid if you compiled it from source code using the [Ordisrespector bonus guide](../../bonus/bitcoin/ordisrespector.md)
{% endhint %}
```sh
@@ -802,7 +844,52 @@ sudo cp * /usr/share/man/man1/
man bitcoin-cli
```
-⬆️ Now come back to the next section [Create the bitcoin user](bitcoin-client.md#create-the-bitcoin-user) to continue with the Bitcoin Core installation process.
+⬆️ Now come back to the next section [Create the bitcoin user](bitcoin-client.md#create-the-bitcoin-user) to continue with the Bitcoin Core installation process
+
+### Generate a full bitcoin.conf example file
+
+* Follow the [Installation progress before](bitcoin-client.md#installation)
+* With user `admin`, clone the source code from GitHub
+
+```bash
+git clone https://github.com/bitcoin/bitcoin.git
+```
+
+* Copy-paste the bitcoind binary file to the source code folder
+
+```bash
+cp /tmp/bitcoin-$VERSION/bin/bitcoind /tmp/bitcoin/src/
+```
+
+* Go to the `devtools` folder
+
+```bash
+cd bitcoin/contrib/devtools
+```
+
+* Exec the `gen-bitcoin-conf` script to generate the file
+
+```bash
+sudo ./gen-bitcoin-conf.sh
+```
+
+Expected output:
+
+```
+Generating example bitcoin.conf file in share/examples/
+```
+
+* Use `cat` to print it on the terminal to enable a copy-paste
+
+```bash
+cat /tmp/bitcoin/share/examples/bitcoin.conf
+```
+
+* Or `nano` to examine the content inside of
+
+```bash
+nano /tmp/bitcoin/share/examples/bitcoin.conf
+```
## Upgrade
@@ -991,7 +1078,7 @@ sudo rm /usr/local/bin/bitcoin-cli && sudo rm /usr/local/bin/bitcoind
### Uninstall FW configuration
-If you followed the [Bisq bonus guide](../bonus/bitcoin/bisq.md), probably you needed to add an allow rule on UFW to allow the incoming connection to the `8333` port (P2P)
+If you followed the [Bisq bonus guide](../../bonus/bitcoin/bisq.md), probably you needed to add an allow rule on UFW to allow the incoming connection to the `8333` port (P2P)
* Ensure you are logged in with the user `admin`, display the UFW firewall rules, and note the numbers of the rules for Bitcoin Core (e.g. "Y" below)
diff --git a/bitcoin/blockchain-explorer.md b/itcoin/bitcoin/blockchain-explorer.md
similarity index 95%
rename from bitcoin/blockchain-explorer.md
rename to itcoin/bitcoin/blockchain-explorer.md
index ca8b8513..49263969 100644
--- a/bitcoin/blockchain-explorer.md
+++ b/itcoin/bitcoin/blockchain-explorer.md
@@ -19,19 +19,19 @@ layout:
Run your own private blockchain explorer with [BTC RPC Explorer](https://github.com/janoside/btc-rpc-explorer). Trust your node, not some external services.
-
+
## Requirements
-* [Bitcoin Core](../index-2/bitcoin-client.md)
+* [Bitcoin Core](bitcoin-client.md)
* Others
- * [Node + NPM](../bonus/system/nodejs-npm.md)
+ * [Node + NPM](../../bonus/system/nodejs-npm.md)
## Introduction
After the MiniBolt runs your own fully validated node, and even acts as a backend for your hardware wallet with [Fulcrum](electrum-server.md), the last important puzzle piece to improve privacy and financial sovereignty is your own Blockchain Explorer. It lets you query transactions, addresses, and blocks of your choice. You no longer need to leak information by querying a third-party blockchain explorer that can be used to get your location and cluster addresses.
-[BTC RPC Explorer](https://github.com/janoside/btc-rpc-explorer) provides a lightweight and easy to use web interface to accomplish just that. It's a database-free, self-hosted Bitcoin blockchain explorer, querying [Bitcoin Core](../index-2/bitcoin-client.md) and [Fulcrum](electrum-server.md) via RPC.
+[BTC RPC Explorer](https://github.com/janoside/btc-rpc-explorer) provides a lightweight and easy to use web interface to accomplish just that. It's a database-free, self-hosted Bitcoin blockchain explorer, querying [Bitcoin Core](bitcoin-client.md) and [Fulcrum](electrum-server.md) via RPC.
## Preparations
@@ -62,7 +62,7 @@ npm -v
```
{% hint style="info" %}
-If the version is **`>=18`**, you can move to the next section. If Nodejs is not installed, follow this [Node + NPM bonus guide](../bonus/system/nodejs-npm.md) to install it
+If the version is **`>=18`**, you can move to the next section. If Nodejs is not installed, follow this [Node + NPM bonus guide](../../bonus/system/nodejs-npm.md) to install it
{% endhint %}
* Install the next dependency package. Press "**y**" and `enter` or directly `enter` when the prompt asks you
@@ -73,7 +73,7 @@ sudo apt install build-essential
### Reverse proxy & Firewall
-In the security [section](../index-1/security.md#prepare-nginx-reverse-proxy), we set up Nginx as a reverse proxy. Now we can add the BTC RPC Explorer configuration.
+In the security [section](../../index-1/security.md#prepare-nginx-reverse-proxy), we set up Nginx as a reverse proxy. Now we can add the BTC RPC Explorer configuration.
Enable the Nginx reverse proxy to route external encrypted HTTPS traffic internally to the BTC RPC Explorer. The `error_page 497` directive instructs browsers that send HTTP requests to resend them over HTTPS.
@@ -161,7 +161,7 @@ sudo su - btcrpcexplorer
curl https://github.com/janoside.gpg | gpg --import
```
-* Download the source code directly from GitHub and go to the `btc-rpc-explorer` folder
+* Download the source code directly from GitHub and go to the `btc-rpc-explorer` folder
{% code overflow="wrap" %}
```sh
@@ -228,23 +228,27 @@ Installation can take some time, be patient. There might be a lot of confusing o
cp .env-sample .env
```
-* Edit the `.env` file. Activate any setting by removing the `#` at the beginning of the line or editing directly
+* Edit the `.env` file.
```sh
nano .env
```
+{% hint style="info" %}
+Activate any setting by removing the `#` at the beginning of the line or editing directly
+{% endhint %}
+
* Instruct the BTC RPC Explorer to connect to the local Bitcoin Core
```
-# replace this line
+# Uncomment & replace the value of these lines
BTCEXP_BITCOIND_COOKIE=/data/bitcoin/.cookie
```
* To get address balances, either an Electrum server or an external service is necessary. Your local Electrum server can provide address transaction lists, balances, and more
```
-# replace these lines
+# Uncomment & replace the value of these lines
BTCEXP_ADDRESS_API=electrum
BTCEXP_ELECTRUM_SERVERS=tcp://127.0.0.1:50001
```
@@ -260,7 +264,7 @@ You can set additional features of [Privacy](blockchain-explorer.md#privacy) / [
{% endhint %}
* Save and exit
-* Exit the `btcrpcexplorer` user session to return to the "admin" user session
+* Exit the `btcrpcexplorer` user session to return to the `admin` user session
```sh
exit
@@ -284,6 +288,7 @@ sudo nano /etc/systemd/system/btcrpcexplorer.service
[Unit]
Description=BTC RPC Explorer
+Requires=bitcoind.service fulcrum.service
After=bitcoind.service fulcrum.service
[Service]
@@ -318,7 +323,7 @@ journalctl -fu btcrpcexplorer
## Run
-To keep an eye on the software movements, [start your SSH program](../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as "admin"
+To keep an eye on the software movements, [start your SSH program](../../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as "admin"
* Start the service
@@ -516,12 +521,12 @@ RPC Terminal / Browser require authentication. Set an authentication password vi
{% endhint %}
{% hint style="info" %}
-With DEMO mode enabled, the user will see the next message:
+With DEMO mode enabled, the user will see the next message:
`"Sorry, that RPC command is blacklisted. If this is your server, you may allow this command by removing it from the 'rpcBlacklist' setting in config.js."`
{% endhint %}
-
+
### Remote access over Tor
diff --git a/bitcoin/desktop-wallet.md b/itcoin/bitcoin/desktop-wallet.md
similarity index 93%
rename from bitcoin/desktop-wallet.md
rename to itcoin/bitcoin/desktop-wallet.md
index 35b6bbb6..bbd0d50a 100644
--- a/bitcoin/desktop-wallet.md
+++ b/itcoin/bitcoin/desktop-wallet.md
@@ -19,12 +19,12 @@ layout:
We install [Sparrow wallet](https://github.com/sparrowwallet/sparrow) on a computer and connect it to your Electrum server on your node for private Bitcoin on-chain transactions.
-
+
## Requirements
-* [Bitcoin Core](../index-2/bitcoin-client.md)
-* Electrum server: [Fulcrum](electrum-server.md) or [Electrs](../bonus/bitcoin/electrs.md)
+* [Bitcoin Core](bitcoin-client.md)
+* Electrum server: [Fulcrum](electrum-server.md) or [Electrs](../../bonus/bitcoin/electrs.md)
## Introduction
@@ -33,13 +33,13 @@ Sparrow wallet is an excellent software wallet to use with your MiniBolt: it's r
You can also use the following alternatives instead of Sparrow Wallet, according to your preferences and needs:
* BitBoxApp: wallet for users of BitBox hardware wallets
-* [Electrum Wallet Desktop](../bonus/bitcoin/electrum-wallet-desktop.md): a well-established poweruser wallet
+* [Electrum Wallet Desktop](../../bonus/bitcoin/electrum-wallet-desktop.md): a well-established poweruser wallet
* [Ledger Live](https://support.ledger.com/hc/en-us/articles/360017551659-Setting-up-your-Bitcoin-full-node?docs=true): wallet for users of Ledger hardware wallets (this wallet connects directly to Bitcoin Core)
* [Trezor Suite](https://blog.trezor.io/connecting-your-wallet-to-a-full-node-edf56693b545?gi=d1e285f3d3c5): wallet for users of Trezor hardware wallets
We will connect Sparrow wallet to our own Electrum server as it is the most private option. For more information about the privacy and security trade-offs of the various server connection options, read the following [article](https://www.sparrowwallet.com/docs/best-practices.html) by Craig Raw, the author of the wallet.
-
+
We will set up Sparrow to connect to Fulcrum within your local network. There is also an optional section at the end that explains how to connect Sparrow to Fulcrum using Tor for when you're on the move.
@@ -77,7 +77,7 @@ We now configure Sparrow to connect to your node within your local network.
> [...]
```
-
+
If there is a connection error message, try the following troubleshooting:
@@ -90,7 +90,7 @@ If there is a connection error message, try the following troubleshooting:
Let's go back to the wallet and check that it is connected to our own Electrum server.
* Close the server configuration window
-* Check the icon in the bottom right corner of the wallet window 
+* Check the icon in the bottom right corner of the wallet window 
* The icon should be a blue slider button and a mouse over should display "Connected to \[...] at height \[...]"
You're set! Sparrow is now configured to connect to your Electrum server from within your local network.
@@ -147,7 +147,7 @@ Expected output:
> [...]
```
-
+
You're set! Sparrow is now configured to connect to your node over Tor and you can use it wherever you are.
@@ -197,16 +197,16 @@ Expected output:
> [...]
```
-
+
{% hint style="info" %}
-If you followed the [**Use the Tor proxy from another device**](../index-1/privacy.md#use-the-tor-proxy-from-another-device) section, you can use the Tor instance of your node instead of the instance of your regular computer, simply put on the "Proxy URL" box, your node IP local address (i.e 192.168.1.60) instead of localhost (127.0.0.1)
+If you followed the [**Use the Tor proxy from another device**](../../index-1/privacy.md#use-the-tor-proxy-from-another-device) section, you can use the Tor instance of your node instead of the instance of your regular computer, simply put on the "Proxy URL" box, your node IP local address (i.e 192.168.1.60) instead of localhost (127.0.0.1)
{% endhint %}
Now, let's go back to the wallet and check that the proxy is working properly.
* Close the server configuration window
-* Check the two icons in the bottom right corner of the wallet window 
+* Check the two icons in the bottom right corner of the wallet window 
* The first icon should be grey, not red; and a mouse hover should display "External Tor proxy enabled"
You're set! Sparrow Wallet is now configured to use the Tor proxy when fetching the Bitcoin price and when communicating with the Whirlpool server during CoinJoins.
diff --git a/bitcoin/electrum-server.md b/itcoin/bitcoin/electrum-server.md
similarity index 96%
rename from bitcoin/electrum-server.md
rename to itcoin/bitcoin/electrum-server.md
index dd3fb838..ddbb82dc 100644
--- a/bitcoin/electrum-server.md
+++ b/itcoin/bitcoin/electrum-server.md
@@ -21,16 +21,16 @@ layout:
-
+
## Requirements
-* [Bitcoin Core](../index-2/bitcoin-client.md)
+* [Bitcoin Core](bitcoin-client.md)
* \~ 130GB of free storage for the database
-Fulcrum is a replacement for [Electrs](../bonus/bitcoin/electrs.md), these two services cannot be run at the same time (due to the same standard ports used), remember to stop Electrs doing `sudo systemctl stop electrs`.
+Fulcrum is a replacement for [Electrs](../../bonus/bitcoin/electrs.md), these two services cannot be run at the same time (due to the same standard ports used), remember to stop Electrs doing `sudo systemctl stop electrs`.
## Introduction
@@ -44,7 +44,7 @@ One possibility to use Bitcoin Core with your Bitcoin wallets is to use an Elect
## Preparations
-Make sure that you have [reduced the database cache of Bitcoin Core](../index-2/bitcoin-client.md#activate-mempool-and-reduce-dbcache-after-a-full-sync)
+Make sure that you have [reduced the database cache of Bitcoin Core](bitcoin-client.md#activate-mempool-and-reduce-dbcache-after-a-full-sync)
### Install dependencies
@@ -399,7 +399,7 @@ sudo nano /etc/systemd/system/fulcrum.service
[Unit]
Description=Fulcrum
-Wants=bitcoind.service
+Requires=bitcoind.service
After=bitcoind.service
StartLimitBurst=2
@@ -436,7 +436,7 @@ journalctl -fu fulcrum
## Run
-To keep an eye on the software movements, [start your SSH program](../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as "admin"
+To keep an eye on the software movements, [start your SSH program](../../index-1/remote-access.md#access-with-secure-shell) (eg. PuTTY) a second time, connect to the MiniBolt node, and log in as "admin"
* Start the service
@@ -448,7 +448,7 @@ sudo systemctl start fulcrum
-
+
@@ -464,7 +464,7 @@ DO NOT REBOOT OR STOP THE SERVICE DURING THE DB CREATION PROCESS. YOU MAY CORRUP
* When you see logs like this ` XXXX mempool txs involving XXXX addresses`, which means that Fulcrum is fully indexed
-
+
* Ensure the service is working and listening at the default `50002` & `50001` ports and the `8000` admin port
diff --git a/lightning/channel-backup.md b/lightning/channel-backup.md
index 4759edb2..84f79449 100644
--- a/lightning/channel-backup.md
+++ b/lightning/channel-backup.md
@@ -57,7 +57,7 @@ We recommend using both methods, but you can choose either one of them, dependin
## Requirements
-* [Bitcoin Core](../index-2/bitcoin-client.md)
+* [Bitcoin Core](../itcoin/bitcoin/bitcoin-client.md)
* [LND](lightning-client.md)
## Preparations
@@ -237,7 +237,7 @@ UUID=123456 /mnt/static-channel-backup-external vfat auto,noexec,nouser,rw,sync,
sudo mount -a
```
-* Ensure that `/mnt/static-channel-backup-external` is listed
+* Ensure that `/mnt/static-channel-backup-external` is listed
```bash
df -h /mnt/static-channel-backup-external
@@ -330,7 +330,7 @@ git config user.email "minibolt@dummyemail.com"
cd ~/.lnd
```
-* Replace `` with your own GitHub username. When prompted `"Are you sure you want to continue connecting (yes/no/[fingerprint])?"` type "yes" and enter
+* Replace `` with your own GitHub username. When prompted `"Are you sure you want to continue connecting (yes/no/[fingerprint])?"` type "yes" and enter
```bash
git clone git@github.com:/remote-lnd-backup.git
@@ -423,7 +423,7 @@ To keep an eye on the software movements, [start your SSH program](../index-1/re
sudo systemctl start scb-backup
```
-**Example** of expected output on the first SSH session with `journalctl -fu scb-backup` ⬇️
+**Example** of expected output on the first SSH session with `journalctl -fu scb-backup` ⬇️
```
Jul 25 17:31:54 minibolt systemd[1]: Started SCB Backup.
@@ -440,7 +440,7 @@ sudo touch /data/lnd/data/chain/bitcoin/mainnet/channel.backup
-Example of the expected output with journalctl -fu scb-backup ⬇️
+Example of the expected output with journalctl -fu scb-backup ⬇️
```
Jul 25 17:32:32 minibolt scb-backup[401705]: /data/lnd/data/chain/bitcoin/mainnet/channel.backup OPEN
@@ -473,7 +473,7 @@ Nov 05 23:18:43 minibolt scb-backup[1711268]: error: src refspec main does not m
Nov 05 23:18:43 minibolt scb-backup[1711268]: error: failed to push some refs to 'github.com:/remote-lnd-backup.git
```
-\-> Replace the line 41 `git push "--set-upstream origin`` `**`main"`** to "`git push --set-upstream origin`` `**`master"`** [in the script](channel-backup.md#create-script) , and try again
+\-> Replace the line 41 ` git push "--set-upstream origin`` `` `**`main"`** to "` git push --set-upstream origin`` `` `**`master"`** [in the script](channel-backup.md#create-script) , and try again
{% endhint %}
* **If you enabled the local backup**, check the content of your local storage device. It should now contain a backup file with the date/time corresponding to the test made just above
@@ -514,7 +514,7 @@ sudo rm /etc/systemd/system/scb-backup.service
### Uninstall script
-* Delete the script installed
+* Delete the script installed
```bash
sudo rm /usr/local/bin/scb-backup
diff --git a/lightning/lightning-client.md b/lightning/lightning-client.md
index 3cb39e8f..ca4a69e2 100644
--- a/lightning/lightning-client.md
+++ b/lightning/lightning-client.md
@@ -27,7 +27,10 @@ We set up [LND](https://github.com/lightningnetwork/lnd), the Lightning Network
## Requirements
-* [Bitcoin Core](../index-2/bitcoin-client.md)
+* [Bitcoin Core](../itcoin/bitcoin/bitcoin-client.md)
+* Others
+ * [PostgreSQL](../bonus-guides/system/postgresql.md)
+ * [Go!](../bonus-guides/system/go.md) **(optional)**
## Preparations
@@ -69,13 +72,41 @@ Expected output:
> tcp LISTEN 0 100 127.0.0.1:28333 0.0.0.0:* users:(("bitcoind",pid=773834,fd=22))
+### Install PostgreSQL
+
+{% hint style="warning" %}
+You may want to use the bbolt database backend instead of PostgreSQL, if yes, jump to the [next step](lightning-client.md#installation) and follow the [Use bbolt database backend](lightning-client.md#use-the-bbolt-database-backend) section and remember to create the `lnd.conf` properly with this configuration when you arrive at the [configuration section](lightning-client.md#configuration)
+{% endhint %}
+
+* With user `admin`, check if you already have PostgreSQL installed
+
+```bash
+psql -V
+```
+
+**Example** of expected output:
+
+```
+> psql (PostgreSQL) 15.3 (Ubuntu 15.3-1.pgdg22.04+1)
+```
+
+{% hint style="info" %}
+If you obtain "**command not found**" outputs, you need to follow the [PostgreSQL bonus guide installation progress](../bonus-guides/system/postgresql.md#installation) to install it and then come back to continue with the guide
+{% endhint %}
+
+#### Create PostgreSQL database
+
+* With user `admin`, create a new database with the `postgres` user
+
+```bash
+sudo -u postgres createdb -O admin lndb
+```
+
## Installation
### Download binaries
-We'll download, verify, and install LND.
-
-* Navigate to the temporary directory
+* We'll download, verify, and install LND. Navigate to the temporary directory
```sh
cd /tmp
@@ -84,7 +115,7 @@ cd /tmp
* Set a temporary version environment variable to the installation
```sh
-VERSION=0.17.5
+VERSION=0.18.0
```
* Download the application, checksums, and signature
@@ -257,7 +288,7 @@ sudo rm -r lnd-linux-amd64-v$VERSION-beta && sudo rm lnd-linux-amd64-v$VERSION-b
{% endcode %}
{% hint style="info" %}
-If you come to update this is the final step
+If you come to [update](lightning-client.md#upgrade) this is the final step
{% endhint %}
### Create the lnd user & group
@@ -288,7 +319,7 @@ sudo adduser admin lnd
sudo mkdir /data/lnd
```
-* Assign as owner the `lnd` user
+* Assign as owner the `lnd` user
```sh
sudo chown -R lnd:lnd /data/lnd
@@ -379,13 +410,13 @@ tlsautorefresh=true
tlsdisableautofill=true
# Channel settings
-# Fee settings - default LND base fee = 1000 (mSat),
-# default LND fee rate = 1 (ppm)
+# Fee settings - default LND base fee = 1000 (mSat), fee rate = 1 (ppm)
# You can choose whatever you want e.g ZeroFeeRouting (0,0) or ZeroBaseFee (0,1)
#bitcoin.basefee=0#bitcoin.feerate=0
-# Minimum channel size (default: 20000 sats). You can choose whatever you want
+# (Optional) Minimum channel size. Uncomment and set whatever you want
+# (default: 20000 sats)
#minchansize=20000
maxpendingchannels=5
@@ -401,7 +432,7 @@ protocol.simple-taproot-chans=true
# Watchtower client
wtclient.active=true
-# Specify the fee rate with which justice transactions will be signed
+# (Optional) Specify the fee rate with which justice transactions will be signed
# (default: 10 sat/byte)
#wtclient.sweep-fee-rate=10
@@ -415,19 +446,19 @@ ignore-historical-gossip-filters=true
stagger-initial-reconnect=true
# Database
-[bolt]
-# Set the next value to false to disable auto-compact DB
-# and fast boot and comment the next line
-db.bolt.auto-compact=true
-# Uncomment to do DB compact at every LND reboot (default: 168h)
-#db.bolt.auto-compact-min-age=0h
+[db]
+db.backend=postgres
-# Optional (uncomment the next 2 lines (default: CONSERVATIVE))
+[postgres]
+db.postgres.dsn=postgresql://admin:admin@127.0.0.1:5432/lndb?sslmode=disable
+db.postgres.timeout=0
+
+# (Optional) Uncomment the next 2 lines
+# (default: CONSERVATIVE)
#[Bitcoind]
-#bitcoind.estimatemode=ECONOMICAL
+#bitcoind.estimatemode=ECONOMICAL
[Bitcoin]
-bitcoin.active=true
bitcoin.mainnet=true
bitcoin.node=bitcoind
@@ -438,10 +469,10 @@ tor.streamisolation=true
{% hint style="info" %}
-This is a standard configuration. Check the official LND [sample-lnd.conf](https://github.com/lightningnetwork/lnd/blob/master/sample-lnd.conf) with all possible options
+This is a standard configuration. Check the official LND [sample-lnd.conf](https://github.com/lightningnetwork/lnd/blob/master/sample-lnd.conf) with all possible options if you want to add something special
{% endhint %}
-* Exit of the `lnd` user session to return to the **admin** user session
+* Exit of the `lnd` user session to return to the `admin` user session
```sh
exit
@@ -465,8 +496,8 @@ sudo nano /etc/systemd/system/lnd.service
[Unit]
Description=Lightning Network Daemon
-Wants=bitcoind.service
-After=bitcoind.service
+Requires=bitcoind.service postgresql.service
+After=bitcoind.service postgresql.service
[Service]
ExecStart=/usr/local/bin/lnd
@@ -588,12 +619,12 @@ or 'n' to create a new seed (Enter y/x/n):
{% tabs %}
{% tab title="Scenery 1" %}
-#### **If you are creating a new node and you wish to create a new seed**
+**If you are creating a new node and you wish to create a new seed**
* Press `n` and enter
{% hint style="info" %}
-If you choose this option, the next step will be choosing the passphrase **(optional -** press enter to proceed without a cipher seed passphrase**)**
+If you choose this option, the next step will be choosing the passphrase **(optional -** press enter to proceed without a cipher seed passphrase\*\*)\*\*
{% endhint %}
Expected output:
@@ -632,39 +663,36 @@ You can use a simple piece of paper, write them on the custom themed [Shiftcrypt
{% hint style="danger" %}
This piece of paper is all an attacker needs to empty your on-chain wallet!
-
-
🚫 **Do not store it on a computer**
🚫 **Do not take a picture with your mobile phone**
🚫 **This information should never be stored anywhere in digital form**
-
-
This information must be kept secret at all times
{% endhint %}
**Return to the first terminal with `journalctl -fu lnd`. Example of expected output ⬇️**
```
-Nov 26 19:17:38 raspiboltest lnd[1004]: 2023-11-26 19:17:38.037 [INF] LNWL: Opened wallet
-Nov 26 19:17:38 raspiboltest lnd[1004]: 2023-11-26 19:17:38.204 [INF] CHRE: Primary chain is set to: bitcoin
-Nov 26 19:17:38 raspiboltest lnd[1004]: 2023-11-26 19:17:38.244 [INF] LNWL: Started listening for bitcoind block notifications via ZMQ on 127.0.0.1:28332
-Nov 26 19:17:38 raspiboltest lnd[1004]: 2023-11-26 19:17:38.245 [INF] CHRE: Initializing bitcoind backed fee estimator in CONSERVATIVE mode
-Nov 26 19:17:38 raspiboltest lnd[1004]: 2023-11-26 19:17:38.244 [INF] LNWL: Started listening for bitcoind transaction notifications via ZMQ on 127.0.0.1:28333
-Nov 26 19:17:40 raspiboltest lnd[1004]: 2023-11-26 19:17:40.576 [INF] LNWL: The wallet has been unlocked without a time limit
-Nov 26 19:17:40 raspiboltest lnd[1004]: 2023-11-26 19:17:40.712 [INF] CHRE: LightningWallet opened
-Nov 26 19:17:40 raspiboltest lnd[1004]: 2023-11-26 19:17:40.722 [INF] SRVR: Proxying all network traffic via Tor (stream_isolation=true)! NOTE: Ensure the backend node is proxying over Tor as well
-Nov 26 19:17:40 raspiboltest lnd[1004]: 2023-11-26 19:17:40.723 [INF] TORC: Starting tor controller
-Nov 26 19:17:40 raspiboltest lnd[1004]: 2023-11-26 19:17:40.744 [INF] HSWC: Cleaning circuits from disk for closed channels
-Nov 26 19:17:40 raspiboltest lnd[1004]: 2023-11-26 19:17:40.744 [INF] HSWC: Finished cleaning: no closed channels found, no actions taken.
+[...]
+Nov 26 19:17:38 minibolt lnd[1004]: 2023-11-26 19:17:38.037 [INF] LNWL: Opened wallet
+Nov 26 19:17:38 minibolt lnd[1004]: 2023-11-26 19:17:38.204 [INF] CHRE: Primary chain is set to: bitcoin
+Nov 26 19:17:38 minibolt lnd[1004]: 2023-11-26 19:17:38.244 [INF] LNWL: Started listening for bitcoind block notifications via ZMQ on 127.0.0.1:28332
+Nov 26 19:17:38 minibolt lnd[1004]: 2023-11-26 19:17:38.245 [INF] CHRE: Initializing bitcoind backed fee estimator in CONSERVATIVE mode
+Nov 26 19:17:38 minibolt lnd[1004]: 2023-11-26 19:17:38.244 [INF] LNWL: Started listening for bitcoind transaction notifications via ZMQ on 127.0.0.1:28333
+Nov 26 19:17:40 minibolt lnd[1004]: 2023-11-26 19:17:40.576 [INF] LNWL: The wallet has been unlocked without a time limit
+Nov 26 19:17:40 minibolt lnd[1004]: 2023-11-26 19:17:40.712 [INF] CHRE: LightningWallet opened
+Nov 26 19:17:40 minibolt lnd[1004]: 2023-11-26 19:17:40.722 [INF] SRVR: Proxying all network traffic via Tor (stream_isolation=true)! NOTE: Ensure the backend node is proxying over Tor as well
+Nov 26 19:17:40 minibolt lnd[1004]: 2023-11-26 19:17:40.723 [INF] TORC: Starting tor controller
+Nov 26 19:17:40 minibolt lnd[1004]: 2023-11-26 19:17:40.744 [INF] HSWC: Cleaning circuits from disk for closed channels
+Nov 26 19:17:40 minibolt lnd[1004]: 2023-11-26 19:17:40.744 [INF] HSWC: Finished cleaning: no closed channels found, no actions taken.
[...]
```
{% endtab %}
{% tab title="Scenery 2" %}
-#### **If you had an old node and an existing cipher seed**
+**If you had an old node and an existing cipher seed**
* Press `y` and enter to recover it
@@ -721,8 +749,9 @@ lnd successfully initialized!
Return to the first terminal with `journalctl -f -u lnd`. Search to the next lines to ensure LND already entered the RECOVERY MODE and go out of this ⬇️
-
[...]
+Apr 17 21:17:19 minibolt lnd[63591]: 2024-04-17 21:17:19.288 [INF] LNWL: Opened wallet
+Apr 17 21:17:19 minibolt lnd[63591]: 2024-04-17 21:17:19.288 [INF] LTND: Wallet recovery mode enabled with address lookahead of 2500 addresses
[...]
Nov 26 19:47:08 minibolt lnd[1321]: 2023-11-26 19:47:08.642 [INF] LNWL: RECOVERY MODE ENABLED -- rescanning for used addresses with recovery_window=2500
Nov 26 19:47:08 minibolt lnd[1321]: 2023-11-26 19:47:08.685 [INF] LNWL: Seed birthday surpassed, starting recovery of wallet from height=2540246 hash=00000000000000178484e446a4fb5c966b5fd5db76121421bfa470c7c879ff05 with recovery-window=2500
@@ -743,7 +772,7 @@ The current state of your channels, however, cannot be recreated from this seed.
There is a dedicated [guide](channel-backup.md) to making an automatic backup
{% endhint %}
-* Type "exit" to return to the `admin` user
+* Return to the `admin` user
```sh
exit
@@ -757,16 +786,16 @@ sudo ss -tulpn | grep LISTEN | grep lnd
Expected output:
-
### Allow user "admin" to work with LND
-We interact with LND using the application `lncli`. At the moment, only the user "lnd" has the necessary access privileges. To make the user "admin" the main administrative user, we make sure it can interact with LND as well.
+We interact with LND using the application `lncli`. At the moment, only the user `lnd` has the necessary access privileges. To make the user "admin" the main administrative user, we make sure it can interact with LND as well.
-* As user `admin`, link the LND data directory in the user "`admin`" home. As a member of the group "`lnd`", the "`admin`" user has read-only access to certain files
+* As user `admin`, link the LND data directory in the user `admin` home. As a member of the group `lnd`, the `admin` user has read-only access to certain files
```sh
ln -s /data/lnd /home/admin/.lnd
@@ -795,7 +824,7 @@ drwxrwxr-x 5 admin admin 4096 Jul 12 07:57 .cargo
drwxrwxr-x 3 admin admin 4096 Jul 11 20:32 .config
drwx------ 3 admin admin 4096 Jul 15 20:54 .gnupg
-rw------- 1 admin admin 20 Jul 11 22:09 .lesshst
-lrwxrwxrwx 1 admin admin 9 Jul 18 07:10 .lnd -> /data/lnd
+lrwxrwxrwx 1 admin admin 9 Jul 18 07:10 .lnd -> /data/lnd
drwxrwxr-x 3 admin admin 4096 Jul 12 09:15 .local
drwxrwxr-x 3 admin admin 4096 Jul 16 09:23 .npm
-rw-r--r-- 1 admin admin 828 Jul 12 07:56 .profile
@@ -808,7 +837,7 @@ drwx------ 2 admin admin 4096 Jul 11 20:47 .ssh
-* Make all directories browsable for the group
+* Make all directories browsable for the group
```sh
sudo chmod -R g+X /data/lnd/data/
@@ -891,7 +920,7 @@ Monitor logs with `journalctl -fu lnd` to check the watchtower client is working
### Watchtower server
-Same as you can connect as a watchtower client to other watchtower servers, you could give the same service running an altruist watchtower server. **This was previously activated** in the `lnd.conf`, and you can see the information about it by typing the following command and sharing it with your peers.
+Same you can connect as a watchtower client to other watchtower servers, you could give the same service running an altruist watchtower server. **This was previously activated** in the `lnd.conf`, and you can see the information about it by typing the following command and sharing it with your peers.
```sh
lncli tower info
@@ -911,131 +940,414 @@ Expected output:
}
```
-{% hint style="info" %}
+{% hint style="warning" %}
This watchtower server service is not recommended to activate if you have a slow device without high-performance features, if yes consider disabling it commenting, or deleting the line `watchtower.active=true` of the `lnd.conf` file
{% endhint %}
-{% hint style="warning" %}
-Almost all of the following steps could be run with the [mobile](mobile-app.md) | [web](web-app.md) app guides. We strongly recommend using these applications with intuitive and visual UI to manage the Lightning Node, instead of using the command line
+{% hint style="info" %}
+Almost all of the following steps could be run with the [mobile](mobile-app.md) | [web](web-app.md) app guides. We strongly recommend using these applications with intuitive and visual UI to manage the Lightning Node, instead of using the command line. Anyway, if you want to explore the lncli, you have some useful commands in the[ extra section](lightning-client.md#some-useful-lncli-commands)
{% endhint %}
## Extras (optional)
-### Funding your Lightning node
+### Use the default bbolt database backend
-* Generate a new Bitcoin address (p2tr = taproot/bech32m) to receive funds on-chain and send a small amount of Bitcoin to it from any wallet of your choice
+Once you have skipped the before section of the [PostgreSQL installation](lightning-client.md#install-postgresql), and when you arrive at the [Configuration section](lightning-client.md#configuration), modify `lnd.conf` file
-```sh
-lncli newaddress p2tr
+* With user `lnd`, edit `lnd.conf`
+
+```bash
+nano /data/lnd/lnd.conf
```
-Expected output:
+* Replace `# Database` section about the PostgreSQL database backend
```
-> "address": "bc1p..."
+# Database
+[db]
+db.backend=postgres
+
+[postgres]
+db.postgres.dsn=postgresql://admin:admin@127.0.0.1:5432/lndb?sslmode=disable
+db.postgres.timeout=0
```
-* Check your LND wallet balance
+* To this
-```sh
-lncli walletbalance
+```
+# Database
+[bolt]
+# Set the next value to false to disable auto-compact DB
+# and fast boot and comment the next line
+db.bolt.auto-compact=true
+# Uncomment to do DB compact at every LND reboot (default: 168h)
+#db.bolt.auto-compact-min-age=0h
+```
+
+* Return to the `admin` user
+
+```bash
+exit
+```
+
+{% hint style="info" %}
+Continue with the guide on the [Create systemd service](lightning-client.md#create-systemd-service) section
+{% endhint %}
+
+### Migrate an existing bbolt database to PostgreSQL
+
+{% hint style="danger" %}
+Attention: this process is very risky, supposedly this [software is in an experimental state](https://github.com/lightninglabs/lndinit/pull/21) which could damage your existing LND database. Act at your own risk. It is recommended to start from scratch by closing all existing channels, rather than a migration
+{% endhint %}
+
+#### Install Go!
+
+* With user `admin`, verify that you've installed Go by typing the following command
+
+```bash
+go version
```
**Example** of expected output:
```
-{
- "total_balance": "712345",
- "confirmed_balance": "0",
- "unconfirmed_balance": "712345"
-}
+> go version go1.21.10 linux/amd64
```
-As soon as your funding transaction is mined (1 confirmation), LND will show its amount as "confirmed\_balance".
+{% hint style="info" %}
+If you obtain "**command not found**" outputs, you need to follow the [Go! bonus guide installation progress](../bonus-guides/system/go.md#installation) to install it and then come back to continue with the guide
+{% endhint %}
+
+#### Install lndinit
+
+* With user `admin`, go to the temporary folder
+
+```bash
+cd /tmp
+```
+
+* Clone the `migrate-db` branch of the lndinit, from the official repository of the Minibolt and enter to the lndinit folder
+
+{% code overflow="wrap" %}
+```bash
+git clone --branch migrate-db https://github.com/minibolt-guide/lndinit.git && cd lndinit
+```
+{% endcode %}
+
+* Compile it
+
+```bash
+make install
+```
{% hint style="info" %}
-If you want to open a few channels, you might want to send a few transactions. If you have only one UTXO, you need to wait for the change to return to your wallet after every new channel opening
+This process can take quite a long time, 5-10 minutes or more, depending on the performance of your device. Please be patient until the prompt shows again
{% endhint %}
-### Opening channels
+* Install it
+
+```bash
+sudo install -m 0755 -o root -g root -t /usr/local/bin /home/admin/go/bin/lndinit
+```
+
+* Check the correct installation
-Although LND features an optional "autopilot", we manually open some channels.
+```bash
+lndinit -v
+```
+
+**Example** of expected output:
-We recommend going on [amboss.space](https://amboss.space) or [1ML.com](https://1ml.com) and looking for a mix of big and small nodes with decent Node Ranks. Another great way to find peers to collaboratively set up channels is [LightningNetwork+](https://lightningnetwork.plus/).
+```
+2024-05-30 23:00:15.666 LNDINIT: Version 0.1.4-beta commit=, debuglevel=debug
+2024-05-30 23:00:15.668 LNDINIT: Config error: Please specify one command of: gen-password, gen-seed, init-wallet, load-secret, migrate-db, store-secret or wait-ready
+```
-To connect to a remote node, you need its URI that looks like `@host`:
+**(Optional)** Delete the installation files
-* the `` is just a long hexadecimal number, like `02b03a1d133c0338c0185e57f0c35c63cce53d5e3ae18414fc40e5b63ca08a2128`
-* the `host` can be a domain name, a clearnet IP address, or a Tor onion address, followed by the port number (usually `:9735`)
+```bash
+sudo rm -r /tmp/lndinit
+```
-Just grab the whole URI above the big QR code and use it as follows (we will use the `⚡2FakTor⚡` LN node **as an example**):
+#### Migrate bbolt database to PostgreSQL
-* **Connect** to the remote node, with the full URI
+* With user `admin`, stop lnd
-{% code overflow="wrap" %}
```bash
-lncli connect 02b03a1d133c0338c0185e57f0c35c63cce53d5e3ae18414fc40e5b63ca08a2128@aopvxn7cf7kv42u5oxfo3mplhl5oerukndi3wos7vpsfvqvc7vvmgyqd.onion:9735
+sudo systemctl stop lnd
+```
+
+* Confirm and ensure that LND is stopped successfully by monitoring logs
+
+```bash
+journalctl -fu lnd
```
-{% endcode %}
-* **Open a channel** using the `` only (_i.e._, the part of the URI before the `@`) and the channel capacity in satoshis.
+Expected output:
-The command has a built-in fee estimator, but to avoid overpaying fees, you can manually control the fees for the funding transaction by using the `sat_per_vbyte` argument as follows (to select the appropriate fee, in sats/vB, check [mempool.space](https://mempool.space/))
+
