Thursday, August 1st, 2024
Following This indicates that the upgrade procedure should be performed on block number 80319200
The Injective Canonical Chain will undergo a scheduled enhancement upgrade on Thursday, August 1st, 2024, 14:00 UTC.
The following is a short summary of the upgrade steps:
Vote and wait till the node panics at block height 80319200.
Backing up configs, data, and keys used for running the Injective Canonical Chain.
Install the
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 .
The network upgrade can take the following potential pathways:
Happy path Validators successfully upgrade chain without purging the blockchain history, and all validators are up within 5-10 minutes of the upgrade.
Not-so-happy path Validators have trouble upgrading to the latest Canonical chain.
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.
You must remove the wasm cache before upgrading to the new version (rm -rf .injectived/wasm/wasm/cache/).
Verify you are currently running the correct version (c1a64b7ed) of injectived:
Make a backup of your .injectived directory
Download and install the injective-chain v1.13.0 release
Verify you are currently running the correct version (c1a64b7ed) of injectived after downloading the v1.13.0 release:
Start injectived
Verify you are currently running the correct version (ead1119) of peggo after downloading the v1.13.0 release:
Start peggo
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 , and validators will need to resume running the chain without any updates or changes.
In the event that the upgrade does not succeed, validators and operators must restore the snapshot and downgrade back to and continue the chain until next upgrade announcement.
