Skip to content

Releases: cosmos/evm

v0.4.1

14 Aug 18:45
f0609d9
Compare
Choose a tag to compare

v0.4.1

Cosmos EVM v0.4.1 is a minor version update with major feature additions and several quality of life improvements. For complete documentation on the latest version, refer to the docs.

Major feature upgrades:

  • Upgrades Go-Ethereum v1.16.2
  • EVM Callbacks, allowing OnReceive messages to be executed on IBC receipts
  • (Experimental) EVM-Compatible Appside Mempool (Integration and Architecture Docs)
    • Adds the txpool namespace
  • Preinstall message handler for adding preinstalled smart contracts at specified addresses

Major quality of life improvements

  • Improved StateDB balance handling
  • JSON-RPC alignment with Go-Ethereum
  • Fully decoupled /evmd from /evm
  • Cleaned up EvmAppOptions
  • Fixed keyring options
  • Multi-node testing infrastructure

For migrating from v0.3.x, please refer to the migration guide.

What's Changed

Read more

v0.3.1

05 Aug 20:31
13181f2
Compare
Choose a tag to compare

Cosmos EVM v0.3.1 is a patch update with some minor quality of life changes and dependency updates.

What's Changed

New Contributors

Full Changelog: v0.3.0...v0.3.1

v0.3.0

25 Jul 21:19
c4e5233
Compare
Choose a tag to compare

This release has been audited by Sherlock. A link to the final audit report can be found here.

The v0.3.0 release includes:

  • Upgraded GETH to v1.15
  • Permissionless ERC20 registrations on x/bank
  • Support for IBC v2 & IBC-Go v10
  • Support for Cosmos SDK v0.53.x
  • Integrated Kava's x/precisebank to handle varying decimals for gas tokens
  • Feemarket for Dynamic Fee transaction support (EIP-1559)
  • Removal of the x/authz dependency on precompiles
  • Changed erc20/ prefix to erc20: to support IBC v2 specification
  • Testing refactor
  • Separate Cosmos and EVM chain IDs (no longer required to merge these into one chain-id string)
  • x/gov precompile now supports all messages including proposal submission

Our priorities for the next v0.4.0 release are:

  • Getting the application-side mempool working
  • Spiking all remaining EVM-equivalence unknowns (and fixing high priority ones)
  • Setting up a proper benchmarking framework and perform load-testing