⛓️Joining Mainnet
Make sure you completed the Installation step before following this session. You will also need knowledge about linux service file (systemd).
Current Version: v2.0.1
Chain ID: titan_18888-1
Denom: atkx, tkx (1e18 atkx)
Endpoint: Mainnet
Explorer: https://tkxscan.io
Information
The Titan mainnet is currently running titand v2.0.1
. Visit the explorer to view real-time on-chain activity
We recommend running public mainnet nodes on a machine with at least two cores, 8GB of RAM, and 100GB of disk space SSD.
Installation & Configuration
Init config file and data
Now, a folder will be created by default in your HOME directory as $HOME/.titan
. This folder will store all the configuration and data files of the node during operation.
Retrieve the genesis file of the Titan Chain and store it in the config directory.
Config your node.
Set peers
Config external address
You will need to config external_address
in file config.toml
is external address of your node. Correct this config will allow other node in P2P network connect to your node.
Index:
By default, we disable all indexes and only keep 100 recent blocks to optimize the diskspace used by node.
If you want to enable index, you need to change the config in file app.toml
and config.toml
Ethereum transaction (in
app.toml
)
TX index, for query tx (in
config.toml
)
Config state sync
If you use the latest binary version, this is required to sync data from blockchain. If you want to sync data from the genesis block, you must start syncing from genesis binary and follow every upgrade in history.
Without this, your node will have to synchronize data from the genesis, which could take a considerable amount of time. Instead, we will search for snapshots from trusted peers at a specific height and then verify a minimal set of snapshot chunks against the network.
Get the block height and block hash. First, you need to access the explorer website to obtain the nearest block height and its corresponding hash. We configure a node to take a snapshot every 1000 blocks and keep the 10 most recent snapshots. Therefore, the snapshot corresponding to the nearest block height will have the highest thousand value. For example, at the time of writing this guide testnet block height is 37026
so the nearest block height will be 37000
. Enter the block height in the search bar at the top of the website to retrieve its hash. The hash of Block 37000
is: 7240576BE8C737A4DA3849C2739143944F2D87C7E2A449A0949D03D1B72E878C
After having block height and block hash run the following command in order (replace <BLOCK_HEIGHT>
and <BLOCK_HASH>
by the value you found in the above step)
rpc_servers
need at least 2 servers.
Create Service File
To make the upgrade process as convenient as possible, instead of using titand
binary directly we recommend you follow this guide to use cosmovisor
Get your absolute path of titand
binary and your HOME directory that contains .titan
folder
Create a service file at /etc/systemd/system/titand.service
. Replace <titand_absolute_path>
and <home_directory>
to your.
To find out your <titand_absolute_path>
you can use command which titand
. And your <home_directory>
by command echo $HOME
Start the Service
Now that your node has started up and the synchronization process has begun, you can check the sync status of the node using the following command. If the node is syncing, it will show true
. Please wait until it show false
, which means your node has caught up with the network and is ready for querying.
If have any issue, you can check error log by
Last updated