Running a testnet node
Running a testnet node is very similar to running a mainnet node. Therefore, we recommand you to read the mainnet version first and to adjust the commands with the instructions provided here.
Starting a Node
To start your clients and contribute to the LUKSO testnet network, you have 3 options.
📟 With the LUKSO CLI
Difficulty: Medium 🌶️🌶️
For the main information, please refer to the mainnet version of this article. The only difference to run a testnet node with the CLI is to append the --testnet flag to the commands:
If you are starting your node in a fresh working directory or after being offline for a while, make sure to add the checkpoint synchronization flag to significantly speed up the synchronization during the startup.
lukso start --testnet
For the logs:
# Viewing the logs of the execution client
lukso logs execution --testnet
# Viewing the logs of the consensus client
lukso logs consensus --testnet
For more options, check the LUKSO CLI documentation.
🚢 With Docker
Difficulty: Hard 🌶️🌶️🌶️
The process is similar to the mainnet version. You will simply need to use the testnet genesis files instead of the mainnet ones.
So, when fetching the genesis files, the command should look like this (main is replaced by testnet):
mkdir configs
wget -O ./configs/genesis.ssz https://raw.githubusercontent.com/lukso-network/network-configs/main/testnet/shared/genesis.ssz
wget -O ./configs/genesis.json https://raw.githubusercontent.com/lukso-network/network-configs/main/testnet/shared/genesis.json
wget -O ./configs/config.yaml https://raw.githubusercontent.com/lukso-network/network-configs/main/testnet/shared/config.yaml
📄 With your own clients
Difficulty: Advanced 🌶️🌶️🌶️🌶️
The process is similar to the mainnet version. You will have to use the files in the testnet folder instead of the mainnet folder.
Need Help?
Check the Network FAQ section.
Ask your question in the validators channel on the official LUKSO Discord server.