installation


description: Setting up your validator node has never been so easy. Get your validator running in minutes by following step by step instructions.

Installation

Warden Protocol
Warden Protocol

Network name: Warden Protocol | Chain ID: chiado_10010-1 | Latest version: v0.5.4 | Custom Port: 273

Setup validator name

Replace YOUR_MONIKER_GOES_HERE with your validator name

MONIKER="YOUR_MONIKER_GOES_HERE"

Install dependencies

Update system and install build tools

sudo apt -q update
sudo apt -qy install curl git jq zst build-essential
sudo apt -qy upgrade

Install Go

sudo rm -rf /usr/local/go
curl -Ls https://go.dev/dl/go1.19.8.linux-amd64.tar.gz | sudo tar -xzf - -C /usr/local
eval $(echo 'export PATH=$PATH:/usr/local/go/bin' | sudo tee /etc/profile.d/golang.sh)
eval $(echo 'export PATH=$PATH:$HOME/go/bin' | tee -a $HOME/.profile)

Download and build binaries

# Clone project repository
cd $HOME
rm -rf warden
git clone https://github.com/warden-protocol/wardenprotocol warden
cd warden
git checkout v0.5.4

# Build binaries
make install

# Prepare binaries for Cosmovisor
mkdir -p .warden/cosmovisor/genesis/bin
mv ~/go/bin/wardend .warden/cosmovisor/genesis/bin/
rm -rf build

Install Cosmovisor and create a service

# Download and install Cosmovisor
go install cosmossdk.io/tools/cosmovisor/cmd/cosmovisor@v1.4.0

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

[Service]
User=$USER
ExecStart=$(which cosmovisor) run start
WorkingDirectory=.warden
Restart=always
RestartSec=5
LimitNOFILE=65535
Environment="DAEMON_HOME=.warden"
Environment="DAEMON_NAME=wardend"
Environment="DAEMON_ALLOW_DOWNLOAD_BINARIES=false"
Environment="DAEMON_RESTART_AFTER_UPGRADE=true"
Environment="UNSAFE_SKIP_BACKUP=true"
Environment="PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:.warden/cosmovisor/current/bin"

[Install]
WantedBy=multi-user.target
EOF
sudo systemctl daemon-reload
sudo systemctl enable wardend

Initialize the node

# Set node configuration
wardend config chain-id chiado_10010-1
wardend config node tcp://localhost:27357

# Initialize the node
wardend init $MONIKER --chain-id chiado_10010-1

# Download genesis and addrbook
curl -Ls https://raw.githubusercontent.com/warden-protocol/networks/main/testnets/chiado/genesis.json > .warden/config/genesis.json
curl -Ls https://snapshots.lavenderfive.com/testnet-addrbooks/warden/addrbook.json > .warden/config/addrbook.json

# Add seeds
seeds="2d2c7af1c2d28408f437aef3d034087f40b85401@52.51.132.79:26656,3f472746f46493309650e5a033076689996c8881@warden-testnet.rpc.kjnodes.com:17859"
sed -i -e "s|^seeds *=.*|seeds = \"$seeds\"|" .warden/config/config.toml

# Set minimum gas price
sed -i -e "s|^minimum-gas-prices *=.*|minimum-gas-prices = \"0.025uward\"|" .warden/config/app.toml

# Set pruning
sed -i \
  -e 's|^pruning *=.*|pruning = "custom"|' \
  -e 's|^pruning-keep-recent *=.*|pruning-keep-recent = "100"|' \
  -e 's|^pruning-keep-every *=.*|pruning-keep-every = "0"|' \
  -e 's|^pruning-interval *=.*|pruning-interval = "19"|' \
  .warden/config/app.toml

# Set custom ports
sed -i -e "s%^proxy_app = \"tcp://127.0.0.1:26658\"%proxy_app = \"tcp://127.0.0.1:27358\"%; s%^laddr = \"tcp://127.0.0.1:26657\"%laddr = \"tcp://127.0.0.1:27357\"%; s%^pprof_laddr = \"localhost:6060\"%pprof_laddr = \"localhost:27360\"%; s%^laddr = \"tcp://0.0.0.0:26656\"%laddr = \"tcp://0.0.0.0:27356\"%; s%^prometheus_listen_addr = \":26660\"%prometheus_listen_addr = \":27366\"%" .warden/config/config.toml
sed -i -e "s%^address = \"tcp://0.0.0.0:1317\"%address = \"tcp://0.0.0.0:27317\"%; s%^address = \":8080\"%address = \":27380\"%; s%^address = \"0.0.0.0:9090\"%address = \"0.0.0.0:27390\"%; s%^address = \"0.0.0.0:9091\"%address = \"0.0.0.0:27391\"%; s%:8545%:27345%; s%:8546%:27346%; s%:6065%:27365%" .warden/config/app.toml

Start service and check the logs

sudo systemctl start wardend && sudo journalctl -u wardend -f --no-hostname -o cat

Sync

To catch up quickly, you can either use a snapshot or state sync

Last updated