> ## Documentation Index
> Fetch the complete documentation index at: https://injectivelabs-docs-tokenization-section.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Upgrade to v1.13.2

Tuesday, August 20th, 2024

Following [proposal 424](https://injhub.com/proposal/424/) This indicates that the upgrade procedure should be performed on block number **82830000**

* [Summary](#summary)
* [Recovery](#recovery)
* [Upgrade Procedure](#upgrade-procedure)
* [Notes for Validator Operators](#notes-for-validators)

## Summary

The Injective Canonical Chain will undergo a scheduled enhancement upgrade on **Thursday, August 20th, 2024, 15:00 UTC**.

The following is a short summary of the upgrade steps:

1. Vote and wait till the node panics at block height **82830000**.
2. Backing up configs, data, and keys used for running the Injective Canonical Chain.
3. Install the [v1.13.2-1723753267](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.13.2-1723753267)
4. Start your node with the new injectived binary to fulfill the upgrade.

Upgrade coordination and support for validators will be available on the `#validators` private channel of the [Injective Discord](https://discord.gg/injective).

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 5-10 minutes of the upgrade.
2. **Not-so-happy path**\
   Validators have trouble upgrading to the latest Canonical chain.
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](https://discord.gg/injective), and validators will need to resume running the chain without any updates or changes.

## 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 v1.13.2 release](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.13.2-1723753267) and continue the chain until next upgrade announcement.

### Upgrade Procedure

## Notes for Validators

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 (`af924ca9`) of `injectived`:

   ```bash theme={null}
      injectived version
      Version dev (af924ca9)
      Compiled at 20240728-0905 using Go go1.22.5 (amd64)
   ```
2. Make a backup of your `.injectived` directory

   ```bash theme={null}
   cp ~/.injectived ./injectived-backup
   ```

   3. Download and install the injective-chain `v1.13.2 release`

   ```bash theme={null}
   wget https://github.com/InjectiveLabs/injective-chain-releases/releases/download/v1.13.2-1723753267/linux-amd64.zip
   unzip linux-amd64.zip
   sudo mv injectived peggo /usr/bin
   sudo mv libwasmvm.x86_64.so /usr/lib
   ```
3. Verify you are currently running the correct version (`6f57bf03`) of `injectived` after downloading the v1.13.2 release:

   ```bash theme={null}
   injectived version
   Version dev (6f57bf03)
   Compiled at 20240815-2021 using Go go1.22.5 (amd64)
   ```
4. Start injectived

   ```bash theme={null}
   injectived start
   ```
5. Verify you are currently running the correct version (`ead1119`) of `peggo` after downloading the v1.13.2 release:

   ```bash theme={null}
    peggo version
    Version dev (ead1119)
    Compiled at 20240815-2021 using Go go1.22.5 (amd64)
   ```
6. Start peggo

   ```bash theme={null}
   peggo orchestrator
   ```