Upgrade to v1.11

Thursday, June 1st, 2023

Following proposal 231 This indicates that the upgrade procedure should be performed on block number 34775000

• Summary

• Risks

• Recovery

• Upgrade Procedure

• Notes for Validator Operators

• Notes for Service Providers

Summary

The Injective Canonical Chain will undergo a scheduled enhancement upgrade on Thursday, June 1st, 2023, 14:00 UTC.

The following is a short summary of the upgrade steps:

1. Vote and wait till the node panics at block height 34775000.

2. Backing up configs, data, and keys used for running the Injective Canonical Chain.

3. Install the v1.11-1685225746

4. Start your node with the new injectived binary to fulfill the upgrade.

Upgrade coordination and support for validators will be available on the #mainnet-validators private channel of the Injective Discord.

The network upgrade can take the following potential pathways:

1. Happy path Validators successfully upgrade chain without purging the blockchain history, and all validators are up within 1-2 hours of the scheduled upgrade.

2. Not-so-happy path Validators have trouble upgrading to the latest Canonical chain. This could be some consensus breaking changes not covered in upgrade handler, or compatibility issue of the migrated state with new injectived binary, but validators can at least export the genesis.

3. Abort path In the rare event that the team becomes aware of unnoticed critical issues, the Injective team will attempt to patch all the breaking states and provide another official binary within 36 hours. If the chain is not successfully resumed within 36 hours, the upgrade will be announced as aborted on the #mainnet-validators channel of Discord, and validators will need to resume running the chain without any updates or changes. A new governance proposal for the upgrade will need to be issued and voted on by the community for the next upgrade.

Risks

As a validator, performing the upgrade procedure on your consensus nodes carries a heightened risk of double-signing and being slashed. The most important piece of this procedure is verifying your software version and genesis file hash before starting your validator and signing.

The riskiest thing a validator can do is discover that they made a mistake and repeat the upgrade procedure again during the network startup. If you discover a mistake in the process, the best thing to do is wait for the network to start before correcting it. If the network is halted and you have started with a different genesis file than the expected one, seek advice from an Injective developer before resetting your validator.

Recovery

Prior to exporting chain state, validators are encouraged to take a full data snapshot at the export height before proceeding. Snapshotting depends heavily on infrastructure, but generally this can be done by backing up the .injectived directory.

It is critically important to backup the .injectived/data/priv_validator_state.json file after stopping your injectived process. This file is updated every block as your validator participates in a consensus rounds. It is a critical file needed to prevent double-signing, in case the upgrade fails and the previous chain needs to be restarted.

In the event that the upgrade does not succeed, validators and operators must restore the snapshot and downgrade back to Injective Chain 10010 release and continue the chain until next upgrade announcement.

Upgrade Procedure

Notes for Validators

Validator operators should configure the timeout_commit in config.toml to 300ms. You must remove the wasm cache before upgrading to the new version (rm -rf .injectived/wasm/wasm/cache/).

1. Verify you are currently running the correct version (b578d018c8) of injectived:

      injectived version
      Version dev (b578d018c8)
      Compiled at 20230118-1421 using Go go1.18.3 (amd64)

2. After the chain has halted, make a backup of your .injectived directory

   cp ~/.injectived ./injectived-backup

   NOTE: It is recommended for validators and operators to take a full data snapshot at the export height before proceeding in case the upgrade does not go as planned or if not enough voting power comes online in a sufficient and agreed upon amount of time. In such a case, the chain will fallback to continue operating the Chain. See Recovery for details on how to proceed.

3. Download and install the injective-chain 10011 release

   wget https://github.com/InjectiveLabs/injective-chain-releases/releases/download/v1.11-1685225746/linux-amd64.zip
   unzip linux-amd64.zip
   sudo mv injectived peggo /usr/bin
   sudo mv libwasmvm.x86_64.so /usr/lib

4. Verify you are currently running the correct version (f77eb5cfd7) of injectived after downloading the 10009 release:

   injectived version
   Version v1.11 (f77eb5cfd7)
   Compiled at 20230527-2215 using Go go1.19.3 (amd64)

5. Coordinate to restart your injectived with other validators

   injectived start

   The binary will perform the upgrade automatically and continue the next consensus round if everything goes well.

6. Verify you are currently running the correct version (5868c94) of peggo after downloading the 10009 release:

  peggo version
  Version dev (5868c94)
  Compiled at 20230527-2216 using Go go1.19.3 (amd64)

1. Start peggo

   peggo start

Notes for DEX relayer providers

Relayer upgrade will be available after the chain is successfully upgraded, as it relies on several other components that work with injectived.