📖Operation Tutorial
Last updated
Last updated
| CPU | RAM | Storage | Bandwidth |
|---|---|---|---|
*During the testnet, the validator's storage usage is small, expected to be in the hundreds of gigabytes level.
Ensure that the following software is installed in order to properly compile and run the Titan Consensus Node:
Git: for cloning the source code
Go 1.21+: for compiling the source code, Titan nodes are written in the Go language, make sure you have Go 1.21 or later installed
1. Initialize the node
Use Titan CLI initialize your node, this step will configure the node and create necessary file structure
Open the terminal
Run the following command, where <your-custom-moniker> is the unique name of your node you choose for identification in the network
This command will create a .titan folder under your user directory, which contains all necessary configuration files and data folders. This is the fundamental configuration environment for the node operation.
2. Set the custom name for the node
After initialization, you need to set or confirm the custom name of the node, which will be used to identify your name in the network
Open the configuration file with vim editor
Find the item moniker in the opened file. It should show the name you just set during initialization. If you want to modify it, you can do it here.
Replace <your-custom-moniker> with your prefered node name, this name will represent your node in the network.
Save and close the file. In vim, press Esc to exit the edit mode, enter :wq (write and quit) and press Enter to save your change and quit the editor.
3. Confirm the configuration
We suggest you to examine the directory structure of .titan to ensure all files are correctly created. You can use the following command.
Check whether sub directories config and delta exist.
Now, your Titan node has been successfully initialized with a custom name, and ready for connecting to the network and synchronizing data. These settings ensure your node can normally be identified and operates in Titan network.
2.1 Understand Seeds and Persistent Peers
When launching a Titan validator node, it is crucial to establish connections with other nodes in the network. Seeds and Persistent Peers are two ways to help new nodes discover and maintain network connectivity.
Seeds: The information of these nodes is used to help the new node to get the initial connection point of the network. Once the initial connection is established, the node will try to establish connections with more nodes of the network.
Persistent Peers: Unlike seed nodes, once the persistent peers are connected, the nodes will attempt to maintain a long-term connection to these nodes, which is critical to the stability of the network.
2.2 Edit the configuration file
Configuration file config.toml in ~/.titan/configis the main file to configure node connections
Open the configuration file
Find seedsandpersistent_peers and edit accordingly
2.3 Add a provided seed node
Configure your node with known stable seed nodes to enhance connection reliability when the node starts:
2.4 Use Quicksync Address Book
Downloading and using the Quicksync Address Book speeds up the synchronization of your nodes with the network, allowing them to integrate into the network faster.
Download and move the address book to the correct location:
Configuring reasonable Gas prices and fees is an important measure to protect nodes from abuse while maintaining economic efficiency. Setting these parameters ensures that only those transactions that pay sufficient fees are processed.
1. Understand Denomination and Unit Conversion
In the Titan-test-1 network, the smallest unit of currency is the uttnt, where 1 ttnt equals 1,000,000 uttnt . This conversion is very important because all transaction fees are calculated and paid in uttnt.
2. Calculate transaction fees
The transaction fee is calculated using the following formula, which is the fee that the network has to pay to run the transaction:
where
gas is the number of gas consumed in the execution of the transaction.
gasPricesis the cost of per unit of gas
3. Set the minimum gas price
Setting an appropriate minimum gas price (min-gas-price) is a key measure to ensure that your nodes do not process low-fee transactions. This not only protects your node from wasted resources (e.g. spam attacks), but also ensures that your node runs efficiently and economically.
Set the minimum gas price in ~/.titan/config/app.toml
4. Recommended gas price
For the current Titan-test-1 network, the suggested price of Gas is 0.0025 uttnt. This price is sufficient to fend off most spam transactions while keeping the network attractive.
The full node keeps all unconfirmed transactions in its memory pool. Setting a reasonable minimum Gas price is an important strategy to ensure that only transactions that meet the fee criteria are added to the memory pool. Doing so protects your nodes from low-quality or malicious transactions that could lead to service denials.
To ensure that your Titan node runs stably as a background service, it is critical to manage the titand service using systemd, which helps to automatically restart the node if it encounters problems.
1. Create a systemd service file
You need to create a new systemd service file /etc/systemd/system/titan.service, this file will define how to start and manage your Titan node.
Open a terminal and enter the following command to create and edit the service file:
In the editor, paste the following configuration. These settings define how to start the service and how to restart it automatically if it fails:
Description: Description of the service
After: Specifies that titandservice needs to start after the network is fully up
User: Specifies the user who will run the service. For security reasons, it may be necessary to create and specify a non-root user
ExecStart: Specifies the start command
Restart: Set to always to automatically restart the service if it fails
RestartSec: The number of seconds to delay restart after an error
LimitNOFILE: Increases the file descriptor limit to help nodes manage large numbers of connections
2. Enable and start the service
After saving the file and exiting the vim editor, execute the following commands to enable and start the service:
These commands will ensure that the Titan service starts automatically at system startup and restarts automatically if any problems occur during operation.
3. Check service status
Check the status of the Titan service to ensure that it is running:
If you need to see the logs of the service, you can use:
With the above steps, your Titan node will be running securely and stably as a systemd service, able to efficiently handle transactions and data on your network. This setup helps you reduce manual intervention and ensures that the node is always online and available.
Before you start running a Titan Validator, make sure your node is set up and synchronized to the latest block height. The following guide will help you step by step to become a validator:
Generate a new key pair: Create a new key pair using Titan Daemon (titand), this command will generate a new account and associated recovery phrase.
<name>: Choose a name for your key pair
Be sure to keep the generated phrase safe, as they can be used to recover your account. Recovery phrase can also be used to import wallet software such as Keplr.
Transfer tokens to your address：
Transfer a certain number of TTNT tokens to your new account address, which will be used to pay transaction fees as well as to fund self-delegated to the validator node.
Create validator config file:
First, create and edit the validator config file:
Replace parameters:
Add following info into the file:
Parameter descriptions:
<pubkey>: Use the command titand tendermint show-validator to obtain the public key of the validator
<amount>: The number of TTNT tokens you want to delegate to the validator.
<moniker>: The name of your validator. This is a custom name used to identify your node in the network.
<commission-rate>sets the commission rate charged by your validator. For example, if it is set to 0.07, this means that 7% of the rewards received by the principal will be charged as commission.
<commission-max-rate>The maximum commission rate your validator can charge. This is a security measure to protect the principal from arbitrary commission increases by the validator.
<commission-max-change-rate>The maximum rate of change your validator can make on the stated commission rate. This defines how often you can change the commission rate and how much can be adjusted per change.
<min-self-delegation>is the minimum number of tokens that the validator must consistently delegate on its own nodes. This parameter ensures that validators have enough financial incentive to maintain honest and responsible behavior.
<identity>: Optional identity signature (e.g., UPort or Keybase)
<website>: Optional website of the validator
<security>: Optional security email for the validator
<details>: Optional detail information of the validator
Use the config file to create the validator node:
Use the editted config file to create the validator node:
Parameter descriptions:
<account>: specify which account is used in for signing transactions. This should be the name of the account you created, which should have enough balance to cover transaction fees.
<ip>: Your public IP address. This parameter needs to be set if you intend your node to be a public peering point. If not, you can omit this parameter.
Becoming an active validator: Initially, your validator may not immediately become part of the active validator set, as a sufficient total amount of delegation is required to enter the active set.
Delegate operations: Users can use a wallet application such as Keplr to delegate TTNT to you or any other validator.
Monitor Status: You can use a blockchain browser such as Mintscan to monitor your validator status and ranking.
When setting up and running Titan validator nodes, it is extremely useful to have access to a dedicated Titan blockchain browser. Such a tool can help you monitor the network status in real-time, confirm that transactions are successful, and check the performance of your node and other nodes.
Recommended blockchain browser:
16 cores
16GB
2TB (SSD recommended for better speed)
Up / Down 100Mbps, Fixed Public IP