Lumera has upgraded to full EVM compatibility on testnet. If you have an existing Lumera wallet, your account needs to be migrated before you can use MetaMask, access EVM-based features, or interact with the new DeFi layer.
This guide walks you through the entire process from start to finish. No technical background required.
What Changed and Why You Need to Act
Before the EVM upgrade, Lumera used the standard Cosmos account system. Your wallet address was derived using a cryptographic method called secp256k1 with coin-type 118, which is the default across most Cosmos chains.
After the upgrade, Lumera now uses Ethereum-style accounts based on a key type called eth_secp256k1 with coin-type 60. This is the same key standard that MetaMask, Ethereum, and most EVM-compatible chains use.
The important detail: the same seed phrase (your 12 or 24-word recovery phrase) now produces a completely different Lumera address depending on which key type is used. Your funds, delegations, and on-chain state are still sitting at your old address. Migration is the process of moving all of that to your new EVM-compatible address in a single transaction.
A few things worth knowing before you start:
Migration is irreversible. Once completed, your legacy address is removed from the chain and all balances move to the new one. There is no going back.
Migration is free. You do not need any LUME on either address to submit the transaction.
Everything moves together. Balances, active staking delegations, unbonding entries, redelegations, authorization grants, fee grants, and vesting schedules all transfer atomically. Pending staking rewards and validator commission are also auto-withdrawn into your balance as part of the migration. Nothing is left behind.
Before You Start
You will need the Keplr browser extension installed with your wallet imported, access to the Lumera Portal, and your recovery phrase accessible since you will need it at the end to re-import into Keplr.
If you run a validator node or supernode, this guide is not for you. Those roles have dedicated migration procedures with additional steps. Start with the Validator Operator EVM Migration Guide or the Supernode Operator EVM Migration Guide instead.
Step 1: Open the EVM Migration Page
Go to the Lumera Portal and make sure you are on the legacy network profile. In the top-left network picker, you should see lumera-testnet-2 or lumera-mainnet-1 (not the EVM variant). This is the legacy profile, and it lets Keplr see your old coin-type 118 balance.
Click EVM Migration in the left-hand navigation. The page opens with a Migration Status panel at the top. Before you connect a wallet, you will already see the network name, a migration window countdown if there is a deadline, and global progress stats showing how many accounts have migrated so far.
The EVM Account Migration page before connecting a wallet
Step 2: Connect Your Wallet
Click Connect Wallet in the top-right corner and choose Keplr.
Connect Wallet dialog — select Keplr
Once connected, the Migration Status panel fills in four rows. The first shows the on-chain network with EVM support confirmed. The second shows the Portal profile (legacy coin-type 118, shown in yellow). The third shows what coin-type Keplr has stored for this chain internally (also coin-type 118 at this stage). The fourth shows which key Keplr is actually serving for your connected account (legacy key, coin-type 118).
All four rows being yellow is normal at this point. It just means you have not migrated yet. Below the status panel you will see a Ready to Migrate breakdown showing your current balance, delegations, unbonding entries, and any other state that will be moved.
Legacy account connected — Ready to Migrate breakdown
Click Start Migration Wizard to begin.
Step 3: Review Your Migration Details
The wizard opens on Step 1: Review. Check that the eligibility banner says Eligible for migration with a Standard Account badge. Verify the asset summary matches what you expect. Note both the Legacy Address (your current lumera1… address in coin-type 118) and the New Address (your destination shown both as a Lumera bech32 and an Ethereum hex 0x… format).
Step 1: Review — eligibility, addresses, and asset summary
The destination is automatically derived from your same seed phrase using the new coin-type 60 key standard. You do not need to generate a separate wallet.
Click Next when you are satisfied.
Step 4: Sign the Migration Proofs
Click Sign Migration Proofs. The wizard will tell Keplr to open two signature popups, one after the other. These are message signatures only. No tokens move, no fee is charged, and nothing is sent on-chain yet at this step.
Step 2: Sign and Confirm — before signing
The first popup is the legacy proof. Keplr shows your legacy lumera1… address and a message payload. This proves you own the old address. Click Approve.
Keplr legacy proof popup (ADR-036 signArbitrary)
The second popup is the new address proof. Keplr switches to its Ethereum signing provider and shows your 0x… address. This proves you control the destination. Click Approve.
Keplr new address proof popup (EIP-191 personal_sign)
Once both are signed, the wizard shows both proofs with green checkmarks. Tick the confirmation checkbox acknowledging that the migration is irreversible, then click Migrate.
Both proofs signed — confirmation checkbox active
Step 5: Migration Complete
The Portal broadcasts the transaction and waits for it to confirm on-chain, usually 5 to 6 seconds. On success you will see a Migration Result screen. Your funds are now at the new address. The screen shows your new Lumera bech32 address, your new Ethereum hex address, and the transaction hash with a copy button.
Migration Successful — post-migration checklist
Keep this screen open for the next step.
Step 6: Re-Configure Keplr
Your funds have moved, but Keplr still has the old coin-type 118 key loaded. You need to update Keplr so it shows the migrated account. There are a few steps here, and one specific trap to avoid.
a. Remove the legacy chain in Keplr
Open the Keplr menu (the three-line icon in the top right) and choose Add/Remove Chains. Find the legacy Lumera chain entry and toggle it off.
Keplr menu — Add/Remove Chains
Important: toggling it off does not delete it. Keplr stores chain definitions from its own registry and cannot truly delete them. This step just reduces the chance of the cached definition interfering with the next step.
Toggle the legacy Lumera chain off in Keplr
b. Switch the Portal to the EVM profile
In the Portal, click the network picker in the top-left and select the EVM variant (lumera-testnet-evm or lumera-mainnet-evm). The Portal will reload and your wallet will disconnect. This is expected.
Portal on EVM profile, wallet disconnected
Portal network picker — select the EVM profile
c. Reconnect Keplr — watch out for the trap
Click Connect Wallet again and choose Keplr. The Portal will ask Keplr to add the EVM chain definition (coin-type 60 version).
Connect Wallet on EVM profile — Keplr and MetaMask available
⚠️ Keplr may show a collapsed dialog with a title like “Add Lumera Testnet to Keplr,” a “Community driven” tag, and a large blue Approve button. Do NOT click Approve on this screen. If you do, Keplr will re-enable its cached legacy coin-type 118 definition instead of the EVM one.
Instead, click the small “Add chain as suggested” link first. This expands the full chain definition. Confirm the chain name ends in “-evm” and that it shows coinType: 60. Only then click Approve.
Correct screen: verify coinType 60 and chain name ends in -evm, then Approve
The trap: click Add chain as suggested, NOT Approve
d. Re-import your seed phrase into a fresh Keplr profile
Click your wallet name in the top-left of Keplr and click the + button. Choose Import an existing wallet, then Use recovery phrase or private key. Enter the same seed phrase you have always used for your Lumera account. Give the new profile a name such as evm-wallet and save it.
🔒 Security: only ever enter your recovery phrase into the wallet extension’s own import screen. Never paste it into a website, form, or chat. The Lumera Portal will never ask for your seed phrase.
Enter your recovery phrase
Choose Import an existing wallet
Keplr Select Wallet — click + to add a new profile
Step 7: Verify Everything Is Aligned
After selecting the newly imported wallet profile, the Migration Status panel in the Portal should show all four rows in green: Portal profile on coin-type 60, Keplr chain config on coin-type 60, Keplr account key as EVM key, and your connected wallet address matching your post-migration address.
The card body should read: Your wallet and Portal are already on the migrated EVM address. Your Keplr balance will now show your LUME at the new address. Migration is complete.
All four rows green — migration complete, wallet aligned
Step 8: Connect MetaMask (Optional but Recommended)
Now that your account is on coin-type 60, you can connect MetaMask to the same account.
Getting the Lumera network into MetaMask
The easiest way is to let the Portal do it automatically. On the EVM profile in the Portal, click Connect Wallet and choose MetaMask. The Portal will check if MetaMask already knows the Lumera EVM network. If not, it triggers a standard Add network popup in MetaMask. Confirm that the network name ends in “-evm” (for example lumera-testnet-evm or lumera-mainnet-evm), the RPC URL is an EVM JSON-RPC endpoint (not a Cosmos or CometBFT URL), and the currency symbol is LUME. The chain ID is 76857769 on every Lumera network. MetaMask will also set 18 decimals for the EVM side automatically. Click Confirm.
Connect Wallet dialog — select MetaMask
Portal dashboard before connecting MetaMask
MetaMask may label your balance as ETH in some views. This is a MetaMask display quirk for custom EVM chains. The amount is correct and represents your LUME.
MetaMask connection request — select account and connect
MetaMask Add network popup — confirm the name ends in -evm and the RPC URL is an EVM JSON-RPC endpoint
A note on RPC URLs
MetaMask speaks Ethereum JSON-RPC, not Cosmos. If you paste a Keplr or Cosmos URL into MetaMask, it will fail with “could not fetch chain ID.” The correct URLs are:
Lumera Mainnet EVM RPC: https://evm-rpc.lumera.io
Lumera Testnet EVM RPC: https://evm-rpc.testnet.lumera.io
Importing your account into MetaMask
If your migrated account does not appear in MetaMask automatically, import it. Open the MetaMask account selector, choose Add wallet, then Import a wallet, and enter your 12, 18, or 24-word seed phrase (or a single private key if you have that instead). MetaMask will derive the correct 0x… address automatically since it uses coin-type 60 by default.
🔒 Security: only ever enter your seed phrase into the MetaMask extension’s own import screen, not into any website or form — including the Lumera Portal.
Once connected, the Portal will show both your lumera1… and 0x… addresses side by side. Both represent the same account.
Portal connected via MetaMask — balances and both address formats shown
Using Both Wallets Going Forward
After migration, you have two ways to access your Lumera account. Keplr handles Cosmos-native operations: staking, governance voting, IBC transfers, and anything that uses the lumera1… address format. MetaMask handles EVM operations: DeFi protocols, dApps, and anything that uses your 0x… address format.
These are not two separate accounts. They are two different interfaces to the same account, connecting through different endpoints on the same chain.
Troubleshooting
Balance shows 0 after migration
Your funds are safe. This means Keplr is still serving the legacy coin-type 118 key and showing the now-empty old address. Follow the Keplr re-configuration steps in Step 6.
Keplr keeps going back to coin-type 118
You approved the collapsed Keplr dialog without clicking Add chain as suggested first. Disconnect, go back to Step 6c, and follow the exact sequence. The expanded screen with coin-type 60 visible is the one to approve.
MetaMask says it cannot fetch the chain ID
The RPC URL you entered is not an EVM JSON-RPC endpoint. Make sure you are using evm-rpc.lumera.io (mainnet) or evm-rpc.testnet.lumera.io (testnet), not a Cosmos LCD or CometBFT URL.
The wizard shows an error during Step 4
If you switched Keplr accounts or profiles between the two signature popups, the wizard will reject the second signature. Go back to Step 1, reconnect the same account, and run through both signatures in one go without switching wallets.
What Comes Next
EVM compatibility is the foundation for a much larger set of features on Lumera. DeFi integrations, EVM-native dApps, and cross-chain tooling all depend on accounts being on coin-type 60. Running through migration on Testnet now is also how the team identifies any edge cases before mainnet, so your experience here matters.
If you run into anything unexpected, report it in the Lumera Discord testnet channel.
Full documentation for all migration paths (including validators, supernode operators, and multisig accounts) is available here: https://pastelnetwork.notion.site/User-facing-guides-348df11fee1480e98411e2f27f798a9e
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 lumera.io
