Skip to main content
Version: release (v0.77)

Upgrade to 0.77

This guide describes the steps to upgrade from v0.76.8 to v0.77.6 using the protocol upgrade mechanism. See the changelog for v0.77.6 ↗ for information about breaking changes and new features.

Assumptions for the guide​

The instructions below are written for Debian-like Linux operating systems.

The guide assumes you are using systemd commands (systemctl and journalctl) to control binaries. If you are using something different, your system's commands may vary.

This guide is specifically intended for those who are already running a validator node with version v0.76.8.

Study the changes between versions​

Before upgrading your node software, review the changelog for v0.77.6 ↗ for a list of breaking API changes compared to the previously released version.

Required changes​

There are no extra required changes for this release.

Before you upgrade​

Please read the changelogs to see all the changes. Below you can find a list of the changes you must perform before the upgrade to v0.77.6 ↗.

When should I upgrade config?​

You can update the config any time before the upgrade block happens.

We recommend you do it in the following way:

  1. Make a copy of the original config.
  2. Update the config in the copied files.
  3. A few hours before the upgrade, replace the original config with updated one.
Back up your original config files

Make sure you have a backup for the original config in case you need them in the future.

We do not recommend you do it too early in case you have to restart your node with the current version for some reason, for example if your node fails or your server restarts, etc.

Config changes​

The default locations for configuration files:

  • data-node: YOUR_VEGA_HOME/config/data-node/config.toml
  • vega-core: YOUR_VEGA_HOME/config/node/config.toml
  • comet BFT: YOUR_COMET_BFT_HOME/config/config.toml

We recommend checking all of the changes on your own. Follow the below instructions to do it, and read through every description to understand the changes:

  1. Download vega v0.77.6
  2. Generate config files within the temp home directory
  • vega config
  • comet BFT config
  • data-node config
  1. Compare the new generated file in the temp location and the old file to see the differences.

There is a new parameter max_request_batch_size, set to a default of 10, the value of which does not need to be updated.

Upgrade your node​

To upgrade the network follow the protocol upgrade documentation.

Common issues​

If you come across any problems, please refer to the frequent issues solutions before requesting help.