Lumera Mainnet Is Going EVM-Compatible: What You Need to Know Before You Migrate

Lumera’s EVM upgrade has been running on Testnet since late June, and the results have been smooth which means that Mainnet is next. The upgrade is coming soon, and when it does, every Lumera account holder, validator, and supernode operator will need to take one specific action: migrating to a new account key type.

This post explains what is changing, why it matters, and what you need to do to make sure your balance, staking, and delegations move over safely. There is no action required today. Consider this your advance notice so you understand the process before the migration window opens.

What Is Changing

Lumera is adding a native Ethereum execution layer alongside its existing Cosmos layer. Once live, the chain runs both environments simultaneously, sharing the same state and the same security.

In practice, that means MetaMask-compatible accounts, full Ethereum JSON-RPC support, Solidity and Vyper smart contracts, and custom precompiles that let EVM contracts call Lumera’s native staking and supernode logic directly. Developers can deploy with Hardhat, Foundry, or Remix without learning a new SDK. Wallets, indexers, and block explorers built for EVM chains can integrate Lumera without custom work.

Nothing about Lumera’s Cosmos layer is going away. IBC, validators, supernodes, governance, and Bech32 addresses all continue to work exactly as they do today. The two execution environments run side by side on the same chain.

Why This Matters

Lumera is built as infrastructure for AI and compute workloads on chain: decentralized storage, inference, data provenance, and the economic layer of staking and supernodes that makes all of it viable at scale. That vision depends on broad developer access, and the Ethereum ecosystem holds the largest pool of smart contract developers, the deepest DeFi liquidity, and the most mature tooling of any blockchain platform.

Until now, reaching that ecosystem from a Cosmos chain meant bridges, wrappers, and custom integrations, all of which add friction and slow everyone down. With EVM support live, that friction goes away. Solidity developers deploy directly to Lumera. DeFi protocols can call native Lumera staking logic from the same contract that handles their trading logic. None of this required giving anything up on the Cosmos side. Lumera is not bolting an EVM sidecar onto the chain, it is becoming natively bilingual.

The Part That Affects You: Account Migration

Here is the piece that requires action from every user, validator, and supernode operator.

Legacy Lumera accounts use coin type 118 with secp256k1 keys, the Cosmos default. EVM-compatible accounts use coin type 60 with eth_secp256k1 keys, the Ethereum standard. Your existing recovery phrase still works, but it now derives a different Lumera address using the new coin type. That new address is your EVM-compatible account.

Migration is the process of moving your existing on-chain state, including your balance, staking, delegations, rewards, unbonding, authz grants, and supernode records, from your legacy address to your new EVM-compatible address. Here is what you need to know:

It’s free. Zero gas. There is no cost to migrate.
It’s one-way. Once migration completes, your legacy address is permanently blocked. This is irreversible, so always use the official migration flow.
It’s atomic. Everything moves in a single transaction. There is no partial-migration state.
There is a 90-day window. Once Mainnet upgrades, you will have 90 days to migrate. This mirrors the window that has been running successfully on Testnet.
Your liquid balance is safe either way. Even if you don’t migrate right away, your balance stays at your legacy address and cannot be lost. Staking, delegations, and unbonding are different: if you miss the migration window, they are permanently unrecoverable. If you stake, migrating within the window is not optional.

Who This Applies To

Regular users follow the standard migration flow through the Portal, Keplr wizard, or CLI.
Validators use a dedicated migration path (MsgMigrateValidator). Your consensus key is not touched, only your operator key changes.
Supernode operators can let the daemon migrate automatically on restart, or migrate manually and let the daemon detect the on-chain record.
Node operators and relayers should review the EVM config and Hermes IBC relayer guides ahead of the upgrade, since there are HD-path details relayer operators specifically need to know before migrating.

What To Do Right Now

Nothing, yet. Mainnet has not upgraded. This post is here so that when the migration window does open, you already understand what is happening and why.

If you want to see the process in action first, Testnet has been running the exact same migration flow since late June. Rehearsing there is the best way to walk through the steps before Mainnet requires it.

Guides for every role are available in the Lumera GitHub repository:

End users: EVM Migration User Guide, MetaMask Configuration Guide
Validators: Validator Operator EVM Migration Guide
Supernode operators: Supernode Operator EVM Migration Guide
Node operators and relayers: Node Operator EVM Config Guide, Hermes IBC Relayer Migration Guide

We will publish the full Mainnet upgrade announcement, with the exact upgrade height and migration window details, once the upgrade is scheduled and confirmed. Watch this space, Twitter, Discord, and Telegram for that update.

About Lumera Protocol

Lumera Protocol is a high-performance blockchain purpose-built for AI-driven Web3 economies, integrating a Validator-SuperNode architecture to enable decentralized AI services, trustless computation, and secure data storage. Built on cometBFT Proof-of-Stake (PoS), Lumera ensures cross-chain compatibility, efficient AI data sharing, and scalable interoperability.

At its core, Lumera’s SuperNode-powered infrastructure extends beyond validation to support LLM hosting, autonomous agents, task verification, and cross-network communication, with governance driven by a stake-weighted system. Its adaptive tokenomics dynamically adjust inflation based on network participation, ensuring economic sustainability.

Lumera also introduces an Action & Agent Framework, powering decentralized AI services through specialized Actions (e.g., Cascade for storage, Sense for verification) and Agents (e.g., Inference for AI computation). By merging AI, decentralized computation, and blockchain security, Lumera sets a new standard for AI-powered applications and autonomous services in Web3.

For more information on Lumera, follow us on Twitter, Telegram, Discord and visit https://lumera.io.