Proposal Details
Proposal #94
Proposal title
Evmos Mainnet v10.0.0 Upgrade
Submit time
Deposit end time
Voting start time
Voting end time
Tally result
Proposal #94 description
Description
Author
Daniel Burckhardt, Evmos Core Team
Software upgrade being scheduled with this proposal
If successful, this proposal will schedule an Evmos Mainnet software upgrade at block height 9,495,000 from its current version v9.1.0 to v10.0.0. This proposal has a voting time of 5 days.
Motivation
By proposing a scheduled upgrade, we want to implement a smooth and transparent upgrade process, that is first proposed on Testnet and then on Mainnet. Software upgrades generally aim to improve current performance and add new features to the Evmos chain. For more information on the types of upgrades, please visit our Software Upgrade Guide.
Impact
On a high level, the v10.0.0 software includes the following improvements:
- Update Cosmos-SDK to v0.46.7, IBC-Go to v5.2.0 and Ethermint to v0.20.0
- Automatic conversion of IBC coins to their ERC20 representation upon receiving
- Support for ERC20 token transfers via IBC
- ERC20 proposals to register ERC20 tokens and Cosmos coins now can receive multiple denominations
- Prioritized mempool support for Cosmos and Ethereum txs
- EIP-1559 support for native Cosmos transactions
- EIP-712 fixes for all major Cosmos messages (eg: MsgGrant for restake support)
- Add Ledger support to the evmosd CLI
- Ethereum Tx indexer
- The funder for a clawback vesting account can now be updated
- Introduce minimum commission rate as governance ruled parameter for the staking module (set at 5%)
- EIP-712 fixes for the vesting module
- Add a default file store listener for a basic implementation of ADR-038: State Listening
- Update default node snapshot interval to 5000 seconds
- Update Ledger supported algorithms to only consist of EthSecp256k1
A full change log can be found here.
NOTE: Since Cosmos v0.46 it is not possible to include links to Windows binaries in software upgrade proposals anymore.
Testing
The Evmos core team created an End-to-End testing suite that performs the software upgrade locally. These tests have been completed successfully for this upgrade. The instructions on how to run the End-to-End testing suite can be found here. Additionally, the upgrade has been manually performed on a local node.
Discussion
Before voting, please follow and discuss this proposal using the official discussion on commonwealth.