EVM Legacy Account Migration - User Guide

Applies to: Lumera chain with x/evmigration module enabled (post-EVM upgrade)

Why Migration Is Needed

The Lumera chain upgraded from a standard Cosmos SDK chain to an EVM-compatible chain. This changed the underlying cryptography used for account addresses:

• Before the upgrade (legacy): accounts used coin-type 118 with secp256k1 keys and Cosmos-style address hashing (ripemd160(sha256(pubkey)))
• After the upgrade (EVM): accounts use coin-type 60 with eth_secp256k1 keys and Ethereum-style address hashing (keccak256(pubkey)[12:])

Because the address derivation changed, the same mnemonic now produces a different Lumera address. Your funds, delegations, and other on-chain state remain at the old (legacy) address. Migration moves all of that state to your new EVM-compatible address.

What Gets Migrated

Migration transfers all on-chain state from your legacy address to your new address in a single atomic transaction:

• Bank balances (all denominations)
• Staking delegations (active delegations to validators)
• Unbonding delegations
• Redelegations
• Authz grants (both as granter and grantee)
• Feegrant allowances (both as granter and grantee)
• Action records (creator and supernode references)
• Claim records
• Supernode registration (if applicable)