Cronos Mainnet network upgrade to beta v0.7.0 — proposed for May 10, 2022

An internal dry-run has been completed, and the Cronos mainnet beta binary v0.7.0 will be released soon. The binary is upgraded based on…

An internal dry-run has been completed, and the Cronos mainnet beta binary v0.7.0 will be released soon. The binary is upgraded based on Cosmos SDK 0.45.4 and Tendermint v0.34.19, containing several major changes, key improvements and multiple fixes.

Moving forward, we are proposing the network upgrade for the Cronos mainnet beta to take place on May 10, 2022. On that date, node operators will need to upgrade their cronosd binary to the newest version v0.7.0 at a specific block height announced in a separate post. No action is required before May 10, 2022.

See this post for announcement and details

What’s included in this upgrade:

• This binary includes multiple dependency upgrades (Ibc-go, Ethermint, Cosmos-SDK) and several bug fixes, including WebSocket bug fix, Metamask transaction failure fix, and more.

• A new feemarket module introduces a dynamic fee structure to the network. With this implementation, the common base fee is calculated dynamically at each block for the next block, depending on network utilization, and enforced in the whole network.

• In v0.7.0 binary, the development team has implemented a refactoring of the EVM’s StateDB to improve the performance of contract execution significantly. This improvement allows a larger transaction volume to be processed within each block, hence increasing overall efficiency and scalability.

If you are interested in diving deeper, you may refer to Network Upgrade on Cronos Testnet v0.7.0 and Cronos Testnet v0.7.0 upgrade release notes.

What to expect:

The proposed upgrade date is May 10, 2022 and the chain will be upgraded at a specific block height.

See this post for announcement and details:

• Target upgrade block height;

• Links to v0.7.0 release;

• Instruction for the upgrade (config.toml and parameters updates).

After the upgrade block height, all node operators should upgrade their node binary to v0.7.0 so that their node can continue to sync with the chain. The chain will be paused, and put back on once the majority of validators have been upgraded.

How do I prepare?

Node runners will need to upgrade to the latest cronosd binary until the chain reaches the specific block. Kindly refer to our announcement regarding the block height for the upgrade and DO NOT UPGRADE to the binary v0.7.0 before that.

See this post for announcement and details

If you would like to test out some new features ahead, feel free to interact the Cronos testnet v0.7.0. For instance, you may try to performing transactions with the dynamic fee structure. The transaction records including transaction fees can be tracked on the Cronos testnet explorer.

—

If you have questions or comments, please reach out to us via the #cronos-mainnet-beta channel on the Cronos & Crypto.org Discord server or you may email chain@crypto.org.

We sincerely thank you for your support. Best regards,

The Cronos chain team