SiteExplorerGitHubTwitterMedium

⚙️ Installation

🛠️ Hardware Requirements

Additional requirements

⏱️ 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/main/nibiru/install-nibiru.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 orai
git clone https://github.com/oraichain/orai
cd orai
git checkout v0.42.4
make install

# Initialize the node
cd $HOME
oraid init "$MONIKER" --chain-id Oraichain

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

# Set seeds
sed -E -i 's/seeds = \".*\"/seeds = \"4d0f2d042405abbcac5193206642e1456fe89963@3.134.19.98:26656,24631e98a167492fd4c92c582cee5fd6fcd8ad59@162.55.253.58:26656,bf083c57ed53a53ccd31dc160d69063c73b340e9@3.17.175.62:26656,35c1f999d67de56736b412a1325370a8e2fdb34a@5.189.169.99:26656,5ad3b29bf56b9ba95c67f282aa281b6f0903e921@64.225.53.108:26656,d091cabe3584cb32043cc0c9199b0c7a5b68ddcb@seed.orai.synergynodes.com:26656\"/' $HOME/.oraid/config/config.toml

# Set minimum gas price
sed -i -e "s|^minimum-gas-prices *=.*|minimum-gas-prices = \"0.025orai\"|" $HOME/.oraid/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/.oraid/config/app.toml

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

# Create a service
sudo tee /etc/systemd/system/oraid.service > /dev/null <<EOF
[Unit]
Description=Orai Network Node
After=network.target
[Service]
Type=simple
User=$USER
ExecStart=$(which oraid) start --home $HOME/.oraid
Restart=on-failure
RestartSec=10
LimitNOFILE=65535
[Install]
WantedBy=multi-user.target
EOF

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

📌Step 3: Node Health Check

Follow the commands to check if your node is working properly

  1. Check version

oraid version

  1. View sync status

while true; do 
  local_height=$(oraid status | jq -r .sync_info.latest_block_height)
  network_height=$(curl -s https://rpc.oraichain-mainnet.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 oraid.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.

📝 Create Validator

📌Step 1: Create wallet

oraid 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).

📌Step 2: Request tokens to your wallet address

You need to send at least 1 ORAI token to your orai address, you can buy it on any of the offered platforms here: Coinmarketcap Then send it to your wallet and check the balance.

oraid q bank balances $(oraid 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

oraid tx staking create-validator \
  --amount 100000orai \
  --commission-max-change-rate "0.01" \
  --commission-max-rate "0.2" \
  --commission-rate "0.05" \
  --min-self-delegation "1" \
  --pubkey=$(oraid tendermint show-validator) \
  --moniker "" \ #Validator name, displayed in explorers. 
  --website "" \ #Your website is available, or leave the field blank
  --identity "" \ #Use your KeyBase ID. If you don't have one, leave it empty.
  --details "" \ #Any details about your validator.
  --security-contact="" \ #Your mail
  --chain-id Oraichain \
  --from wallet #Wallet name, as specified during creation, or typically '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/.0gchain/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/.oraid/config/priv_validator_key.json

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

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

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

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

PreviousOraichainNext🆙 Upgrade

Last updated