- 2023-05-26 Created initial post
Please note that an older proposal for v10 has now been archived and is no longer relevant.
Informal Blog - Informal Hub Team Jan 2023 update
This release contains a number of updates to core dependencies and an upgrade to the golang version that should be used to build and run Gaia.
The relevant commits are:
- (deps) #2498 Bump multiple dependencies.
- (deps) Bump cosmos-sdk to v0.45.16-ics. See the v0.45.16 release notes for details.
- (deps) Bump ibc-go to v4.4.0.
- (deps) Bump CometBFT to v0.34.28.
- (gaia) Bump Golang prerequisite from 1.18 to 1.20. See (Go 1.20 is released! - The Go Programming Language) for details.
The release binaries and further details can be found here on Github.
A release checklist can be found here.
The v10 release has gone through rigorous testing and has been independently tested by Hypha.
Validators can join either the Cosmos Hub Public Testnet (theta-testnet-001) or the Cosmos Hub Replicated Security Testnet provider chain, both of which have been upgraded to v10. You can find the relevant information (genesis file, peers, etc.) to join the testnets via shell script or Ansible playbook here for the public testnet or here for the replicated security one. The cosmos/testnets repo also includes information on how to test the upgrade using a local testnet.
Although extensive testing and simulation has taken place, there always is a risk that the Cosmos Hub might experience problems due to potential bugs or errors from the new features. In the case of serious problems, validators should stop operating the network immediately.
Cosmos Core Contributors will coordinate with validators in the #cosmos-hub-validators-verified channel of the Cosmos Developer Discord to create and execute a contingency plan. Likely this will be an emergency release with fixes or the recommendation to consider the upgrade aborted and revert back to the previous release of gaia (v9.x.x).
If this proposal passes, a software upgrade proposal will occur at the specified halt-height.
If this proposal is rejected, then nothing will happen and the Cosmos Hub will continue to run the recommended v9.x version.
The following items summarise the voting options and what it means for this proposal:
You agree that the Cosmos Hub should be updated with this release.
You disagree that the Cosmos Hub should be updated with this release.
NO WITH VETO
A ‘NoWithVeto’ vote indicates a proposal either (1) is deemed to be spam, i.e., irrelevant to Cosmos Hub, (2) disproportionately infringes on minority interests, or (3) violates or encourages violation of the rules of engagement as currently set out by Cosmos Hub governance. If the number of ‘NoWithVeto’ votes is greater than a third of total votes, the proposal is rejected and the deposits are burned.
You wish to contribute to the quorum but you formally decline to vote either for or against the proposal.