Skip to content

v8.0.0
Compare
Choose a tag to compare
@glnro glnro released this 31 Jan 13:35
· 624 commits to main since this release
v8.0.0
f9507c7
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Gaia v8.0.0 Release Notes

This is the final release for the Rho upgrade which is proposed to take place at height 14,099,412 which should occur approximately at February 16th 2023 at approximately 13:00 UTC. The chain id will remain cosmoshub-4.

For full upgrade instructions please see https://hub.cosmos.network/main/hub-tutorials/upgrade-node.html.

Rho Changelog :

Summary

This on-chain upgrade governance proposal is to adopt Gaia v8.0.0. By voting YES to this proposal, you approve of adding these updates to the Cosmos Hub.

This upgrade does not include the Replicated Security feature; that will be part of the v9-Lambda upgrade.

The forum post discussing this upgrade can be found here.

Background

Since the last v7-Theta upgrade at height 9283650 there have been a number of updates, fixes and new modules added to Gaia.

Updates

  • Bump IBC to v3.4.0 from v3.0.0 which includes a fix for the interchain accounts vulnerability. See the full Changelog for more information.
  • Bump Cosmos SDK to v0.45.12 from v0.45.9. See the full Release Notes and Commit History for details and updates between the last version of the SDK used in Theta.
  • Bump Tendermint to v0.34.24 and replace with the Informal Systems fork to ensure software continuity.
  • Bump Liquidity to v1.5.3 which notably includes updating Go to 1.18 and the Cosmos-SDK to v45.11 to ensure compatiblity with the Cosmos Hub.
  • Bump Packet Forward Middleware to v3.1.1 from v2.1.1. Users should note that PFM was not configure properly in the previous version of Gaia. This module update includes necessary bug fixes to make it functional on the Cosmos Hub in v8.

Features

  • Add the Global Fee module to the Cosmos Hub, which enables setting transaction fees at the network level via param-change governance proposal. For more information, see the module documentation.
  • Add the debug bech32-convert command, enabling users to convert any bech32 string to the cosmos prefix.

Fixes

  • Fix Bank Denom Metadata issue. In a previous upgrade, the x/bank metadata was incorrectly migrated, resulting in an incorrect bank metadata. See the fix in the upgrade handler for more information.
  • Fix Quicksilver ICA exploit detailed in the forum post on the incident. See the fix in the upgrade handler for more information.

Tests

Testnet

V8 Rho went live on the persistent testnet after the successful simulated upgrade. For more information, see the testnet upgrade proposal or block explorer, and visit the persistent testnet documentation.

On-Chain Upgrade Process

This upgrade can be performed in multiple ways. When the network reaches the halt height, the state machine program of the Cosmos Hub will be halted. The classic method for upgrading requires all validators and node operators to manually substitute the existing state machine binary with the new binary. Alternatively node operators can use the Cosmovisor utility to swap the binaries automatically. Cosmovisor also includes the ability to download the binaries automatically before swapping them. Documentation on Cosmovisor can be found here and instructions specific to the upgrade can be found here. If you are interested in trying Cosmosvisor with a simulated local upgrade please see the local testnet documentation. Because it is an onchain upgrade process, the blockchain will be continued with all the accumulated history with continuous block height.

Potential Risk Factors

Although very extensive testing and simulation has taken place there always still exists 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 #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 (v7.1.0).

App: gaiad
Version: v8.0.0
Commit: f9507c7e79f258aaa9a2265ca7d94e53988ffe16
Files:
 8fe881e83591c0fc0b469581d20d5bb6  gaiad-v8.0.0-darwin-amd64
 d372488e8e8b7563151a32d629777495  gaiad-v8.0.0-darwin-arm64
 05122de371d5eaea915a23b9ca6953cb  gaiad-v8.0.0-linux-amd64
 ab6e43a56759384184f1efe6505b410f  gaiad-v8.0.0-linux-arm64
 eef509e8d352d4542c373d7efdba2322  gaiad-v8.0.0-windows-amd64.exe
 c60a462f039ca2b6bb92dbca770d0a30  gaiad-v8.0.0.tar.gz
Checksums-Sha256:
 e66c0e62aa5b0ccf9fb174c50b598df6048c1d7952f5f99b807b9934c9629f2c  gaiad-v8.0.0-darwin-amd64
 95000b52f55f22e1b40b81263bc0ae0df1351e8b9b40264c54509ad1e4d6e9fb  gaiad-v8.0.0-darwin-arm64
 6d0c123e246a8b56ba534f70dd5dc72058b00fd5e5dde5ea40509ff51efc42e2  gaiad-v8.0.0-linux-amd64
 a0afbbe35eda3d5e52a7907bcae296415e84b3ff6c7da97429d91f324004a5ab  gaiad-v8.0.0-linux-arm64
 fca2a4371eef6dc50b6b46a025bde3537fa96ec32c732499c8be8aa64683f147  gaiad-v8.0.0-windows-amd64.exe
 52e3dc20f3425c95c0b9141e9e0a5f7a32d641a92a2873f8decb669a8723b2f4  gaiad-v8.0.0.tar.gz
Assets 9
Loading