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

Network name: dydx | Chain ID: dydx-testnet-4 | Latest version: protocol/v6.0.3-rc0 | Custom Port: 266

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 lz4 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 dydx
git clone https://github.com/dydxprotocol/v4-chain/ dydx
cd dydx
git checkout protocol/v6.0.3-rc0

# Build binaries
make install

# Prepare binaries for Cosmovisor
mkdir -p .dydxprotocol/cosmovisor/genesis/bin
mv ~/go/bin/dydxprotocold .dydxprotocol/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/dydxprotocold.service > /dev/null << EOF
[Unit]
Description=osmosis node service
After=network-online.target

[Service]
User=$USER
ExecStart=$(which cosmovisor) run start
WorkingDirectory=.dydxprotocol
Restart=always
RestartSec=5
LimitNOFILE=65535
Environment="DAEMON_HOME=.dydxprotocol"
Environment="DAEMON_NAME=dydxprotocold"
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:.dydxprotocol/cosmovisor/current/bin"

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

Initialize the node

# Set node configuration
dydxprotocold config chain-id dydx-testnet-4
dydxprotocold config node tcp://localhost:26657

# Initialize the node
dydxprotocold init $MONIKER --chain-id dydx-testnet-4

# Download genesis and addrbook
curl -Ls https://raw.githubusercontent.com/dydxprotocol/v4-testnets/main/dydx-testnet-4/genesis.json > .dydxprotocol/config/genesis.json
curl -Ls https://snapshots.lavenderfive.com/testnet-addrbooks/dydx/addrbook.json > .dydxprotocol/config/addrbook.json

# Add seeds
seeds="87ee8de5f0f82af6ee6740a30f8844bbe6434413@seed.dydx-testnet.cros-nest.com:26656,20e1000e88125698264454a884812746c2eb4807@testnet-seeds.lavenderfive.com:23856"
sed -i -e "s|^seeds *=.*|seeds = \"$seeds\"|" .dydxprotocol/config/config.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"|' \
  .dydxprotocol/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:26658\"%; s%^laddr = \"tcp://127.0.0.1:26657\"%laddr = \"tcp://127.0.0.1:26657\"%; s%^pprof_laddr = \"localhost:6060\"%pprof_laddr = \"localhost:26660\"%; s%^laddr = \"tcp://0.0.0.0:26656\"%laddr = \"tcp://0.0.0.0:26656\"%; s%^prometheus_listen_addr = \":26660\"%prometheus_listen_addr = \":26666\"%" .dydxprotocol/config/config.toml
sed -i -e "s%^address = \"tcp://0.0.0.0:1317\"%address = \"tcp://0.0.0.0:26617\"%; s%^address = \":8080\"%address = \":26680\"%; s%^address = \"0.0.0.0:9090\"%address = \"0.0.0.0:26690\"%; s%^address = \"0.0.0.0:9091\"%address = \"0.0.0.0:26691\"%; s%:8545%:26645%; s%:8546%:26646%; s%:6065%:26665%" .dydxprotocol/config/app.toml

Start service and check the logs

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

Sync

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

Last updated