From 616d2cfee5ed750b0d40e1a3fe215ca8f8a08490 Mon Sep 17 00:00:00 2001 From: Nikola Marcetic Date: Wed, 6 Apr 2022 23:36:26 +0200 Subject: [PATCH] Update binary versions Signed-off-by: Nikola Marcetic --- docs/migration/injective-canonical-chain-5.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/migration/injective-canonical-chain-5.md b/docs/migration/injective-canonical-chain-5.md index 61e7f4e..d86a833 100644 --- a/docs/migration/injective-canonical-chain-5.md +++ b/docs/migration/injective-canonical-chain-5.md @@ -1,7 +1,7 @@ # Injective Chain Upgrade Instructions The following document describes the necessary steps involved that validators and full node operators -must take in order to upgrade the Injective Chain from 10004-rc1 [patch version 10004-rc1-1645352045](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.4.0-1645352045) to 10005-rc1. The upgrade will take place via an on-chain software upgrade proposal passed by the Injective Chain governance. +must take in order to upgrade the Injective Chain from 10004-rc1 [patch version 10004-rc1-1645352045](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.4.0-1645352045) to [10005-rc1](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.5.0-1649280277). The upgrade will take place via an on-chain software upgrade proposal passed by the Injective Chain governance. If passed, this proposal would commit the Injective Mainnet to halting the 10004-rc1 `injectived` application binary at approximately 14:00 UTC on April 11th 2022 and starting the application binary for the 10005-rc1 `injectived` application binary for the upgraded Injective Chain. In case of a failed migration via the upgrade module, the Injective Labs team will post an official `injective-canonical-chain-5` genesis file, but it is recommended that validators should do try to export the genesis on their own node to verify the resulting genesis file. @@ -22,7 +22,7 @@ The following is a short summary of the upgrade steps: 1. Vote and wait until the node panics at block height 9614200. 2. Backing up configs, data, and keys used for running the Injective Chain. -3. Install the [Injective Chain 10005-rc1 release](release_url) +3. Install the [Injective Chain 10005-rc1 release](https://github.com/InjectiveLabs/injective-chain-releases/releases/tag/v1.5.0-1649280277) 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](https://discord.gg/injective). @@ -87,11 +87,11 @@ In the event that the upgrade does not succeed, validators and operators must re sudo mv injectived /usr/bin ``` -4. Verify you are currently running the correct new version (``) of `injectived` after downloading the 10005-rc1 release: +4. Verify you are currently running the correct new version (`568ce23`) of `injectived` after downloading the 10005-rc1 release: ```bash $ injectived version - Version dev () - Compiled at using Go go1.17.6 (amd64) + Version dev (568ce23) + Compiled at 20220406-2125 using Go go1.18 (amd64) ``` 5. Coordinate to restart your injectived with other validators