Skip to main content
The v1.20.0 release, named Aurora Convergence, added full EVM compatibility to Lumera Protocol. It shipped on June 25, 2026 and is live on testnet (lumera-testnet-2 runs the v1.20.2 line). Mainnet still runs v1.12.0, so the mainnet upgrade is ahead. This page explains what changed and what users and operators need to do when their network upgrades.

​
What changed

  • Cosmos EVM v0.6.0 runs Solidity contracts natively alongside Cosmos SDK modules and CosmWasm
  • New modules x/vm, x/feemarket, x/precisebank, x/erc20, and x/evmigration
  • Key derivation moved from secp256k1 (coin type 118) to eth_secp256k1 (coin type 60)
  • An 18 decimal EVM denom alume bridges to the native 6 decimal ulume
  • Ethereum JSON-RPC, WebSocket, indexer, tracing, and OpenRPC discovery are on by default
  • An EIP-1559 fee market and EVM precompiles for native modules, including Action and SuperNode
Both execution environments run on the same chain and share the same state and the same security. Nothing on the Cosmos side is removed. IBC, validators, SuperNodes, governance, and bech32 addresses continue to work as before. See the smart contracts overview for the developer view.

​
Release timeline

​
Why account keys changed

The chain switched key types at the upgrade. Ethereum tooling derives addresses differently from Cosmos, so supporting MetaMask and standard EVM wallets required moving from BIP44 coin type 118 to coin type 60. The practical effect is that the same mnemonic now derives a different Lumera address. Everything you hold stays at the old address until you migrate it. The x/evmigration module moves that state in one atomic, fee-free transaction carrying two proofs, an ADR-036 signature from the legacy key and an EIP-191 signature from the new key. After migration one account works in both wallets. Keplr shows the bech32 form starting lumera1. MetaMask shows the hex form starting 0x. Both point at the same funds.
Migration is irreversible and time-limited. Delegations and unbonding become permanently unrecoverable after 30 November 2026. See EVM migration for the deadline and the steps.

​
For node operators

The release adds several EVM sections to app.toml, covering [evm], [evm.mempool], [json-rpc], and rate limiting. Nodes on v1.20.0 and later fill in missing sections automatically on first start. Mainnet rejects the debug, personal, and admin JSON-RPC namespaces. Public RPC operators should review the node config guide before the upgrade height, and the tuning guide for parameter sizing. Validators should stage the new binary in Cosmovisor ahead of the upgrade height. See validator operations for the procedure, including the libwasmvm step that catches operators out on every release.

​
Next steps

EVM migration

What to do with your account, and by when.

Smart contracts

What you can build now that the EVM is live.

Validator operations

Stage the binary and prepare for the upgrade height.