MetaMask Wallet on EVM Networks: Complete List of Supported Chains and Setup Instructions

A user with digital assets across multiple blockchains faces a practical question: which wallet maintains control over those funds while offering straightforward access to decentralized applications and token swaps across different networks? MetaMask wallet has become the dominant interface for Ethereum and its ecosystem, but its support extends far beyond the mainnet. Understanding which chains are supported, how to configure them, and what differences exist between networks is essential for managing assets efficiently and avoiding costly routing mistakes.

MetaMask functions as a self-custody wallet, meaning the user retains ownership through their recovery phrase and private keys, stored locally rather than on MetaMask’s servers. The application is available as a browser extension on Chrome, Firefox, Brave, Edge, and Opera, as well as on iOS and Android mobile devices. As a multichain wallet, it now supports Ethereum, Bitcoin, Solana, and dozens of EVM-compatible networks—environments that follow Ethereum’s Virtual Machine standard and therefore can work with MetaMask’s basic architecture. However, not all chains are equal in terms of setup effort, user interface integration, or transaction cost.

Why EVM compatibility matters for multichain wallets

The Ethereum Virtual Machine is a runtime environment that executes smart contracts and transaction logic. Networks that adopt EVM compatibility do not fork Ethereum’s entire code; instead, they build their own consensus and data layers while accepting the same contract code and address format. This standardization means that a single address generated by MetaMask wallet can function across all EVM networks with the same private key. A user does not need separate wallets for Arbitrum, Polygon, or Base—switching between them involves selecting the network rather than importing a new recovery phrase.

This design choice simplifies user experience but creates operational constraints. Each EVM network has its own transaction fee structure, block time, and smart contract ecosystem. A token contract on Polygon is a different contract from the same token on Ethereum, even though both use the same token name or symbol. Sending funds to the wrong network address can result in permanent loss because the token contract does not exist on the destination chain. Therefore, network selection is not merely a convenience setting; it is a critical control point in every transaction.

Non-EVM networks present a different category entirely. Bitcoin and Solana do not use the EVM and require separate derivation paths and address formats. MetaMask now offers limited support for these chains through additional setup, but the user experience is less seamless than switching between Layer 2s or sidechains. The practical consequence is that multichain wallet users must understand the distinction between an EVM-compatible network and an entirely separate blockchain.

Ethereum and Layer 2 networks: the core EVM ecosystem

Ethereum mainnet is the network where MetaMask was originally built and remains the most widely used. It supports the broadest range of decentralized applications, token contracts, and liquidity pools. However, Ethereum mainnet transaction fees vary considerably depending on network congestion. During periods of heavy activity, sending a transaction can cost tens or hundreds of dollars. For users prioritizing lower costs and higher transaction throughput, Layer 2 networks built on top of Ethereum are the primary alternative.

Arbitrum One is an optimistic rollup that batches transactions off-chain and posts them to Ethereum for settlement. It has become one of the largest Layer 2 ecosystems with significant liquidity for DeFi protocols and a growing NFT market. Transaction costs on Arbitrum are typically under one dollar. Optimism is another prominent optimistic rollup with a comparable cost structure and a strong developer ecosystem. Both networks require manual addition to MetaMask wallet if using an older version, though recent versions often include them by default.

Base, built by Coinbase, is an Optimism-based network with integrated fiat on-ramp and off-ramp services, making it useful for users converting between crypto and traditional currency. Polygon (formerly Matic) operates as a sidechain rather than a rollup, maintaining its own set of validators. It has the lowest transaction fees among major networks and hosts the largest ecosystem of DeFi and gaming applications. zkSync Era and StarkNet are zero-knowledge rollups that use cryptographic proofs rather than fraud proofs; they offer stronger security guarantees in theory but a smaller ecosystem in practice. Each network can be added to MetaMask through the network switch menu or by using the network’s official RPC endpoint.

How to add and configure EVM networks in MetaMask

MetaMask includes several major networks by default: Ethereum, Sepolia testnet, Arbitrum One, Optimism, and Polygon. For networks not listed, users can add them manually by providing four critical pieces of information: the network’s RPC endpoint URL, the chain ID, the native currency symbol, and the block explorer URL. Each value must be exact. An incorrect chain ID or RPC endpoint can cause transactions to fail or send funds to an unintended destination.

To add a custom network in the browser extension, click the network button at the top left, select “Add a network,” then “Add a network manually.” Enter the network details in the provided fields. For mobile, navigate to Settings, tap Networks, and select “Add a Network.” Always verify these values against the official network documentation rather than trusting third-party sources. A malicious RPC endpoint can return false transaction information or expose your wallet address to network surveillance.

Major networks often provide their own button or link that adds them to MetaMask automatically, bypassing manual entry. This is more convenient and reduces the risk of typos, but it still depends on the user visiting the legitimate website. A phishing site could present the same interface and add a fraudulent RPC endpoint instead. After adding any network, make a test transaction with a small amount before transferring significant funds. Confirm that the transaction appears on the correct block explorer and settles to the expected address.

RPC endpoint selection also affects reliability and privacy. MetaMask’s default endpoints are managed by Infura and Alchemy, professional services that handle millions of requests daily. Users concerned about privacy can run a local node or use Tor-compatible RPC services, though this introduces technical complexity and potential latency. For most users, the trade-off between convenience and privacy makes the default endpoints acceptable, but the choice remains under the user’s control.

Bitcoin and Solana support: beyond EVM compatibility

MetaMask’s addition of Bitcoin and Solana support marks a shift toward becoming a general-purpose blockchain wallet rather than an Ethereum-focused tool. However, these non-EVM chains require different address generation and transaction signing logic. Bitcoin addresses use legacy, SegWit, or Bech32 formats, while Solana uses a base58 encoding. A recovery phrase generated by MetaMask wallet can derive addresses on all these networks, but the addresses and transaction formats are incompatible across chains.

Bitcoin support is still experimental in MetaMask. It allows users to hold Bitcoin in the wallet but offers limited functionality for sending and receiving compared to dedicated Bitcoin wallets. The interface for Bitcoin transactions is less polished than the Ethereum experience, and fee estimation can be opaque. Users moving significant Bitcoin balances should test small transactions first and maintain familiarity with the actual network fee structure for the current block height.

Solana integration is more mature. MetaMask can interact with Solana programs and authorize transactions on the Solana blockchain. However, users should be aware that the Solana wallet generated by MetaMask uses a different derivation path than some other Solana wallets. This means that importing a Solana seed phrase from another wallet into MetaMask may not produce the expected address. Verification through a test transaction is critical.

Common EVM networks by layer, cost, and ecosystem size

Network selection involves trade-offs between transaction cost, ecosystem maturity, and technical risk. Ethereum mainnet has the highest fees but the deepest liquidity and most established protocols. Users should expect fees ranging from five dollars during low congestion to over one hundred dollars during peak activity. Arbitrum and Optimism offer a middle ground with moderate fees, strong developer communities, and direct settlement on Ethereum, which some users perceive as more secure than sidechains.

Polygon has the lowest fees, often fractions of a cent, making it ideal for testing or small transactions. However, as a sidechain, Polygon does not inherit Ethereum’s security properties in the same way a Layer 2 does. The trade-off is acceptable for many use cases but should be understood. Base combines low fees with Coinbase’s institutional backing and integration, making it attractive for users who may want to move funds to traditional finance. BNB Chain is the Binance-operated EVM network with extremely high activity and competitive fees, though it is more centralized than networks with larger validator sets.

Avalanche, Fantom, Harmony, Celo, and Gnosis Chain are mature EVM networks with their own ecosystems and communities. Each has lower fees than Ethereum and less congestion than major Layer 2s. The choice depends on where specific applications or tokens are deployed. A user tracking a particular DeFi protocol should configure MetaMask wallet to support the networks where that protocol is live. This often means adding multiple networks to the wallet and checking the official protocol website to confirm deployment addresses.

Critical security and operational considerations across networks

Managing a recovery phrase across multiple EVM networks simplifies key management but concentrates risk. If the recovery phrase is compromised, all addresses across all networks are immediately vulnerable. Hardware wallet integration through Ledger or Trezor can mitigate this risk by keeping the private key isolated during transactions, though this adds latency and complexity. For smaller balances or test funds, software MetaMask wallet security depends primarily on the user’s device security and password strength for the MetaMask application itself.

Network switching is a common source of user error. Approving a transaction on the wrong network or sending funds to an address that does not support the originating chain can result in permanent loss. MetaMask displays network information prominently, but users must develop a habit of verifying the network name and chain ID before confirming any transaction. This is especially critical when using a dApp that works across multiple networks, as the interface may not make the active network obvious.

Custom RPC endpoints introduce additional attack surface. A malicious RPC could return false balance information, incorrect transaction history, or claim transactions succeeded when they did not. The wallet’s core security—the ability to control funds through the private key—is not compromised by a bad RPC, but transaction reliability and user awareness can be. Users should trust official RPC providers and monitor community reports for any network outages or service degradation.

Token approval patterns also deserve attention. When interacting with a DeFi protocol, the user typically approves the protocol smart contract to spend a specific token on their behalf. An excessive approval (for example, unlimited spending) or approval to a malicious contract can result in token theft. Users should grant minimal necessary approval amounts, revoke approvals to contracts no longer in use, and verify the contract address against official documentation before approving. This applies equally whether the transaction occurs on Ethereum or any supported EVM network.

Comparing MetaMask to other multichain wallets

Phantom is the dominant non-custodial wallet for Solana but also supports Ethereum and Polygon. It offers a more refined Solana experience than MetaMask but less Ethereum ecosystem depth. Trust Wallet is a mobile-first multichain wallet supporting over 70 blockchains, including all major EVM networks, Bitcoin, Solana, and many others. It has less Ethereum application integration than MetaMask but broader coverage of smaller networks. Rabby is a newer wallet focused on sophisticated DeFi users, with advanced features like batch approvals and token simulations, but fewer networks supported initially.

MetaMask wallet remains the market standard for Ethereum and EVM networks because of its browser extension accessibility, integration with virtually every major DeFi protocol, and first-mover advantage. For users prioritizing Ethereum, Layer 2s, or broad Web3 compatibility, it remains the most practical choice. For Solana-first users, Phantom is superior. For coverage of smaller blockchains, Trust Wallet provides breadth MetaMask does not match. The decision ultimately depends on which networks and applications the user intends to use most frequently.

Best practices for maintaining control and reducing transaction errors

Regular backups of the recovery phrase, stored offline in a physically secure location, are non-negotiable. The phrase should never be typed into a computer file, sent over email, or photographed in a way that could be cloud-synced. A hardware wallet or security deposit box can provide appropriate storage. Users should also document which networks are configured, which applications have token approvals, and what assets are held where. This documentation should not include the recovery phrase itself but should be detailed enough to allow account recovery without relying on memory.

Testing is especially important when configuring a new network or using a new application. Send a small amount of the native cryptocurrency (ETH on Ethereum, MATIC on Polygon, ARB on Arbitrum) to the address to verify it works. Confirm the transaction on the correct block explorer before sending larger amounts. Do not rush or assume because the address looks correct in the wallet interface. Typos in custom RPC endpoints or incorrect chain IDs have caused real financial losses.

Staying informed about network status and security announcements also reduces operational risk. Follow official Twitter accounts or documentation for networks and applications you use. Monitor MetaMask’s changelog for updates, as new versions often include bug fixes or security improvements. Be skeptical of unsolicited messages claiming to offer help or asking to verify the recovery phrase. The legitimate MetaMask team will never ask for this information.