Testnet Campaign Flow (Phase 1)
Table of Contents
- What do I need to participate in testnet campaign?
This simple guide will help you participate in The Power testnet campaign.
Please, turn off the firewall before starting your work with the node.
Prerequisites for a node
|CPU cores||Memory||Hard disk||Network|
|4||4 GB or more||Minimum: 40 GB, SSD preferred||100 Mbit/s|
|OS||Erlang version||Eshell version||Docker version||Server|
|Ubuntu 22.04||24.3||10.4||latest (20.10.18 as of September 2022)||Virtual machine|
You need to have a clear server to work with your node. If you have done any experiments before, please delete the previous builds.
What do I need to participate in testnet campaign?
To participate in ThePower testnet campaign you need to:
Step 1: Learn
Learn what is a testnet in DCloud. This guide will help you understand what ThePower Testnet is.
Step 2: IP addresses and DNS
You need to have a public IP address to take part in the testnet campaign. You can register a DNS for your server, if you want. The word "domain" will be used in the text below with the meaning of "domain", or of "IP address".
Step 3: Install Erlang
Before starting Tea Ceremony you need to set up your environment by installing Erlang. You will need Erlang to run the Tea Ceremony client. You will not be able to start the node and connect to the chain without Tea Ceremony. To install Erlang, run:
apt -y install erlang-base erlang-public-key erlang-ssl
You need to install
erlang-ssl. Otherwise, Erlang will not operate properly!
Step 4: Get Tea Ceremony client and token
Get the Tea Ceremony client by running the following command:
teaclientfile mode to executable by running the following command:
chmod +x teaclient
Otherwise, you will NOT be able to start the client.
Get the Tea Ceremony token from the testnet bot.note
This and the following steps are crucial because you will NOT be able to start your node without
node.configfiles. You can find more information about these files here.
Step 5: Start the Tea Ceremony client
Before starting the Tea Ceremony, make sure you've opened the ports
1080 like this:
ufw allow 22
ufw allow 1800
ufw allow 1443
ufw allow 1080
We strongly recommend you to start the Tea Ceremony in
To start the client, run the following command:
./teaclient -n nickname aaaaa.bbbbb
teaclient— Tea Ceremony client,
nickname— The name of your node. Maximum 10 characters,
aaaaa.bbbbb— Tea Ceremony Token, you've got from the Tea Ceremony bot,
-nis used with a minus sign, not with a dash.
The token (
aaaaa.bbbbb) consists of two parts:
aaaaa— chain token. It is common for all nodes in the chain, and
bbbbb— personal token. It can't be expired until it is used, but you can use it only once.
If you start the Tea Ceremony with the chain part of the token, you will be able to check the ports availability.
After you have started the client, wait for other participants. Please, DON'T turn off the Tea Ceremony client for 24 hours.
If the client is started without options, you will see a short reference on the command and options.
If you have successfully started the Tea Ceremony client, you will get
genesis.txt files after the ceremony ends. You can find these files under the same directory where you have started the Tea Ceremony client.
You can get a ready-to-work
node.config file. To do this, rerun the Tea Ceremony.
Check out the nickname requirements:
- min. 4 symbols;
- max. 16 symbols;
- the nickname must contain alphanumeric symbols of any case.
Step 6: Download the node
Download ThePower Node. Here you have two options:
- Download ThePower node using the Docker image (recommended for most users), or
- Download the source code and build it (only for advanced users).
Download, build, and run the node using Docker
Use this manual to download, build, and run the node using Docker. It is a fast and easy way to build and run the Power Node. Recommended to the most of testneters.
Download, build, and run the node using the source code
Use this manual to download, build, and run the node from the source code if you want to go through the advanced way of building sources, but we still recommend you to use the Docker image.