Moving assets to Linea needs wallet prep, the official bridge, and a Lineascan balance check. Most transfers finish in about 5 to 15 minutes for beginners and intermediate users who keep ETH for gas
Transferring ETH or ERC-20 tokens into Linea is a routine Layer 2 move for users who want lower fees while staying inside the Ethereum ecosystem. Linea is a zkEVM network built with support from Consensys, and it uses ETH as its only gas token. For U.S. readers who already hold assets on Ethereum or another EVM chain, the practical path is straightforward: prepare a self-custodial wallet, use the official bridge interface, confirm the source-chain transaction, then verify the destination balance on Lineascan.
The full flow usually takes about 5 to 15 minutes when networks are not congested. It does not require advanced development skills, but it does require careful URL checks, enough gas on the source chain, and confirmation that the destination token contract matches what you expect. Bridging does not distribute the LINEA token, and gas on Linea remains ETH only.
Wallet and Network Setup
Before opening any bridge page, confirm four basics: an EVM-compatible wallet such as MetaMask, funds and gas on the source network, the correct Linea Mainnet parameters, and the official bridge URL. Linea Mainnet uses Chain ID 59144. The block explorer is lineascan.build, and transaction fees on Linea are paid in ETH.
Many wallets already list Linea Mainnet. If the network is missing, add it manually with Network Name Linea Mainnet, Chain ID 59144 (hex 0xe708), Currency Symbol ETH, and the Lineascan explorer URL. RPC endpoints from Infura and other Consensys-related services are commonly used. After the network appears, switch to it once so the wallet can display Linea balances later.
Keep a small ETH buffer on the source chain for bridge fees and any approval transactions. Users who skip this step often stall mid-transfer when the wallet cannot pay gas. As with other rollups compared in broader Ethereum scaling discussions, bridge cost and speed depend heavily on source-chain gas and the bridge contracts involved, not only on Linea fees.
Using the Official Bridge
Open the official interface at bridge.linea.build, or reach it through linea.build/bridge. Before connecting a wallet, check that the browser address bar shows a linea.build subdomain. Unverified search results and chat links remain a common phishing vector for bridge users.
Connect the wallet, then choose a route. The All Bridges aggregator is the option most users pick because it lets them select the source network, set Linea as the destination, pick the token, and enter an amount. Native Bridge is intended for canonical Ethereum to Linea transfers. Review the quoted route, fees, and estimated arrival window, then confirm the transaction in the source network wallet.
After the source transaction confirms, wait for the bridge path to complete. Typical bridging of ETH or ERC-20 tokens into Linea finishes in roughly 5 to 15 minutes under normal conditions. Do not close the wallet or switch networks until the source confirmation is finished, and do not send a second transfer while the first is still pending unless you understand the risk of duplicate sends.
Verify on Lineascan
When the bridge reports completion, open lineascan.build, search your wallet address on Linea Mainnet, and confirm that the ETH balance or the target ERC-20 balance increased. Also check the token contract address against a trusted source before interacting with any newly received asset. A matching balance on Lineascan is the practical proof that funds arrived.
Common failures include wrong URLs, incorrect network parameters, insufficient source gas, and skipping the explorer check. If funds do not appear after the expected window, recheck the source transaction hash, confirm you are viewing Linea Mainnet rather than another chain, and verify that the destination address matches the wallet you control.
Official bridge tooling on bridge.linea.build supports both Native Bridge and All Bridges. Security still depends on user behavior. Phishing sites, malicious token contracts, and rushed approvals remain the main risks. Testing with a small amount first is a practical habit for anyone moving larger balances.
Linea Mainnet is identified by Chain ID 59144, uses ETH exclusively for gas, and is monitored through lineascan.build. The documented user path is a five-stage sequence: confirm the official URL, prepare the wallet and source funds, add and activate Linea Mainnet, select and confirm a route on bridge.linea.build, then verify the destination balance and token contract on Lineascan. That sequence is aimed at beginner-to-intermediate users and does not require deep protocol knowledge when official interfaces are used carefully.
Cross-chain bridges move value by locking or burning assets on one network and minting or releasing representations on another, which means users temporarily rely on bridge contracts, message-passing systems, and correct destination parameters. A successful source-chain confirmation does not by itself prove final receipt until the destination explorer shows the balance. For U.S. users, that distinction matters for recordkeeping, tax lots, and recovery if a transfer stalls. Self-custody wallets keep private keys with the user, so recovery depends on seed-phrase backups rather than customer support. Bridge interfaces can also surface multiple routes with different fees, latency, and trust assumptions, which is why checking the official Linea domain, confirming Chain ID 59144, and validating token contracts on Lineascan remain core controls even when the transfer itself looks simple.
