> For the complete documentation index, see [llms.txt](https://minibolt.minibolt.info/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://minibolt.minibolt.info/bonus-guides/bitcoin/minibolt-on-testnet.md).
# MiniBolt on Testnet
You can run your MiniBolt node on **Testnet4** to develop and experiment with new applications without risking real money. This bonus guide highlights all configuration changes compared to the main guide.
{% hint style="warning" %}
Difficulty: Medium
{% endhint %}
## Introduction
Running a testnet node is a great way to get acquainted with the MiniBolt and the suite of Bitcoin-related software typical of these powerful setups. Moreover, testnet empowers users to tinker with the software and its many configurations without the threat of losing funds. Helping Bitcoiners run a full testnet setup is a goal worthy of the MiniBolt, and this page should provide you with the knowledge to get there.
The great news is that most of the MiniBolt guide can be used as-is. The small adjustments come in the form of changes to the config files and ports for the testnet. You can follow the guide and replace the following configurations in the right places as you go.
{% hint style="info" %}
> **Advice:**
>
> For the moment, this guide will touch **only the case of simultaneous mode situation for Bitcoin client**, in the future, we will study adding the case of configuration to enable the parallel/simultaneous mode (`mainnet+testnet` in the same device, that is in the same MiniBolt node.
> The services mentioned in this guide are those that have been tested using testnet configuration and these worked fine. Later, in the next versions of this guide, we will go to adding other process to adapt other services to the testnet mode.
> {% endhint %}
## Bitcoin
### Bitcoin client: [Bitcoin Core](/bitcoin/bitcoin/bitcoin-core.md) or [Bitcoin Knots](/bonus-guides/bitcoin/bitcoin-knots.md)
{% hint style="success" %}
Mainnet + testnet simultaneous mode
{% endhint %}
* Follow the complete MiniBolt guide from the beginning ([Bitcoin client: Bitcoin Core](/bitcoin/bitcoin/bitcoin-core.md) or [Bitcoin Knots](/bonus-guides/bitcoin/bitcoin-knots.md) included) when you arrive at the ["Configuration section"](/bitcoin/bitcoin/bitcoin-core.md#configuration)
```bash
nano /home/bitcoin/.bitcoin/bitcoin.conf
```
* Stay tuned to add the next lines to the `bitcoin.conf` file.
{% hint style="info" %}
`[main]` and the `# Initial block download optimizations` parameters behind the `[testnet4]` section are needed only if you want to run a mainnet + testnet simultaneous nodes
{% endhint %}
```
[main]
# Exclusive mainnet node uacomment
uacomment=MiniBolt node mainnet
[testnet4]
# P2P testnet4 bind
bind=127.0.0.1
bind=127.0.0.1=onion
# Exclusive testnet4 node uacomment
uacomment=MiniBolt node testnet4
# Initial block download optimizations (exclusive for the testnet4 instance)
dbcache=2048
blocksonly=1
```
* When you arrive at the [Create systemd service](/bitcoin/bitcoin/bitcoin-core.md#create-systemd-service), create a new systemd file configuration for Testnet4
```bash
sudo nano /etc/systemd/system/bitcoind-testnet4.service
```
* Include this content
```
# MiniBolt: systemd unit for bitcoind
# /etc/systemd/system/bitcoind-testnet4.service
[Unit]
Description=Bitcoin client daemon (Testnet4)
Requires=network-online.target
After=network-online.target
[Service]
ExecStart=/usr/local/bin/bitcoind -testnet4 \
-pid=/run/bitcoind/bitcoind-testnet4.pid \
-conf=/home/bitcoin/.bitcoin/bitcoin.conf \
-datadir=/home/bitcoin/.bitcoin \
-startupnotify='systemd-notify --ready' \
-shutdownnotify='systemd-notify --status="Stopping"'
# Process management
####################
Type=notify
NotifyAccess=all
PIDFile=/run/bitcoind/bitcoind-testnet4.pid
Restart=on-failure
TimeoutStartSec=infinity
TimeoutStopSec=600
# Directory creation and permissions
####################################
User=bitcoin
Group=bitcoin
RuntimeDirectory=bitcoind
RuntimeDirectoryMode=0710
UMask=0027
# Hardening measures
####################
PrivateTmp=true
ProtectSystem=full
NoNewPrivileges=true
PrivateDevices=true
MemoryDenyWriteExecute=true
SystemCallArchitectures=native
[Install]
WantedBy=multi-user.target
```
* Enable autoboot **(optional)**
```bash
sudo systemctl enable bitcoind-testnet4
```
* Prepare “bitcoind” monitoring by the systemd journal and check the logging output. You can exit monitoring at any time with Ctrl-C
```bash
journalctl -fu bitcoind-testnet4
```
* When you arrive at the [Run](/bitcoin/bitcoin/bitcoin-core.md#run) section, start the service with this
```bash
sudo systemctl start bitcoind-testnet4
```
{% hint style="warning" %}
**Attention:** the next step is critical to allow the Bitcoin client dependencies to access the `.cookie` file and start up without problems
{% endhint %}
* When you finish the [Run](/bitcoin/bitcoin/bitcoin-core.md#run) 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/testnet4
```
{% hint style="info" %}
Use the flag `--testnet4` when you use the `bitcoin-cli` commands, e.g `bitcoin-cli --testnet4 -netinfo`
{% endhint %}
{% hint style="success" %}
The rest of the Bitcoin client guide is the same as the mainnet mode
{% endhint %}
### [Electrum server: Fulcrum](/bitcoin/bitcoin/fulcrum.md)
{% hint style="warning" %}
Only testnet mode
{% endhint %}
Follow the complete Electrum server guide from the beginning, when you arrive at the ["Configure Firewall"](/bitcoin/bitcoin/fulcrum.md#configure-firewall) section:
[Configure Firewall](/bitcoin/bitcoin/fulcrum.md#configure-firewall)
* Replace the next lines with 40001/40002 ports, to match the Testnet mode
```sh
sudo ufw allow 40001/tcp comment 'allow Fulcrum Testnet4 TCP from anywhere'
```
```sh
sudo ufw allow 40002/tcp comment 'allow Fulcrum Testnet4 SSL from anywhere'
```
* When you arrive at the ["Data directory"](/bitcoin/bitcoin/fulcrum.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
wget https://raw.githubusercontent.com/minibolt-guide/minibolt/main/resources/fulcrum-banner-testnet4.txt
```
{% endcode %}
[Configuration](/bitcoin/bitcoin/fulcrum.md#configuration)
* In the next [Configuration](/bitcoin/bitcoin/fulcrum.md#configuration) step, stay tuned to **replace** the next lines in the `fulcrum.conf` file, to match the testnet mode
```sh
nano /data/fulcrum/fulcrum.conf
```
```
# Bitcoin client settings
bitcoind = 127.0.0.1:48332
rpccookie = /data/bitcoin/testnet4/.cookie
# Fulcrum server general settings
ssl = 0.0.0.0:40002
tcp = 0.0.0.0:40001
# Banner
banner = /data/fulcrum/fulcrum-banner-testnet4.txt
```
[Create systemd service](/bitcoin/bitcoin/fulcrum.md#create-systemd-service)
* When you arrive at the [Create systemd service](/bitcoin/bitcoin/fulcrum.md#create-systemd-service) section, stay tuned to replace the next lines in the `fulcrum.service` file, to match the Bitcoin client on Testnet mode dependency. Save and exit
```bash
sudo nano +6 -l /etc/systemd/system/fulcrum.service
```
```
Requires=bitcoind-testnet4.service
After=bitcoind-testnet4.service
```
[Remote access over Tor](/bitcoin/bitcoin/fulcrum.md#remote-access-over-tor)
* When you arrive at the[ remote access over the Tor section](/bitcoin/bitcoin/fulcrum.md#remote-access-over-tor), edit the torrc file
```sh
sudo nano +63 -l /etc/tor/torrc
```
* Replace ports to `40001/40002` to match the testnet mode
```
############### This section is just for location-hidden services ###
# Hidden Service Fulcrum Testnet4 TCP & SSL
HiddenServiceDir /var/lib/tor/hidden_service_fulcrum_testnet4_tcp_ssl/
HiddenServiceEnableIntroDoSDefense 1
HiddenServicePoWDefensesEnabled 1
HiddenServicePort 40001 127.0.0.1:40001
HiddenServicePort 40002 127.0.0.1:40002
```
* Reload the Tor configuration
```sh
sudo systemctl reload tor
```
* Get your connection addresses
```sh
sudo cat /var/lib/tor/hidden_service_fulcrum_testnet4_tcp_ssl/hostname
```
**Example** of expected output:
```
abcdefg..............xyz.onion
```
{% hint style="info" %}
You should now be able to connect to your Fulcrum server remotely via Tor using your hostname and port 40001 (TCP) or 40002 (SSL)
{% endhint %}
{% hint style="success" %}
The rest of the **Fulcrum** guide is the same as the mainnet mode
{% endhint %}
### [Blockchain Explorer: BTC RPC Explorer](/bitcoin/bitcoin/btc-rpc-explorer.md)
{% hint style="danger" %}
**Not Testnet4 compatible yet, the next steps are not valid!**
{% endhint %}
* Follow the complete guide from the beginning. When you arrive at the [Configuration section](/bitcoin/bitcoin/btc-rpc-explorer.md#configuration), set the next lines with the next values instead of the existing ones for the mainnet. Edit **`.env`** file
```sh
nano /home/btcrpcexplorer/btc-rpc-explorer/.env
```
```
BTCEXP_BITCOIND_PORT=48332
BTCEXP_BITCOIND_COOKIE=/data/bitcoin/testnet4/.cookie
BTCEXP_ELECTRUM_SERVERS=tcp://127.0.0.1:40001
```
* When you arrive at the [Create systemd service](/bitcoin/bitcoin/btc-rpc-explorer.md#create-systemd-service) section, edit the `btcrpcexplorer.service` file and replace the next lines
```
Requires=bitcoind-testnet4.service fulcrum.service
After=bitcoind-testnet4.service fulcrum.service
```
{% hint style="success" %}
The rest of the **BTC RPC Explorer** guide is the same as the mainnet mode
{% endhint %}
## Lightning
### [Lightning client: LND](/lightning/lightning/lnd.md)
{% hint style="warning" %}
Only testnet mode
{% endhint %}
* Follow the complete guide from the beginning, when you arrive at the [Configuration](/lightning/lightning/lnd.md#configuration) section, edit `lnd.conf`
```bash
nano /data/lnd/lnd.conf
```
* Replace the parameter `bitcoin.mainnet=true` with the `bitcoin.testnet4=true` to enable LND in testnet mode
```
[Bitcoin]
bitcoin.testnet4=true
```
* When you arrive at the [Create systemd service](/lightning/lightning/lnd.md#create-systemd-service) section, edit the `lnd.service` file and replace the next lines
```
Requires=bitcoind-testnet4.service postgresql.service
After=bitcoind-testnet4.service postgresql.service
ExecStop=/usr/local/bin/lncli --network=testnet4 stop
```
{% hint style="info" %}
When you arrive at the [Watchtower client](/lightning/lightning/lnd.md#watchtower-client-recommended) section, keep in mind that the Watchtower server suggested won't work with the LND testnet4, same with the LND mainnet peer suggested to open the channel and send a payment
{% endhint %}
**Interacting with the LND daemon**
* Note that when interacting with the LND daemon, you'll need to use the `"--network=testnet4"` flag. Example:
```sh
lncli --network=testnet4 --tlscertpath /data/lnd/tls.cert.tmp create
```
#### Allow user "admin" to work with LND
* Note that when you arrive at this section, you need to replace the command: `sudo chmod g+r /data/lnd/data/chain/bitcoin/mainnet/admin.macaroon` to the next
```bash
sudo chmod g+r /data/lnd/data/chain/bitcoin/testnet4/admin.macaroon
```
{% hint style="info" %}
It has [a list of testnet aliases](https://raw.githubusercontent.com/minibolt-guide/minibolt/main/resources/.bash_aliases) related to these commonly used commands to make it easier to introduce in the terminal. Follow the [Aliases bonus guide](/bonus-guides/system/aliases.md) to install it
{% endhint %}
{% hint style="success" %}
The rest of the **Lightning Clien**t guide is the same as the mainnet mode
{% endhint %}
### [Channel backup](/lightning/lightning/channel-backup.md)
{% hint style="warning" %}
Only testnet mode
{% endhint %}
* Follow the complete guide from the beginning. When you arrive at the ["Create script"](/lightning/lightning/channel-backup.md#create-script) section, create the script
```sh
sudo nano /usr/local/bin/scb-backup --linenumbers
```
* Replace the `line 18` in the script to match the testnet path
```
SCB_SOURCE_FILE="/data/lnd/data/chain/bitcoin/testnet4/channel.backup"
```
{% hint style="info" %}
**If you have a mainnet node running on another device** and you want to use the same GitHub account for the testnet channel backups:
* Change this line in the script to this, for example: `REMOTE_BACKUP_DIR="/data/lnd/remote-lnd-testnet-backup"`
* When you arrive at the ["Create a GitHub repository"](/lightning/lightning/channel-backup.md#create-a-github-repository) section, change the name of the GitHub repo to, for example: "`remote-lnd-testnet-backup`"
* When you arrive at the ["Clone the repository to your node"](/lightning/lightning/channel-backup.md#clone-the-repository-to-your-node) section, replace the command with: `git clone git@github.com:/remote-lnd-testnet-backup.git`
* When you arrive at the ["GitHub test"](/lightning/lightning/channel-backup.md#github-test) section, replace the command with: `cd remote-lnd-testnet-backup`
{% endhint %}
{% hint style="success" %}
The rest of the **Channel Backup guide** is the same as the mainnet mode
{% endhint %}
### [Web app: ThunderHub](/lightning/lightning/thunderhub.md)
{% hint style="warning" %}
Only testnet mode
{% endhint %}
* Follow the complete guide from the beginning. When you arrive at the [Configuration](/lightning/lightning/thunderhub.md#configuration) section, replace the next parameter to match the testnet mode in the `.env.local` file
```
MEMPOOL_URL='https://mempool.space/testnet4'
```
* And replace the next parameter in the `thubConfig.yaml` file
```
macaroonPath: /data/lnd/data/chain/bitcoin/testnet4/admin.macaroon
```
{% hint style="success" %}
The rest of the **Web app: Thunderhub** is the same as the mainnet mode
{% endhint %}
### [Mobile app: Zeus](/lightning/lightning/zeus.md)
{% hint style="success" %}
Mainnet + testnet simultaneous mode
{% endhint %}
* Follow the complete guide from the beginning, when you arrive at the [**Create a lndconnect QR code**](/lightning/lightning/zeus.md#create-a-lndconnect-qr-code) section, modify the "lndconnect" command to match the next
For **example**, to generate a QR code for a WireGuard VPN connection, enter this command:
{% code overflow="wrap" %}
```sh
lndconnect --host=10.0.1.1 --port=8080 --bitcoin.testnet --adminmacaroonpath=/home/admin/.lnd/data/chain/bitcoin/testnet4/admin.macaroon --nocert
```
{% endcode %}
{% hint style="info" %}
Be careful to add `--nocert` parameter only to the onion and Wireguard VPN network, the local network could be shared with more devices, and you should use a valid certificate to encrypt the connection, so don't add that parameter in this case
{% endhint %}
## Bonus section
### Bitcoin: [Electrs](/bonus-guides/bitcoin/electrs.md)
{% hint style="warning" %}
Only testnet mode
{% endhint %}
Follow the complete guide from the beginning. When you arrive at the [Reverse proxy & Firewall](/bonus-guides/bitcoin/electrs.md#reverse-proxy-and-firewall) section, follow the next steps:
* Create the `electrs-reverse-proxy.conf` file
```sh
sudo nano /etc/nginx/streams-enabled/electrs-reverse-proxy.conf
```
* Replace the mainnet ports `50021/50022` with the `40021/40022` testnet4 ports
```nginx
upstream electrs {
server 127.0.0.1:40021;
}
server {
listen 40022 ssl;
proxy_pass electrs;
}
```
* Test and reload the Nginx configuration
```sh
sudo nginx -t
```
```bash
sudo systemctl reload nginx
```
* Configure the Firewall to allow incoming requests
```sh
sudo ufw allow 40022/tcp comment 'allow Electrs Testnet4 SSL from anywhere'
```
```sh
sudo ufw allow 40021/tcp comment 'allow Electrs Testnet4 TCP from anywhere'
```
[Configuration](/bonus-guides/bitcoin/electrs.md#configuration)
* When you arrive at the [Configuration](/bonus-guides/bitcoin/electrs.md#configuration) section, replace it with the next lines
```sh
nano /data/electrs/electrs.conf
```
* When you arrive at the [Create systemd service](/bonus-guides/bitcoin/electrs.md#create-systemd-service) section, edit the `btcrpcexplorer.service` file and replace the next lines
```
Requires=bitcoind-testnet4.service
After=bitcoind-testnet4.service
```
[Remote access over Tor](/bonus-guides/bitcoin/electrs.md#remote-access-over-tor-optional)
* When you arrive at the [Remote access over Tor](/bonus-guides/bitcoin/electrs.md#remote-access-over-tor-optional) section
```sh
sudo nano +63 /etc/tor/torrc
```
* Edit the `torrc` file and replace the ports with `40021/40022` to match the testnet4 mode
```
# Hidden Service Electrs Testnet4 TCP & SSL
HiddenServiceDir /var/lib/tor/hidden_service_electrs_testnet4_tcp_ssl/
HiddenServiceEnableIntroDoSDefense 1
HiddenServicePoWDefensesEnabled 1
HiddenServicePort 40021 127.0.0.1:40021
HiddenServicePort 40022 127.0.0.1:40022
```
* Reload the Tor configuration and get your connection addresses
```sh
sudo systemctl reload tor
```
```sh
sudo cat /var/lib/tor/hidden_service_electrs_testnet4_tcp_ssl/hostname
```
**Example** of expected output:
```
abcdefg..............xyz.onion
```
{% hint style="success" %}
The rest of the **Electrs guide** is the same as the mainnet mode
{% endhint %}
## Port reference
Here, we are going to describe only what ports differ from the mainnet mode: