Cosmovisor Setup Guide for the Injective Network

Note: These instructions assume you already have an existing chain binary (e.g., injectived) and a working Go environment if you choose to install Cosmovisor from source. Adjust the names and paths as needed for your specific setup.

​

Table of Contents

1. Installation
   • Installing via Go
2. Environment Variables
3. Directory Structure
4. Running Cosmovisor
5. Handling Chain Upgrades
6. Running Cosmovisor as a Systemd Service

​

Installation

​

Installing via Go

go install cosmossdk.io/tools/cosmovisor/cmd/cosmovisor@v1.5.0

Tip: Ensure that your Go binary installation path (commonly $GOPATH/bin or $HOME/go/bin) is added to your system’s PATH. You can verify the installation by running:

which cosmovisor

​

Environment Variables

• DAEMON_NAME
  The name of your chain’s binary (e.g., injectived).
• DAEMON_HOME
  The home directory for your node (e.g., ~/.injectived).

export DAEMON_NAME=injectived
export DAEMON_HOME=~/.injectived

​

Directory Structure

1. Create the Genesis Directory This directory holds the initial (genesis) binary.
   mkdir -p $DAEMON_HOME/cosmovisor/genesis/bin
   
2. Copy Your Current Binary Place your current chain binary (e.g., injectived) into the genesis folder. Make sure the file name matches the DAEMON_NAME value (see next section).
   cp $(which injectived) $DAEMON_HOME/cosmovisor/genesis/bin/injectived
   

​

Running Cosmovisor

cosmovisor run start

• Look for the binary in $DAEMON_HOME/cosmovisor/genesis/bin (or the appropriate upgrade folder).
• Start your node using that binary.
• Monitor for any on-chain upgrade signals and automatically switch binaries when needed.

​

Handling Chain Upgrades

1. Create an Upgrade Directory Use the upgrade name provided on-chain (e.g., v1.14.0):
   mkdir -p $DAEMON_HOME/cosmovisor/upgrades/<upgrade_name>/bin
   
2. Place the New Binary Compile or download the new binary, then copy it into the upgrade directory. Ensure the binary name matches DAEMON_NAME.
   cp /path/to/new/injectived $DAEMON_HOME/cosmovisor/upgrades/<upgrade_name>/bin
   cp /path/to/new/libwasmvm.x86_64.so $DAEMON_HOME/cosmovisor/upgrades/<upgrade_name>/bin
   

TIP: If you have downloaded the injectived binary package from GitHub, we copy libwasmvm.x86_64.so to the upgrade bin directory. An environment variable will be later added to the systemd service to add this directory to LD_LIBRARY_PATH.

3. Upgrade Process When the upgrade height is reached, Cosmovisor will detect the scheduled upgrade and automatically switch to the binary located in the corresponding upgrade folder.

​

Running Cosmovisor as a Systemd Service

1. Create the Service File Create a file (e.g., /etc/systemd/system/injectived.service) with the following content. Adjust the paths and <your_username> accordingly:
   [Unit]
   Description=Injective Daemon managed by Cosmovisor
   After=network-online.target
   
   [Service]
   User=<your_username>
   ExecStart=/home/<your_username>/go/bin/cosmovisor run start
   Restart=always
   RestartSec=3
   Environment="DAEMON_NAME=injectived"
   Environment="DAEMON_HOME=/home/<your_username>/.injectived"
   Environment="PATH=/usr/local/bin:/home/<your_username>/go/bin:$PATH"
   Environment="DAEMON_ALLOW_DOWNLOAD_BINARIES=false"
   Environment="DAEMON_RESTART_AFTER_UPGRADE=true"
   Environment="UNSAFE_SKIP_BACKUP=true"
   Environment="LD_LIBRARY_PATH=/home/<your_username>/.injectived/cosmovisor/current/bin"
   
   [Install]
   WantedBy=multi-user.target
   
2. Enable and Start the Service
   sudo systemctl daemon-reload
   sudo systemctl enable injectived.service
   sudo systemctl start injectived.service
   
3. Check Logs Verify that your service is running smoothly:
   journalctl -u injectived.service -f