Automated Updates
We highly recommend validators use Cosmovisor to run their nodes. This will make low-downtime upgrades smoother, as validators don't have to manually upgrade binaries during the upgrade. Instead, users can pre-install new binaries and Cosmovisor will automatically update them based on on-chain Software Upgrade proposals.
cosmovisor
is a small process manager for Cosmos SDK application binaries that monitors the governance module for incoming chain upgrade proposals. If it sees a proposal that gets approved, cosmovisor can automatically download the new binary, stop the current binary, switch from the old binary to the new one, and finally restart the node with the new binary.
Prerequisites
Install Cosmovisor
1. Setup Cosmovisor
Set up the Cosmovisor environment variables. We recommend setting these in your .profile
so it is automatically set in every session.
After this, you must make the necessary folders for cosmosvisor
in your DAEMON_HOME
directory (~/.egaxd
) and copy over the current binary.
To check that you did this correctly, ensure your versions of cosmovisor
and egaxd
are the same:
2. Download the Egaxd release
Manual Download
Cosmovisor will continually poll the $DAEMON_HOME/data/upgrade-info.json
for new upgrade instructions. When an upgrade is released, node operators need to:
Download (NOT INSTALL) the binary for the new release
Place it under
$DAEMON_HOME/cosmovisor/upgrades/<name>/bin
, where<name>
is the URI-encoded name of the upgrade as specified in the Software Upgrade Plan.
Example: for a Plan
with name v3.0.0
with the following upgrade-info.json
:
Your cosmovisor/
directory should look like this:
Automatic Download
DANGER
NOTE: Auto-download doesn't verify in advance if a binary is available. If there will be any issue with downloading a binary, cosmovisor
will stop and won't restart and the chain (which could lead it to a halt).
It is possible to have Cosmovisor automatically download the new binary. Validators can use the automatic download option to prevent unnecessary downtime during the upgrade process. This option will automatically restart the chain with the upgrade binary once the chain has halted at the proposed upgrade-height
. The major benefit of this option is that validators can prepare the upgrade binary in advance and then relax at the time of the upgrade.
To set the auto-download use set the following environment variable:
3. Start your node
Now that everything is set up and ready to go, you can start your node.
You will need some way to keep the process always running. If you're on linux, you can do this by creating a service.
Then update and start the node
You can check the status with:
Last updated