Skip to main content
Follow the operator portal for upgrade announcements.

For Validators

Consult the Validator Troubleshooting Guide for upgrade and recovery procedures, including validator signing state precautions.

Summary

The Injective Chain upgrade to v1.21.0 is targeted for November 24, 2026, at block 193,145,000, as described in proposal 717. Follow the block height countdown for the latest estimate.
NetworkMainnet, injective-1
Upgrade planv1.21.0
Target halt height193,145,000
Target dateNovember 24, 2026. Block countdown
Mainnet releasev1.21.0-1794954936
Binary source commita13b8b7
The published binaries were built with Go 1.27.4. The following is a short summary of the upgrade steps:
  1. Wait for the node to halt at block height 193,145,000.
  2. Stop the process and back up configs, data and validator signing state.
  3. Remove the Wasm cache after the backup.
  4. Install the v1.21.0 binaries and bundled runtime library.
  5. Verify the binary versions, libwasmvm checksum and loaded library version 2.2.11-rc.4.
  6. Restart the node with the new binary version.

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 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 release v1.20.4-safeharbor.5 and continue this earlier chain until the next upgrade announcement. Official snapshots taken before the upgrade will be provided on the Chain Snapshots page so operators can roll back and restore from a snapshot in a worst-case recovery scenario. If an operator makes a mistake during the upgrade or encounters errors, follow the Validator Troubleshooting Guide, including its snapshot recovery and validator signing-state precautions.

Upgrade Procedure

Notes for Validators

Wait for the chain to halt at 193,145,000 before replacing the active binary. Stop injectived fully before backing up data and validator signing state. After the backup and before starting the new binary, remove the Wasm cache from the actual node home. For the default home:

Steps

  1. Verify you are running v1.20.4-safeharbor.5 before the upgrade:
    Expected version:
  2. Wait for the node to halt at 193,145,000, then confirm injectived has stopped. Make a backup of your .injectived directory:
    Preserve data/priv_validator_state.json after shutdown. Remote signer operators must preserve their signer’s state.
  3. Download the Linux amd64 archive from the official release, verify the published archive checksum, extract it, and install the release binaries and bundled runtime library:
  4. Validate the installed libwasmvm library:
    Expected output:
    An incorrect runtime library checksum can lead to consensus issues. Resolve any mismatch before restarting.
    Validate that the installed binary loads the correct library version:
    Expected output:
    For the Docker image, check the bundled library version with:
    Expected output:
  5. Verify the installed injectived reports v1.21.0 and the build commit published in the release notes:
    Expected output:
  6. Start injectived:
  7. If you run peggo, verify its version against the release notes:
    Expected output:
  8. Start peggo if you operate the bridge orchestrator:
Confirm the node advances past the upgrade height, catches up to the network, and participates normally. Repeat the upgrade for sentries, RPC nodes, and other node infrastructure.

With Cosmovisor

Before the halt, stage the verified binary under the exact upgrade plan name:
Verify the staged version and executable permissions:
Keep the active binary unchanged until the halt. Ensure a backup is taken after the old process stops and before the upgraded process starts. At the upgrade height, Cosmovisor selects the staged binary for v1.21.0. Verify the active version and confirm synchronization and validator participation after restart.
Last modified on November 19, 2026