Metamask wallet
MetaMask wallet is a network-aware transaction console for choosing the right chain and recovering wrong-network transfers
Metamask wallet is a self-custodial transaction interface that binds each EVM signature to the selected network, shows the recipient, asset, amount, and fee before approval, and records the submitted action on that chain. If funds appear on an unexpected network, enable or filter for that network, verify the transaction there, and bridge or resend only after confirming control of the destination account.
The decisive evidence is the chain ID and transaction hash, not the ticker alone. The following workflow starts before confirmation, follows the receipt, and handles the common case of a correct EVM address on the wrong chain.
Prepare the intended network before sending
Network selection in the Metamask wallet is a pre-signing control that determines which EVM ledger receives the transaction.
Every EVM network exposes a numeric chain ID. Ethereum Mainnet uses 1, OP Mainnet uses 10, Polygon PoS uses 137, Base uses 8453, and Arbitrum One uses 42161. The network name is a display label; the chain ID enters the signing context and separates one ledger from another. Confirm that the receiving service supports the exact network, then select the same account, token, and chain inside the wallet. A balance of ETH on Base is Base state, not Ethereum Mainnet state, although both networks use ETH as their native fee symbol.
Metamask keeps network permissions per decentralized application, so one connected app may use Arbitrum while another uses Ethereum. The Tokens view aggregates assets across enabled networks and lets you filter them by chain. Filtering changes the ledger data on screen; switching a connected app changes where its next request will execute. If a network is absent, add its published chain ID, currency symbol, and RPC settings before proceeding. This setup keeps the app request and wallet confirmation on the same ledger.
Which recovery route matches the transaction state?
A recovery route is a control decision based on whether the EVM transaction is unconfirmed, confirmed to your address, or held by a custodial account. Pending transactions remain candidates for speed-up or cancellation; confirmed transactions require a new on-chain action. A canonical withdrawal from OP Mainnet through its Standard Bridge uses a fixed 7-day challenge period, so bridging is a settlement process rather than an instant network switch.
| Confirmed-transaction path | Custody or control model |
|---|---|
| Show funds on the confirmed EVM network | Self-custody under the same standard-account keys |
| Bridge from the confirmed network | Self-custody signs; bridge contracts control cross-chain settlement |
| Resolve an exchange deposit | Exchange custody controls the receiving address |
Read the confirmation as an execution plan
The confirmation screen is an execution plan that identifies the account, network, destination, balance change, and maximum network fee before signing.
Transaction identity and destination
The From field identifies the account whose nonce and balance will change. An EVM address contains 20 bytes and appears as 40 hexadecimal characters after the 0x prefix, making 42 visible characters in total. Match the full destination, not only its shortened rendering. For a token transfer, also confirm the contract asset and amount, because one network may host multiple assets with the same symbol.
Native-value transfers
A direct ETH transfer changes the sender and recipient balances on the selected chain. One ETH equals 1,000,000,000,000,000,000 wei, and a plain transfer to an externally owned account starts with an intrinsic 21,000-gas requirement. The wallet presents a readable amount, while the signed transaction carries the integer value in wei. Confirming on chain ID 8453 spends Base ETH; chain ID 1 spends Ethereum Mainnet ETH.
Contract calls and token movements
An ERC-20 transfer calls a token contract, while ERC-721 and ERC-1155 actions update ownership records in their respective contracts. The destination shown first may therefore be a contract rather than the final recipient encoded in calldata. Ethereum transaction simulations can display estimated balance changes for supported contract interactions, but they remain predictions until execution. Expand transaction details when the plain-language summary omits a field you need. A token with 6 decimals and another with 18 decimals can show similar human amounts while carrying different integers, so read the displayed asset and amount together.
The Network fee line is the estimated gas charge. Review its payment asset, gas limit, max fee, and priority fee, then return to the network label before pressing Confirm. On supported networks, gas-included transactions offer another eligible token as the payment asset; Metamask converts it to the chain’s required fee asset within that transaction. These checks tie the visible intent to one account on one chain.
Verify the state change on-chain
An on-chain receipt is the authoritative execution record that links the Metamask wallet activity entry to one network and block. A transaction hash is a 32-byte Keccak-256 value, displayed as 64 hexadecimal characters after 0x, or 66 characters overall. Open the activity entry, filter by network, and compare the hash, addresses, value, token transfers, block number, and receipt status. EIP-658 uses receipt status 1 for success and 0 for failure; a failed call still consumes gas. A successful ERC-20 transfer updates the token contract’s accounting on that chain.
Restore a balance shown on the wrong network
Wrong-network recovery is an account-visibility workflow when a confirmed EVM transfer reached an address controlled by the intended recipient on another chain. Start with the transaction hash and its chain, then enable that chain in Metamask and filter Tokens or Activity to it. The same standard account normally resolves to the same 20-byte address across EVM networks.
An absent token balance usually means either the network is not enabled or the token is not displayed. Add the token contract for that exact chain when automatic detection misses an ERC-20 asset; a contract address from Ethereum does not identify the corresponding token on Base or Arbitrum. Gas also belongs to the selected ledger: Base, Arbitrum One, and OP Mainnet use ETH, Polygon PoS uses POL, BNB Smart Chain uses BNB, and Avalanche C-Chain uses AVAX. Their chain IDs are 8453, 42161, 10, 137, 56, and 43114, respectively. A new send or bridge transaction then moves the recovered asset from where it actually exists.
Network mechanics beneath the wallet screen
EVM network mechanics are the signing and sequencing rules that make a selected chain, nonce, and fee determine transaction execution.
Chain-separated signatures
EIP-155 places the chain ID in the signed payload, so chain ID 1 and chain ID 8453 produce different signing contexts. EIP-1559 type-2 transactions also carry chain ID, nonce, maximum priority fee per gas, maximum fee per gas, gas limit, destination, amount, data, access list, and signature fields. Selecting another network therefore changes more than the asset filter. It changes the transaction that the account signs and the ledger that accepts it.
Nonces, fees, and pending replacements
An externally owned account starts with transaction nonce 0 and advances by 1 after each included transaction. A speed-up or cancellation competes with a pending transaction by reusing the same nonce and offering a fee the network prefers; once one replacement confirms, the others with that nonce cannot also execute. Under Ethereum’s EIP-1559 formula, a maximum-size block raises the next base fee by one-eighth, or 12.5%, before integer rounding, while the priority fee rewards the validator. Metamask estimates these values before confirmation. The receipt then closes the loop: it identifies the included transaction, its gas usage, and the state outcome on the selected chain.
Key questions about Metamask wallet
Does reinstalling the extension restore custom network settings?
Reinstalling the extension does not restore custom EVM network entries automatically. Add the network again with its correct chain ID, native-currency symbol, and RPC details, then filter the account view to that network. The balances never lived inside the extension, so reinstalling does not move them. A restored standard account reaches the same EVM address, while the interface needs the missing network configuration before it can query that ledger.
Which account should a Ledger user select on the recovered network?
A Ledger-connected account should use the same Ethereum-style address that received the funds on the unexpected EVM network. Reconnect the hardware account through Metamask, choose the matching account and derivation path, enable the relevant chain, and compare the full 42-character address. Base, Arbitrum One, and Polygon PoS use the same EVM address format. The hardware device still authorizes any new bridge or send transaction.
Why is an ERC-20 balance blank after the right network is enabled?
An ERC-20 balance stays blank when Metamask has not associated that chain’s token contract with the account view. Confirm the successful transfer on the correct explorer, then import the token contract address from that same network. The symbol and decimal count are display metadata; the token contract’s on-chain accounting holds the asset state. An Ethereum token contract address should not be substituted for a Base or Arbitrum token contract.
When does a pending transaction survive a network switch?
A pending transaction continues on the network where it was broadcast, even after the wallet displays another network. Return to the original chain, open Activity, and inspect the transaction hash and nonce. Speed-up and cancellation submit replacements with that same nonce; neither action moves the transaction to a new chain. Once the original or a replacement confirms, any bridge or resend starts as a separate transaction.
Where should an exchange deposit sent on an unsupported network be checked?
An unsupported exchange deposit should be checked on the block explorer for the network that actually confirmed it, then raised with the exchange that controls the receiving address. Metamask cannot expose or move assets from an address whose keys belong to the exchange. Provide the transaction hash, network, token contract, amount, and destination address. Credit or recovery depends on the exchange supporting that chain and handling the deposit internally.