How to bridge to Linea? (Consensys L2)

Understanding Linea's Bridge Architecture

1. Linea operates as an Ethereum Layer 2 using zero-knowledge rollup technology developed by Consensys.

2. Its native bridge is permissionless and fully trustless, relying on cryptographic proofs rather than external validators or multisig signers.

3. The bridge supports bidirectional transfers between Ethereum Mainnet and Linea for ETH and ERC-20 tokens that are already deployed on both chains.

4. All bridging logic resides in audited smart contracts verified on Etherscan and LineaScan, with public repositories hosted on GitHub.

5. No centralized relayer infrastructure is required — message passing occurs through Ethereum’s canonical state root verification process.

Step-by-Step Bridging Process

1. Users must connect a Web3 wallet such as MetaMask to the Ethereum Mainnet network.

2. Navigate to the official Linea bridge interface at bridge.linea.build and ensure the connected network is Ethereum Mainnet.

3. Select the token to transfer, enter the amount, and click “Deposit” — this initiates a transaction on Ethereum requiring gas payment.

4. After confirmation on Ethereum, the system queues the deposit; finality occurs once the corresponding zk-proof is verified on Linea, typically within 10–20 minutes.

5. Once finalized, the equivalent balance appears in the same wallet address on Linea, now accessible via MetaMask after adding the Linea network manually or using ChainList.

Security Considerations and Verification

1. Every deposit triggers a Merkle inclusion proof stored on-chain, allowing independent verification of asset movement.

2. Withdrawals require waiting for a challenge period unless using fast-withdrawal services provided by third-party liquidity providers.

3. Users should never input seed phrases or private keys into any bridge interface — legitimate Linea tools never request them.

4. Contract addresses for the bridge have been audited by OpenZeppelin and CertiK, with reports publicly available on the Linea documentation site.

5. Reentrancy guards, access control modifiers, and strict input validation are implemented across all bridge contract functions.

Supported Tokens and Deployment Requirements

1. ETH is natively supported without additional configuration due to its role as Linea’s base currency.

2. ERC-20 tokens require deployment on Linea first — users or token teams must deploy identical bytecode with matching constructor parameters.

3. Only tokens with verified Linea deployments appear in the bridge’s token selector — unverified contracts will not show up.

4. Token bridging requires two separate transactions: one on Ethereum to lock assets and another on Linea to mint equivalents.

5. Some tokens may enforce minimum deposit thresholds or disable bridging entirely based on governance decisions made by their respective teams.

Frequently Asked Questions

Q: Can I bridge NFTs to Linea?A: No, the native Linea bridge does not support NFTs. Only fungible ERC-20 tokens and ETH are supported.

Q: Why does my transaction remain pending after sending ETH to the bridge?A: This usually indicates insufficient gas on Ethereum Mainnet or network congestion. Check the transaction hash on Etherscan to confirm if it was mined.

Q: Do I need to approve the token contract before bridging an ERC-20?A: Yes, approval is mandatory for each ERC-20 token prior to the first deposit. Subsequent deposits do not require re-approval unless the allowance is exhausted.

Q: Is there a fee for bridging from Ethereum to Linea?A: Yes, users pay Ethereum gas fees for the initial deposit transaction. There are no additional bridge service fees imposed by Consensys.