The third validator period will kick off on block 6259269. That should be happening around the 22nd of March, 2021.
The auction was a success, and we now have a new validator set that consists of 35 slots. This new set will replace the old one at the block height mentioned above. All the new validators should have their nodes up and running before the fork block is reached.
There’s a quickstart script for new validators to get started with their node. Those already running a node as a part of the current validator set will only need to update their nodes. The watchtower component allows auto-updates for those that have them enabled; others will need to do a manual update. Again, all the new validators should be ready to start sealing blocks as soon as the fork takes place. If you're not set up in time, you will lose out on block rewards, and the block times on the Trustlines Blockchain do increase.
If you’re a validator in the current set but did not acquire a slot in the third auction, we urge you to keep your node online until the fork block height has been reached.
To learn more about the third auction, check out our "Results of the Third Trustlines Validator Auction" post.
Getting started as a validator is easy
Get ready! We made it easy. There is a quickstart script that will install and start all the necessary components for you. The script guides you along the way during the setup, and you'll be ready to go.
You can also check out our “How to Install a Trustlines Node for Laika Testnet” video to get a general idea of what the setup requires.
The validator components also include some optional components. Still, we suggest you also run them for the benefit of the ecosystem.
The individual components included in the setup are:
- A node for the Trustlines Blockchain itself
- The netstats client to report the node state to https://netstats.tlbc.trustlines.foundation (optional)
- A monitor that checks if the validators act honestly (optional)
- The bridge between Ethereum and the Trustlines Blockchain (only ran by validators)
- Also possible to set up a node for Ethereum (required for bridge to function)
The quickstart script
You will need to be running an Ubuntu-based distro on your machine for the quickstart script to work correctly. The quickstart script will set up the TLBC node and the monitor service, as well as the optional bridge and netstats clients. It allows importing a private key to act as a validator. It will also start a watchtower to update the Docker containers when newer versions become available automatically (e.g., for bug fixes or network forks). If the optional bridge is chosen to be installed, it will allow you to set up an Ethereum node as well to operate the bridge.
The quickstart script can be found at quickstart.tlbc.trustlines.foundation. You can download it or execute it as a one-line command with
bash <(curl -L quickstart.tlbc.trustlines.foundation)
The script is interactive and will ask you which components you wish to set up. Once complete, the various parts will run in the background in the form of Docker containers. Configuration and chain data can be found in the
tlbc directory placed in the current working directory. It is possible to customize the setup by editing the configuration files. This goes for the configuration of the different components and the composition of the Docker containers. If an optional component has not been set up on an earlier run, it can be added later by executing the quickstart script again.
Executing the script again is safe. No configuration will be overridden without asking, in case the user made changes to them themselves. If conflicting configuration updates occur, they are shown to the user, who can see a diff of the changes.
Manual installation is also possible and is available at the Trustlines Dev Docs. The chain spec file will include the validator set as well as the fork block.
Based on the experiences we've had, we recommend at least 4GB of memory and 20GB of SSD storage.
Validators should make sure their node has a high uptime. Otherwise, they miss out on potential block rewards and harm the network by increasing the average block intervals and time to finality.
For block validation and creation, it is essential to make sure your host system has the correct time configuration. On most systems, this should be the case by default. You can check the settings with
timedatectl (look for "System clock synchronized: yes").
For validators, it is crucial to back up their private key safely. If you lose your key, you won't be able to produce any blocks, earn block rewards, or withdraw your stake once it is unlocked.
Furthermore, it is advisable to keep the number of funds stored in the validator account small by regularly sending the newly earned rewards to a different account (e.g., a cold wallet stored on another device).
Earning block rewards
The validators will be sealing and producing blocks in a round-robin fashion. Each one gets their turn sequentially. If a validator node is offline and inactive, it will take some time for the sequence to move onto the next validator. This can cause some delays in producing blocks.
A validator currently gets 3 TLC per block produced as a block reward. The blocks can also include additional rewards paid in the form of transaction fees.
So get set up and start your nodes!
We look forward to seeing validators coming online and wish everyone all the best with the third validator period.
Trustlines ecosystem is growing
For technical discussions and questions, join the Trustlines Community Gitter.
We also have a section at the Trustlines Forum for validators! There you can discuss issues as well as share your experience of becoming a Trustlines validator.
And don’t hesitate to get in touch if you have any questions or need help setting up your node.