SiteExplorerGitHubTwitterMedium

⚙️ Installation

🛠️ Hardware Requirements

Node Type
CPU
RAM
Storage

Full (Recommended)

4v CPU

8 GB

150GB SSD

Additional requirements

Chain ID
Version tag
Binary Name
Binary Home

titan-test-3

v2.1.0

titand

$HOME/.titan

⏱️ Installation time: ~20-40 minutes

The installation time depends on many factors, such as your skills, resources and characteristics of your server, the most important: disk speed, internet connection, server load CPU, RAM, so this value may differ from the one indicated by us.

⚡ Automatic installation

bash <(curl -s https://raw.githubusercontent.com/UnityNodes/scripts/refs/heads/main/titan-network/install-titan-testnet.sh)

With the help of a one-line script, all the necessary commands will be executed automatically, you only need to check the operation of your node at the end

📝 Manual installation

📌Step 1: Installation packeges and dependencies

# Install dependencies for building from source
sudo apt update
sudo apt install -y lz4 jq make git gcc build-essential curl chrony unzip gzip snapd tmux bc

# Install Go
sudo rm -rf /usr/local/go
curl -L https://go.dev/dl/go1.21.6.linux-amd64.tar.gz | sudo tar -xzf - -C /usr/local
echo 'export PATH=$PATH:/usr/local/go/bin:$HOME/go/bin' >> $HOME/.bash_profile
source .bash_profile

📌Step 2: Set moniker and install node

Give your validator a name by which you can find yourself in explorer, put it in ""

MONIKER=""

After that, insert the following node installation command

# Clone project repository
cd $HOME
rm -rf titan-chain
git clone https://github.com/Titannet-dao/titan-chain.git
cd titan-chain
git fetch origin
make install

# Set node CLI configuration
titand config node tcp://localhost:26657
titand config keyring-backend test
titand config chain-id titan-test-3
source $HOME/.bash_profile

# Initialize the node
titand init "$MONIKER" --chain-id titan-test-3

# Download genesis and addrbook files
curl -Ls https://snapshots-testnet.unitynodes.com/titan-testnet/genesis.json > $HOME/.titan/config/genesis.json
curl -Ls https://snapshots-testnet.unitynodes.com/titan-testnet/addrbook.json > $HOME/.titan/config/addrbook.json

# Set minimum gas price
sed -i.bak -e "s/^minimum-gas-prices *=.*/minimum-gas-prices = \"0.0025uttnt\"/;" ~/.titan/config/app.toml

# Set pruning
sed -i \
  -e 's|^pruning *=.*|pruning = "custom"|' \
  -e 's|^pruning-keep-recent *=.*|pruning-keep-recent = "100"|' \
  -e 's|^pruning-interval *=.*|pruning-interval = "17"|' \
  $HOME/.titan/config/app.toml

# Download latest chain data snapshot
curl https://snapshots-testnet.unitynodes.com/titan-testnet/titan-testnet-latest.tar.lz4 | lz4 -dc - | tar -xf - -C $HOME/.titan

# Create a service
sudo tee /etc/systemd/system/titand.service > /dev/null <<EOF
[Unit]
Description=titand
After=network-online.target

[Service]
User=$USER
ExecStart=$(which titand) start
Restart=on-failure
RestartSec=3
LimitNOFILE=65535

[Install]
WantedBy=multi-user.target
EOF

# Start the service and check the logs
sudo systemctl daemon-reload
sudo systemctl enable titand
sudo systemctl start titand.service
sudo journalctl -u titand.service -f -o cat

📌Step 3: Node Health Check

Follow the commands to check if your node is working properly

  1. Check version

titand version

  1. View sync status

while true; do 
  local_height=$(titand status | jq -r .sync_info.latest_block_height)
  network_height=$(curl -s https://rpc.titan-testnet.unitynodes.com/status | jq -r '.result.sync_info.latest_block_height')
  blocks_left=$((network_height - local_height))

  echo -e "\033[1;33m[Sync Status]\033[0m \033[1;32mNode Height:\033[0m \033[1;37m$local_height\033[0m | \033[1;32mNetwork Height:\033[0m \033[1;37m$network_height\033[0m | \033[1;32mBlocks Left:\033[0m \033[1;31m$blocks_left\033[0m"

  sleep 5
done

Blocks left - 0-1 everything is fine and your node catches up with the last block of the network.

  1. Check logs

sudo journalctl -u titand.service -f -o cat

If your node is installed and fully synchronized with the network, proceed with the creation of the validator.

For any questions you may have during installation, please contact our chat team or other project validators.

  1. [OPTIONAL] Change port

If you get an error that the default ports are busy, you can change them with the following command Example this error: ERR failure when running app err="failed to listen on 127.0.0.1:26657: listen tcp 127.0.0.1:26657: bind: address already in use"

#PORT 36
sed -i.bak -e "s%:1317%:2317%g; 
s%:8080%:9080%g;
s%:9090%:10090%g;
s%:9091%:10091%g;
s%:8545%:9545%g;
s%:8546%:9546%g;
s%:6065%:7065%g" $HOME/.titan/config/app.toml	
sed -i.bak -e "s%:26658%:36658%g;
s%:26657%:36657%g;
s%:6060%:7060%g;
s%tcp://0.0.0.0:26656%tcp://0.0.0.0:36656%g;
s%:26660%:36660%g" $HOME/.titan/config/config.toml
sed -i.bak -e "s%:26657%:36657%g" $HOME/.titan/config/client.toml
echo "" 
sudo systemctl restart titand && sudo journalctl -u titand -f -o cat

📝 Create Validator

📌Step 1: Create wallet

titand keys add wallet

Save all information after entering the command, without this you will not be able to restore data to the wallet. SAVE SEED PHRASE (12 words). ▶️ Example:

address: titan1zy5tte123hd25s926t0r5aaqq67hw2xkh6l7y2 name: wallet pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"AiEm5S70FP4HXGdp9FmxYaWOd2Q+EYaeMA4Vs0gWFceI"}' type: local

Important write this mnemonic phrase in a safe place. It is the only way to recover your account if you ever forget your password.

spider margin method scrap bad craft layer fire leaf depart pyramid dolphin mansion pride protect concert pattern energy knock nurse shrug guitar juice powder

📌Step 2: Request test tokens to your wallet address

Go to the discord server https://discord.gg/titannet , verify in the ✅start-here channel and get all the roles in 🔑roles , then go to the faucet-ttnt channel and request tokens $request address wallet

titand q bank balances $(titand keys show wallet -a)

If the node has synchronized and the tokens have arrived in the wallet, create a validator with the command below.

📌Step 3: Create validator

Create a validator.json file

touch $HOME/.titan/config/validator.json

To find out your pubkey, use the command (Save your Pubkey)

titand comet show-validator

Output Example:

The output will be similar to this (with a different key):

{"@type":"/cosmos.crypto.ed25519.PubKey","key":"+vMHVm134I+Rh4kNqLG/YwvQqDy+YqcZqWtgp7ABUop0="}

Open a validator.json file

nano $HOME/.titan/config/validator.json

Paste this into the open validator.json file, pre-replacing all values ​​that start with $ (you can do it in any convenient editor, not directly in nano mode)

{
  "pubkey": {
    "@type": "/cosmos.crypto.ed25519.PubKey",
    "key": "+vMHVm134I+Rh4kNqLG/YwvQqDy+YqcZqWtgp7ABUop0="
  },
  "amount": "1000000uttnt",
  "moniker": "Oliver",
  "identity": "", 
  "website": "", 
  "security": "", 
  "details": "Trusted Blockchain validator", 
  "commission-rate": "0.05",
  "commission-max-rate": "0.2",
  "commission-max-change-rate": "0.2",
  "min-self-delegation": "1"
}

◽ Replace the following values with your own: WALLET - usually it's 'wallet', or your wallet's name. MONIKER - any convenient name for your validator, displayed in the explorer. IDENTITY - validator's avatar, displayed in the explorer. Create a KeyBase ID following the instructions or leave it empty, and it will default to a standard one. DETAILS - details about your validator, also displayed in the explorer.

WEBSITE - your website/github/twitter, etc., if you don't want to specify anything - leave it blank

Replace all necessary values indicated above with the $ sign to successfully create your validator. ◽ Example: 

{
  "pubkey": {
    "@type": "/cosmos.crypto.ed25519.PubKey",
    "key": "+vMHVm134I+Rh4kNqLG/YwvQqDy+YqcZqWtgp7ABUop0="
  },
  "amount": "1000000uttnt",
  "moniker": "Oliver",
  "identity": "", #if you have your identifier, replace it, or leave it blank
  "website": "", #if you have your website, replace it, or leave it blank
  "security": "", 
  "details": "Trusted Blockchain validator", 
  "commission-rate": "0.05",
  "commission-max-rate": "0.2",
  "commission-max-change-rate": "0.2",
  "min-self-delegation": "1"
}

After entering and changing all values, save the file with the key combination Ctrl + X and press Enter

After creating the validator.json and entering all the necessary information, as well as provided that there are tokens in the wallet, run the create command:

titand tx staking create-validator $HOME/.titan/config/validator.json \
--chain-id titan-test-3 \
--gas-adjustment="1.5" \
--fees 500uttnt \
--from wallet

After entering the command, you will receive hash transactions, check the status in the explorer if the status is successful - you have created a validator. You can find your validator here: explorer In the Active / Inactive lists.

📌Step 4: Backup

If you have successfully created a validator, be sure to save your validator.

Show priv_validator_key.json


cat $HOME/.titan/config/priv_validator_key.json

SAVE YOUR PRIVATE KEY AFTER ENTERING THE COMMAND The priv_validator_key.json is the key with which you can always restore the operation of your validator, so keep it and in case of reinstallation/transfer of the validator to another server - transfer it too.

Also remember, if you are a validator with a sufficient number of delegated tokens and you are in an active set, signing blocks, always save priv_validator_state.json - this file contains information about the signed blocks of your validators, and in case of restoring the validator after reinstallation or on another server , this file won't give you the old blocks again, otherwise you'll end up in jail with no way out 💡 Hint:

  • View private key: cat $HOME/.titan/config/priv_validator_key.json

  • View private state: cat $HOME/.titan/config/priv_validator_key.json

  • Private key directory: $HOME/.titan/config/priv_validator_key.json

  • Validator state directory: $HOME/.titan/data/priv_validator_state.json

All the useful commands to manage your node in the section - Useful commands

PreviousTitan NetworkNext🆙 Upgrade

Last updated