RaMiX on Testnet
You can run your RaMiX node on testnet to develop and experiment with new applications, without putting real money at risk. This bonus guide highlights all configuration changes compared to the main guide.
Difficulty: Medium
Introduction
Running a testnet node is a great way to get acquainted with the RaMiX 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 RaMiX, and this page should provide you with the knowledge to get there.
The great news is that most of the RaMiX guide can be used as-is. The small adjustments come in the form of changes to the config files and ports for testnet. You can follow the guide and replace the following configurations in the right places as you go.
Advice:
For the moment, this guide will touch only the case of an only testnet mode situation, in the future, we will study adding the case of configuration to enable the parallel/simultaneous mode (
mainnet+testnet
in the same device) in an extra section in this guide.
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.
Bitcoin
Follow the complete RaMiX guide from the beginning (Bitcoin client included), when you arrive at the "Configuration section", stay tuned to replace and add the next lines on the
"bitcoin.conf"
file
When you finish the Running Bitcoin section, with the user
admin
provide read and execute permissions to the Bitcoin group for the testnet folder
Attention: the step before is critical**!** to allow the Bitcoin Core dependencies to access the .cookie
file and startup without problems
The rest of the Bitcoin client guide is the same as the mainnet mode
Follow the complete Electrum server guide from the beginning, when you arrive at the "Configure Firewall" section:
Replace the next lines to 60001/60002 ports, to match with the Testnet mode
When you arrive at the "Data directory" section, on the _"Download the custom Fulcrum banner based on RaMiX ..." step, d_ownload the Fulcrum testnet banner instead of the mainnet banner
In the next Configuration step, stay tuned to replace the next lines on the
fulcrum.conf
file, to match with the testnet mode
When you arrive at the remote access over the Tor section, edit the torrc file
Replace ports to 60001/60002 to match with testnet mode
Reload the Tor configuration and get your connection addresses
Example of expected output:
You should now be able to connect to your Fulcrum server remotely via Tor using your hostname and port 60001 (TCP) or 60002 (SSL)
The rest of the Fulcrum guide is the same as the mainnet mode
Follow the complete guide from the beginning, when you arrive at the Configuration section, set the next lines with the next values instead of the existing ones for mainnet. Edit
.env
file
The rest of the BTC RPC Explorer guide is the same as the mainnet mode
Lightning
Replace the parameter
bitcoin.mainnet=true
with thebitcoin.testnet=true
to enable LND in testnet mode
If you use Ordirespector on testnet, add the next lines at the end of the file:
When you arrive at the Create systemd service section, edit the
lnd.service
file and replaceExecStop
parameter to this
When you arrive at the Watchtower client section, keep in mind that the Watchtower server suggested won't work with the LND testnet, same with the LND mainnet peer suggested to open the channel and send a payment
Interacting with the LND daemon
Note that when interacting with the LND daemon, you'll need to use the
"--network testnet"
flag. Example:
Note that it has a list of testnet aliases related to these commonly used commands to make it easier to introduce in the terminal. Follow the "Aliases bonus guide" to install it
The rest of the Lightning Client guide is the same as the mainnet mode
Follow the complete guide from the beginning, when you arrive at the "Create script" section, create the script
Replace the
line 18
in the script to match with the testnet path
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 on the script to this for example:
REMOTE_BACKUP_DIR="/data/lnd/remote-lnd-testnet-backup"
When you arrive at the "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" section, replace the command with:
git clone [email protected]:<YourGitHubUsername>/remote-lnd-testnet-backup.git
When you arrive at the "GitHub test" section, replace the command to:
cd remote-lnd-testnet-backup
The rest of the Channel Backup guide is the same as the mainnet mode
Follow the complete guide from the beginning, when you arrive at the Configuration section, replace the next parameter to match with the testnet mode on the
.env.local
file
And replace the next parameter on the
thubConfig.yaml
file
The rest of the Web app: Thunderhub is the same as the mainnet mode
Follow the complete guide from the beginning, when you arrive at the Create a lndconnect QR code section, modify the "lndconnect" command to match with the next
For example, to generate a QR code for a Wireguard VPN connection, enter this command:
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
Bonus section
Bitcoin: Electrs
Follow the complete guide from the beginning, when you arrive at the Reverse proxy & Firewall section, follow the next steps:
Configure the Firewall to allow incoming requests
Create the
electrs-reverse-proxy.conf
file
Replace the mainnet ports
50021/50022
with the60021/60022
testnet ports
Test and reload Nginx configuration
When you arrive at the Configuration section, replace it with the next lines
When you arrive at the Remote access over Tor section
Edit the torrc file and replace ports to
60021/60022
to match with testnet mode
Reload the Tor configuration and get your connection addresses
Example of expected output:
The rest of the Channel Backup guide is the same as the mainnet mode
Port reference
Here we are going to describe only what ports differ from the mainnet mode:
Last updated