Republic AI Node Upgrade Guide

Upgrade Overview

This guide outlines the process for upgrading your Republic AI node to version v0.3.0. Before proceeding, ensure you have backed up your validator state and configuration files.

Upgrade Methods

Choose the method that corresponds to your current node infrastructure.

Option 1: Upgrade via Cosmovisor (Recommended)

Cosmovisor handles the binary switchover automatically. You simply need to place the new binary in the correct upgrade directory.

# Navigate to home and download the new binary
cd $HOME
wget https://github.com/RepublicAI/networks/releases/download/v0.3.0/republicd-linux-amd64 -O republicd
chmod +x republicd

# Create the upgrade directory for version v0.3.0
mkdir -p $HOME/.republic/cosmovisor/upgrades/v0.3.0/bin

# Move the binary to the upgrade folder
mv republicd $HOME/.republic/cosmovisor/upgrades/v0.3.0/bin/

# Restart the service and monitor logs
sudo systemctl restart republicd && sudo journalctl -u republicd -f

Option 2: Manual Upgrade (Non-Cosmovisor)

If you are running a standard systemd service, you must manually replace the binary in your executable path and restart the service.

# Download the new binary
wget https://github.com/RepublicAI/networks/releases/download/v0.3.0/republicd-linux-amd64 -O republicd
chmod +x republicd

# Replace the existing binary in your go path
mv republicd ~/go/bin/

# Restart the service and monitor logs
sudo systemctl restart republicd && sudo journalctl -u republicd -f

Verification

After the upgrade, verify that your node is running the correct version and is successfully catching up with the network.

Check Version

republicd version

*Expected Output: 0.3.0*

Check Sync Status

republicd status 2>&1 | jq .SyncInfo

Common Failure Notes

Wrong Directory: Ensure DAEMON_HOME in your service file matches $HOME/.republic.
Permission Denied: If republicd fails to execute, re-run chmod +x on the binary.
Panic on Startup: Ensure the upgrade-info.json (if generated by the chain) matches the version tag v0.3.0.