Lumera Is Now EVM-Compatible

Testnet goes live June 30, 2026. Mainnet to follow.

📣 Testnet announcement. Everything in this post applies to Lumera Testnet. Mainnet users do not need to take any action yet. We will publish a separate Mainnet announcement with specific upgrade heights and dates once the Testnet phase completes.

What this means and why it matters?

Lumera is built to be the infrastructure layer for AI and compute workloads on-chain — decentralized storage, inference, data provenance, and the economic machinery (SuperNodes, staking, IBC) that makes those things viable at scale. That vision has always required broad developer access. EVM compatibility is how we get there.

The Ethereum ecosystem represents the largest pool of smart contract developers, the deepest DeFi liquidity, and the most mature tooling of any blockchain platform. Until now, tapping into that ecosystem from a Cosmos chain meant bridges, wrappers, and custom integrations — friction that slows everyone down.

With EVM live on Lumera, that friction disappears. Solidity developers deploy directly to Lumera without learning new SDKs. DeFi protocols can write contracts that call native Lumera staking and SuperNode logic in the same transaction. Wallets, indexers, and block explorers built for EVM chains integrate Lumera without custom work. And because we built three purpose-built precompiles that expose Lumera’s native modules to Solidity, EVM contracts aren’t just running on the chain — they’re first-class participants in everything Lumera does.

Critically, this comes without giving anything up. Lumera’s Cosmos layer is fully intact. IBC, validators, SuperNodes, governance, Bech32 addresses — none of that changes. Both execution environments run simultaneously on the same chain, sharing state and security. We didn’t bolt an EVM sidecar onto Lumera. We made Lumera natively bilingual.

What Is the EVM Upgrade?

The EVM upgrade (shipping as v1.20.0 via Cosmos EVM) adds a native Ethereum execution layer to the Lumera chain. Where Lumera previously ran exclusively on Cosmos-style transactions and tooling, it now supports both — simultaneously, on the same chain.

What that unlocks:

MetaMask-compatible accounts — connect your MetaMask wallet directly to Lumera
Ethereum JSON-RPC — any dApp or tool that speaks Ethereum’s standard API works out of the box
Solidity and Vyper smart contracts — deploy contracts with Hardhat, Foundry, Remix, or any standard toolchain
11 EVM precompiles — including 3 purpose-built Lumera precompiles that expose native Lumera functionality (staking, supernodes, and more) directly to Solidity contracts
Bidirectional CosmWasm ↔ EVM bridge — CosmWasm contracts and EVM contracts can call each other natively
IBC ERC-20 middleware — cross-chain token paths work transparently through the EVM
OpenRPC discovery — full API introspection via rpc_discover and /openrpc.json

This is a production-grade implementation. Lumera launches with tracing, rate limiting, governance-controlled IBC ERC-20 policy, and EIP-1559 dynamic fees from day one — features other Cosmos EVM chains took months to add after launch.

What Stays the Same

The EVM upgrade does not replace Lumera’s Cosmos layer. Everything that exists today continues to work:

Lumera accounts and Bech32 addresses
Staking and validator operations
Supernode operations
IBC and all Cosmos-style transactions
Existing Lumera modules and application logic

The chain runs both environments together. Cosmos tools keep working exactly as before.

What Changes: Accounts and Keys

Lumera’s EVM compatibility requires a new account key type. 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 the same phrase 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 — balance, staking, delegations, rewards, unbonding, authz grants, supernode records — from your legacy address to your new EVM-compatible address. It’s a single, atomic, fee-free transaction.

Key facts about migration:

Free. Zero gas. No cost to migrate.
One-way. Once complete, the legacy address is permanently blocked. This is irreversible — always use the official flow.
Atomic. Everything moves in one transaction. There is no partial-migration state.
90-day window on Testnet. After the Testnet upgrade, operators and users have 90 days to migrate. Mainnet will follow the same structure.
Balances are safe. Even if you don’t migrate immediately, your liquid balance remains at your legacy address and cannot be lost. However, delegations, staking, and unbonding are permanently unrecoverable if you miss the migration window. If you stake, migrating in time is not optional.

The Rollout Plan

Given the significant changes involving the network, the roll-out is being done in stages:

Phase Status Timing Release candidate validation ✅ Done — Devnet upgrade rehearsal ✅ Done — Testnet rollout ⏭️ Live now June 30, 2026 Mainnet readiness review ⬜ Upcoming Expected 4 Weeks from Testnet Mainnet upgrade ⬜ Upcoming Expected 8 Weeks from Testnet

The Testnet phase is where users, validators, developers, and partners should rehearse the full flow before Mainnet.

Get Started: The Guides

All documentation lives in the Lumera GitHub repository. Start with the guide that matches your role:

End Users

EVM Migration User Guide — The canonical migration walkthrough. Covers the Portal + Keplr wizard, shell scripts, and raw CLI paths. If you’re a regular wallet user, start here.
MetaMask Configuration Guide — How to connect MetaMask to Lumera’s EVM JSON-RPC endpoint, import your migrated account, and verify everything is working.

Validators

Validator Operator EVM Migration Guide — Validators must use MsgMigrateValidator, not the standard user flow. This guide covers the maintenance window, the consensus key guarantee (your priv_validator_key.json is not touched), and the unjail recovery flow.

Supernode Operators

Supernode Operator EVM Migration Guide — Two paths: let the daemon migrate for you on restart, or migrate manually first and let the daemon detect the on-chain record. Covers the multisig path and common troubleshooting.

Node Operators & Relayers

Node Operator EVM Config Guide — Full app.toml reference for all EVM-relevant sections, deployment patterns for validator/public-RPC/archive nodes.
Hermes IBC Relayer Migration Guide — The HD-path gotcha every relayer operator needs to know before migrating.
Migration Scripts Guide — For bulk migrations, CI pipelines, and safety-rail wrappers around the raw CLI.

Developers

Deploy contracts via Remix, Hardhat, or Foundry using Lumera’s EVM JSON-RPC endpoint
Use Lumera’s custom precompiles to call native staking and supernode functions from Solidity
Explore the full API via OpenRPC: /openrpc.json on any Lumera RPC node

Why This Matters

Lumera is built for Web3 infrastructure and compute workloads — storage, inference, data provenance, and the economic infrastructure that makes those things viable on-chain. EVM compatibility means that the developer tooling and liquidity that grew up in the Ethereum ecosystem can now target Lumera directly.

Solidity developers don’t need to learn new SDKs. DeFi protocols can deploy contracts and access native staking logic in the same transaction. Bridges, indexers, and wallets built for EVM chains can integrate Lumera without custom work.

And because Lumera’s Cosmos layer remains fully intact, nothing is being traded away. IBC, supernodes, Cosmos governance, and the existing module architecture continue operating exactly as before.

The chain is running and Testnet is live.

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.