Hey Cosmos validators–let’s take another crack at our first major upgrade!
This proposal is intended to signal acceptance/rejection of the precise software release that will contain the changes to be included in the Cosmos Hub 3 upgrade. A high level overview of these changes was successfully approved by the voters signalling via Cosmos Hub 3 Upgrade Proposal A.
We are proposing to use this code https://github.com/cosmos/gaia/releases/tag/v2.0.1 to upgrade the Cosmos Hub.
We are proposing to export the ledger’s state at Block Height [TBD], which we expect to occur on [MONTH DATE], 2019 at or around [TIME] UTC. Please note that there will likely be a variance from this target time, due to changes in block time.
We are proposing to launch Cosmos Hub 3 at 60 minutes after Block Height [TBD].
Instructions for migration: https://github.com/cosmos/gaia/wiki/Cosmos-Hub-2-Upgrade
Please note the failure criteria and recovery scenario in the case that the migration procedure fails or in the case that cosmoshub-3 fails to start.
Notification of failure will be made in this channel: https://riot.im/app/#/room/#cosmos_validators_technical_updates:matrix.org
We are signalling that:
- The Gaia 2.0.1 implementation is aligned with the list of high-level changes approved in Cosmos Hub 3 Upgrade Proposal A.
- We are prepared to upgrade the Cosmos Hub to cosmoshub-3 based upon
a. Commit hash: [TBA]
b. The state export from cosmoshub-2 at Block Height [TBD]
c. Genesis time: 60 minutes after the timestamp at Block Height [TBD];
- We are prepared to relaunch cosmoshub-2 based upon
a. A non-trivial error in the migration procedure and/or
b. The failure of cosmoshub-3 to produce a block by 180 minutes after the timestamp of Block Height [TBD]
c. Cosmos SDK v0.34.8: [URL]
d. The ‘recovery’ instructions section of this procedure: https://github.com/cosmos/gaia/wiki/Cosmos-Hub-2-Upgrade;
- The upgrade is considered complete after cosmoshub-3 has produced one (1) block.