Ethereum mainnet gas fees can still hit several dollars for a routine swap during busy hours. Layer 2 rollups like Base, Arbitrum, and Optimism now handle the same transaction for a few cents. As of August 16, 2026, L2BEAT put total value locked across Ethereum’s layer 2 networks at $26.555 billion, led by Base at $11.42 billion and Arbitrum One at $10.11 billion. If you’re still paying mainnet gas for every trade, mint, or contract call, you’re leaving money on the table.

This tutorial walks through setting up a wallet for layer 2 scaling, bridging funds from Ethereum mainnet to Base, Arbitrum, Optimism, zkSync Era, and Starknet, and verifying every transaction along the way. You’ll finish with a working multi-chain setup, a fee-comparison table you can reference before every bridge, and a troubleshooting list built from the errors people actually hit. Budget about 45 minutes for the full walkthrough, plus a few minutes waiting on bridge confirmations.

What is layer 2 scaling, and why it matters in 2026

Layer 2 (L2) scaling means moving transaction execution off Ethereum mainnet (layer 1) onto a secondary network that periodically posts compressed proof data back to layer 1 for security. Ethereum mainnet stays as the settlement and data-availability layer; the L2 does the heavy lifting of processing thousands of transactions cheaply. Two dominant designs exist today: optimistic rollups (Arbitrum, Optimism, Base) and zero-knowledge rollups (zkSync Era, Starknet, Linea).

Optimistic rollups assume transactions are valid by default and give a challenge window for anyone to submit fraud proofs if something’s wrong. ZK rollups instead generate a cryptographic proof (a validity proof) for every batch, so there’s no waiting period for challenges, just a proof-generation cost. That’s why ZK rollups like zkSync Era (around $0.05 per simple transfer) tend to run a touch more expensive than optimistic ones like Base ($0.02), even though both are dramatically cheaper than mainnet.

According to a February 2026 comparative study from CoinBureau, Arbitrum One processes roughly 4.3 million daily transactions and around 129,000 daily active users, with a median “send ETH” fee near $0.0044 post-Dencun upgrade. That’s not a marginal improvement over mainnet, it’s a different cost structure entirely. A January 2026 gas-fee guide from Coinpaprika notes layer 2 rollups cut transaction costs by 90-99% compared to mainnet, with Base charging around $0.02 per transfer and Arbitrum around $0.04.

Much of that cost drop traces back to Ethereum’s Dencun upgrade, which introduced proto-danksharding through EIP-4844. Before Dencun, rollups posted full transaction data to mainnet as calldata, a genuinely expensive operation. After Dencun, rollups post that same data as “blobs,” a cheaper, temporary storage format designed specifically for L2 data availability. That single change is the biggest reason sub-cent and low-cent transfers became the norm across major rollups rather than the exception, and it’s part of why the fee gap between mainnet and L2 widened so sharply through 2025 and into 2026.

Optimistic rollups vs. ZK rollups: the security tradeoffs

Both rollup families inherit Ethereum’s base-layer security for data availability, but they get there through different mechanisms, and that difference shapes how you should think about risk. Optimistic rollups publish a batch of transactions and simply assume it’s correct. Anyone watching the chain has a window, usually measured in days, to submit a fraud proof if they spot an invalid state transition. If nobody challenges it, the batch finalizes as valid. It’s a pragmatic design: cheap to run, but it needs that challenge window before withdrawals to mainnet are considered final.

ZK rollups take a different path. Every batch ships with a cryptographic validity proof, generated off-chain and verified on-chain, that mathematically demonstrates the new state follows correctly from the old one given the included transactions. There’s no need for a challenge window because the proof itself is the guarantee. The tradeoff is computational: generating those proofs costs real money and time, which is why zkSync Era and Starknet transfers tend to run a few cents higher than Base or Arbitrum for equivalent actions.

L2BEAT tracks a separate dimension worth understanding before you bridge meaningful funds: decentralization stage. Rollups are commonly rated from Stage 0 (a centralized sequencer and a security council that can override the system, sometimes called “training wheels”) up toward Stage 2 (fully trustless, no admin key can freeze or alter user funds). CoinBureau’s February 2026 study lists Arbitrum One at L2BEAT Stage 1, meaning fraud proofs are live but some centralized safeguards remain. Check a network’s current stage on L2BEAT before treating it as equivalent in trust assumptions to holding assets on Ethereum mainnet itself, since even the largest L2s aren’t uniformly at the most decentralized stage yet.

Prerequisites: what you need before you start

Layer 2 bridging doesn’t require specialized hardware, but a few things need to be in place first. Skipping any of these is the most common reason a bridge transaction fails or funds end up stuck.

  • A self-custody wallet. MetaMask (browser extension, version 12.x or later) or Coinbase Wallet (mobile/extension, latest version from the official store). Avoid exchange wallets, since exchanges rarely support direct L2 withdrawals to every network.
  • ETH on Ethereum mainnet. At least 0.02-0.05 ETH to cover mainnet gas for the bridge deposit itself, plus whatever amount you intend to move.
  • A secured seed phrase backup. Written down offline, never photographed or typed into a password manager connected to the internet. This matters more once you’re managing balances across five networks instead of one.
  • A block explorer bookmark for each L2. Arbiscan (Arbitrum), Basescan (Base), Optimism’s Etherscan instance, the zkSync Era Explorer, and Starkscan (Starknet). You’ll use these to confirm bridge deposits actually landed.
  • Patience for the withdrawal path. Optimistic rollups (Arbitrum, Optimism, Base) enforce a challenge window, typically around seven days, for withdrawals back to mainnet. ZK rollups don’t need this, but they still take longer than a deposit.

Step 1: Install and secure your wallet

If you don’t already have MetaMask installed, get it only from metamask.io or your browser’s official extension store, never from a search ad or a link in a Discord message. Set a strong password, write your 12-word seed phrase on paper (not a screenshot, not cloud storage), and store it somewhere offline. If you already have a wallet, skip to Step 2, but take thirty seconds to confirm your extension is up to date, since old versions sometimes miss new network presets.

Once your wallet exists, fund it with a small amount of ETH on mainnet from an exchange or another wallet you control. You don’t need much yet, just enough to cover the first bridge transaction’s gas.

Step 2: Add the layer 2 networks to your wallet

MetaMask ships with Arbitrum, Optimism, and Base as one-click presets under Settings → Networks → Add a network → popular networks. For zkSync Era and Starknet, you’ll add custom RPC details manually. Here’s the exact configuration for each network as of August 2026:

// Base Mainnet
Network Name: Base
RPC URL: https://mainnet.base.org
Chain ID: 8453
Currency Symbol: ETH
Block Explorer: https://basescan.org

// Arbitrum One
Network Name: Arbitrum One
RPC URL: https://arb1.arbitrum.io/rpc
Chain ID: 42161
Currency Symbol: ETH
Block Explorer: https://arbiscan.io

// OP Mainnet (Optimism)
Network Name: OP Mainnet
RPC URL: https://mainnet.optimism.io
Chain ID: 10
Currency Symbol: ETH
Block Explorer: https://optimistic.etherscan.io

// zkSync Era Mainnet
Network Name: zkSync Era Mainnet
RPC URL: https://mainnet.era.zksync.io
Chain ID: 324
Currency Symbol: ETH
Block Explorer: https://explorer.zksync.io

Paste each block into MetaMask’s “Add network manually” form one field at a time. Double-check the Chain ID field specifically, a typo here is the single most common setup mistake and it silently breaks transaction signing later.

Step 3: Compare current L2 fees before you commit funds

Fees shift with network congestion and Ethereum blob prices, but the relative ordering has held steady through mid-2026. A late-August 2026 fee analysis from HOGE Wire describes major rollups clustering “from well under a cent to a few cents” for a simple transfer, with swaps and contract calls costing several times more. Use this table as a starting reference, then check L2BEAT’s live fee tracker before a large transfer.

NetworkTypeTVL (Aug 16, 2026)Simple transfer feeBest for
BaseOptimistic rollup$11.42B~$0.02Cheapest transfers, Coinbase on-ramp
Arbitrum OneOptimistic rollup$10.11B~$0.04Deepest DeFi liquidity
OP MainnetOptimistic rollup$1.41B~$0.03Optimism Superchain apps
LineaZK rollup~$415M~$0.04Consensys/MetaMask integration
zkSync EraZK rollup~$404M~$0.05Native account abstraction
StarknetZK rollup (Cairo VM)~$579MvariesComplex on-chain logic

Note the concentration: Arbitrum One, Base, and OP Mainnet together account for roughly 71.7% of total L2 TVL, according to a July 2026 report from Gate Web3 that put aggregate L2 value at $42.04 billion. The other 50-plus tracked networks split the remaining share. That concentration is worth knowing before you assume every L2 has deep liquidity for the token you’re trading.

Choosing the right L2 for your use case

Not every L2 fits every activity equally well. Liquidity depth, ecosystem tooling, and finality speed vary enough between networks that picking the “cheapest” one isn’t always the right call. If you’re trading actively, you want the deepest order books and the most DEX integrations, which still points to Arbitrum One given its dominant share of DeFi TVL. If you’re minting NFTs or using a consumer app tied to Coinbase’s ecosystem, Base usually has the most direct on-ramp and the lowest friction. If you’re building or using an application that needs native account abstraction, smart accounts that can batch transactions or sponsor gas, zkSync Era’s validity-proof architecture was designed with that in mind from the ground up.

Use caseRecommended networkWhy
Active DeFi tradingArbitrum OneDeepest liquidity, most DEX integrations
Consumer apps, payments, NFTsBaseLowest fees, Coinbase on-ramp
Smart accounts, gas sponsorshipzkSync EraNative account abstraction support
Complex on-chain logic, gamingStarknetCairo VM built for compute-heavy apps
MetaMask-native workflowsLineaBuilt and maintained by Consensys

None of this is fixed. Fee rankings and liquidity depth shift as networks upgrade and as capital rotates, which is exactly why the checklist in this tutorial has you bookmark L2BEAT rather than memorize a single snapshot. Treat the table above as a starting point for August 2026, not a permanent ranking.

Step 4: Choose your bridging method

You have two practical options: the official native bridge for each L2, or a bridge aggregator that routes across multiple protocols. Native bridges are the safer default for a first-time move because they’re maintained directly by the L2 team and audited as part of the core protocol. Aggregators (routing through several underlying bridge protocols) can be faster and sometimes cheaper for L2-to-L2 transfers, but they add a layer of third-party contract risk.

For this tutorial, use the official bridge for your first deposit on each network. Once you’re comfortable, aggregators are fine for moving funds between L2s without routing back through mainnet.

Step 5: Bridge ETH from mainnet to Base

Go to bridge.base.org and connect your wallet. Select Ethereum mainnet as the source and Base as the destination. Enter the ETH amount, review the estimated gas (this is a mainnet transaction, so expect the usual mainnet fee here), and confirm. Deposits to Base typically confirm within a few minutes since Base’s deposit path doesn’t require the challenge window that withdrawals do.

1. Open bridge.base.org
2. Connect wallet (MetaMask/Coinbase Wallet)
3. From: Ethereum Mainnet   To: Base
4. Enter amount, e.g. 0.05 ETH
5. Review gas estimate, confirm in wallet
6. Wait for mainnet confirmation (~1-3 min)
7. Wait for Base-side credit (~1-5 min)
8. Verify balance: switch wallet network to Base

Once the deposit posts, switch your wallet’s active network to Base and confirm the balance shows up. If it doesn’t appear within ten minutes, don’t resend the transaction, check Basescan first (Step 8 covers this). Resending a “stuck” deposit before checking the explorer is a common way people end up with two deposits instead of one, which isn’t dangerous but does mean double the mainnet gas spent for no reason.

If you’re moving a larger amount for the first time, consider a two-step approach: send a small test amount first (0.005-0.01 ETH), confirm it lands correctly and that you can see it in both your wallet and Basescan, then send the rest. It costs a little extra in mainnet gas for the second transaction, but it removes any doubt about whether your wallet configuration, RPC endpoint, and bridge contract interaction are all working correctly before you commit meaningful funds.

Step 6: Bridge to Arbitrum and Optimism

The process mirrors Base. For Arbitrum, use the bridge linked from the official Arbitrum documentation; for Optimism, use the Superchain bridge linked from the Optimism docs. Both follow the same pattern: connect wallet, select source and destination, enter amount, confirm, wait for the deposit to post.

One difference worth flagging: Arbitrum’s bridge UI sometimes defaults to Arbitrum Nova (the lower-cost, lower-security AnyTrust chain) instead of Arbitrum One (the main optimistic rollup). Check the destination network name before confirming, since funds sent to the wrong Arbitrum variant require a separate bridge transaction to move.

Optimism’s Superchain bridge is worth understanding on its own terms, since Optimism’s architecture underpins a family of chains beyond just OP Mainnet, including Base itself. That shared technology stack (the OP Stack) is part of why bridging patterns feel so similar across Base and OP Mainnet, they’re built from the same underlying framework, even though they’re operated by different teams with separate governance. If you’re bridging to a newer OP Stack chain beyond the big three, double-check that chain’s official bridge link directly from its own documentation rather than trusting a search result, since OP Stack’s growing ecosystem has made it a target for phishing sites that mimic legitimate chain names.

Step 7: Bridge to zkSync Era and Starknet

ZK rollups use a different underlying proof system, but the bridging UX is nearly identical from a user’s perspective. For zkSync Era, use the official bridge linked from zksync.io. For Starknet, use the bridge linked from starknet.io, which requires a Starknet-compatible wallet (such as Argent X or Braavos) in addition to MetaMask, since Starknet’s account model differs from standard EVM chains.

// Starknet wallet setup (required before bridging)
1. Install Argent X or Braavos browser extension
2. Create a new Starknet account (separate from your MetaMask seed)
3. Fund the Starknet wallet address via starknet.io bridge
4. Confirm receipt in the Argent X/Braavos interface
5. Cross-verify on Starkscan using your account address

This is the step people most often get wrong: assuming Starknet works like every other EVM-compatible L2 and trying to bridge directly into MetaMask. Starknet isn’t EVM-equivalent at the account level, so you need a dedicated wallet before funds arrive.

Step 8: Verify every deposit on a block explorer

Don’t trust the wallet balance display alone, especially on your first few bridges. Copy your wallet address, paste it into the relevant block explorer (Basescan, Arbiscan, Optimism’s Etherscan instance, the zkSync Era Explorer, or Starkscan), and confirm the incoming transaction shows a “Success” status with the expected amount. This takes thirty seconds and catches the rare case where a deposit is still pending or was sent to the wrong chain ID.

Step 9: Set up a bridge aggregator for L2-to-L2 transfers

Once you’re holding funds across multiple L2s, moving between them directly (without routing back through mainnet) saves both time and fees. Bridge aggregators evaluate routes across several underlying protocols and pick the cheapest or fastest path automatically. To use one: connect your wallet, select source L2 and destination L2, enter the amount, and let the aggregator quote a route before you confirm. Always check the quoted output amount against the input, a route with unusually high slippage is a sign to try a different aggregator or wait for less congestion.

Step 10: Track balances and fees across all your networks

Managing five separate networks manually gets tedious fast. MetaMask’s portfolio view aggregates balances across added networks, but for a fuller picture, L2BEAT’s dashboard tracks total value secured, activity, and risk ratings for every tracked L2 in one place. Bookmark it and check it before moving any meaningful amount, since TVL and risk profiles shift; a July 2026 CryptoDaily analysis noted aggregate L2 value secured dropped to around $33.77 billion, a two-year low at that point, driven partly by methodology changes and capital rotation rather than a single event.

It’s also worth keeping a simple personal spreadsheet or note tracking which assets live on which network, separate from any wallet UI. Wallet apps are good at showing what’s on the currently selected network, but poor at giving you a single glance across five chains at once. A basic log, network, asset, amount, date bridged, saves real time later when you’re deciding where to deploy funds next or reconciling balances for tax purposes.

Step 11: Withdraw funds back to mainnet

Withdrawals are where optimistic and ZK rollups diverge most. On Arbitrum, Optimism, and Base, initiating a withdrawal starts a challenge period, commonly around seven days, during which the transaction can theoretically be disputed before funds finalize on mainnet. ZK rollups like zkSync Era and Starknet don’t need this window because the validity proof already mathematically confirms correctness, so withdrawals finalize faster, typically within hours once the batch containing your withdrawal is proven and posted.

Plan withdrawals accordingly. If you need mainnet liquidity urgently from an optimistic rollup, a third-party “fast withdrawal” liquidity provider can front you the funds for a fee, skipping the wait, but that introduces counterparty risk you don’t have with a standard withdrawal.

Step 12: Build a routine for ongoing L2 use

Once your wallet is configured across Base, Arbitrum, Optimism, zkSync Era, and Starknet, the workflow settles into a routine: keep a small mainnet ETH balance for occasional bridging, hold your working capital on whichever L2 has the app or liquidity you need, and check L2BEAT or a block explorer before any transaction over a few hundred dollars. Revisit your network list every few months, since new L2s launch regularly and fee rankings shift as networks upgrade their data-availability approach.

Common pitfalls when setting up layer 2 scaling

  • Bridging to the wrong chain variant. Arbitrum One vs. Arbitrum Nova is the classic mix-up. Always confirm the destination chain ID before signing.
  • Sending funds directly to an exchange deposit address on an L2 the exchange doesn’t support. Not every exchange supports every L2 for deposits; check first or funds can be unrecoverable.
  • Assuming Starknet works like an EVM chain. It requires a separate account model and wallet (Argent X or Braavos), not standard MetaMask.
  • Underestimating the withdrawal challenge window. Planning to move funds off Arbitrum, Optimism, or Base back to mainnet in a hurry, then hitting the roughly seven-day wait, unprepared.
  • Ignoring gas token requirements on the destination chain. Some L2 interactions (beyond a simple transfer) need a small ETH balance already on that L2 to pay for the transaction itself, not just the bridged asset.
  • Using an aggregator quote that’s gone stale. Route quotes can expire in volatile markets; re-quote if more than a minute or two has passed before confirming.
  • Skipping block explorer verification. Trusting a wallet’s cached balance display instead of confirming the transaction status directly.

Example output: what a successful bridge confirmation looks like

After a Base deposit completes, Basescan should show a transaction record similar to this:

Status: Success
Block: 24,681,204
Timestamp: Aug-24-2026 14:32:07 UTC
From: 0xYourWalletAddress
To: Base Standard Bridge (0x3154Cf...)
Value: 0.05 ETH
Transaction Fee: 0.0000021 ETH (~$0.02)
Method: depositTransaction

If the status shows “Pending” for more than 15-20 minutes, or the “Method” field looks unfamiliar, stop and check the troubleshooting section below before taking further action.

Layer 2 network comparison at a glance

FeatureBaseArbitrum OnezkSync Era
Rollup typeOptimisticOptimisticZK (validity proof)
Withdrawal to mainnet~7-day challenge window~7-day challenge windowHours (proof-based)
Wallet compatibilityStandard EVM (MetaMask)Standard EVM (MetaMask)Standard EVM (MetaMask)
Native ecosystem tieCoinbaseOffchain LabsMatter Labs
Typical use caseConsumer apps, paymentsDeFi, deep liquidityAccount abstraction apps

Security checklist before you bridge large amounts

The steps above work fine for small test amounts, but treat any bridge transfer above what you’d be comfortable losing as a higher-stakes action deserving extra checks. Bridge contracts, even official ones, are a common target for phishing sites that clone the real interface pixel-for-pixel and swap out the destination contract address. Before confirming a large deposit, run through this list.

  • Type the URL manually or use a bookmark you saved earlier, rather than clicking a link from search results, social media, or a direct message. Fake bridge sites regularly outrank or impersonate official ones in ad placements.
  • Confirm the contract address MetaMask shows you matches the official one listed in the network’s own documentation, not just what the website displays, since a compromised front-end can show correct-looking text while pointing at a malicious contract.
  • Never approve an “unlimited” token allowance for a bridge or dApp you’re using for the first time if the interface offers a choice; approve only the amount you’re actually moving.
  • Split very large transfers into two or more transactions across separate sessions, so a single compromised signature doesn’t expose your entire balance.
  • Double-check you’re not connected to a testnet that shares a similar name to the mainnet you intend to use; MetaMask’s network selector sometimes lists both side by side.

None of this is unique to layer 2 bridging, the same discipline applies to any on-chain transaction, but the novelty of managing five networks instead of one makes it easier to let your guard down on autopilot. Slow down specifically on the bridge step; it’s the single transaction type most frequently targeted by phishing infrastructure in the current threat landscape.

Advanced tips for reducing costs further

Batch your mainnet-to-L2 bridge deposits instead of sending small amounts repeatedly; each deposit pays a full mainnet gas fee regardless of size, so one $500 deposit costs the same base gas as one $50 deposit. Time large bridge transactions for periods of lower mainnet congestion, typically weekends or outside US/EU business hours, since the mainnet leg of your bridge transaction is still subject to normal gas auctions. When moving between two L2s, compare a direct aggregator route against bridging back to mainnet and out again; for larger amounts, mainnet round-trips are sometimes cheaper in total despite the extra step, because L2-to-L2 aggregator routes can carry a liquidity premium.

If you interact with contracts frequently on a given L2, keep a slightly larger-than-minimum ETH balance there. Running a balance to zero mid-transaction is a common way first-time L2 users get stuck unable to pay for a follow-up transaction, like an approval, right after a swap.

Watch blob-price conditions on Ethereum mainnet, too. Since Dencun, L2 fees are tied to the cost of posting blob data, which fluctuates with mainnet demand for blob space, not just mainnet gas itself. During periods when blob demand spikes (large NFT drops, major protocol launches with heavy L2 activity), even the cheapest rollups can see their transfer fees creep up temporarily. It’s a smaller effect than mainnet gas volatility, but it’s not zero, and it explains why fee figures you see quoted for Base or Arbitrum can drift day to day rather than staying perfectly fixed.

Troubleshooting layer 2 bridging issues

  • Deposit shows on mainnet but not on the L2: Check the block explorer for the destination chain directly; L2 credit can lag the mainnet confirmation by several minutes during congestion.
  • MetaMask shows a zero balance after adding a network: Confirm the Chain ID matches exactly; a wrong Chain ID silently points MetaMask at the correct network’s RPC but the wrong internal chain reference.
  • Transaction stuck as “Pending” for over an hour: Check whether you set a gas price too low during network congestion; most wallets allow speeding up a pending transaction by resubmitting with higher gas.
  • Bridged funds don’t appear in Starknet wallet: Confirm you’re checking the Argent X/Braavos wallet, not MetaMask; Starknet balances don’t show in standard EVM wallets.
  • Aggregator quote fails at confirmation: The quote likely expired due to price movement; request a fresh quote rather than retrying the stale one.
  • Withdrawal to mainnet seems to have vanished: On optimistic rollups, this is expected during the challenge window; check the bridge’s “claim” or “finalize” step once the window closes, since some withdrawals require a manual claim transaction.
  • Gas estimate on Arbitrum looks unusually high: Confirm you’re not accidentally connected to Arbitrum Nova or a testnet; double-check the network name in your wallet’s network selector.
  • Can’t find your token on a new L2 despite bridging correctly: Some tokens require adding the contract address manually per network, since token contract addresses differ between mainnet and each L2 (they are not automatically the same address).

Complete working setup: reference checklist

Here’s the full setup condensed into a single reference you can follow start to finish:

[ ] MetaMask installed, seed phrase backed up offline
[ ] Mainnet ETH funded (0.05+ ETH recommended)
[ ] Base, Arbitrum, OP Mainnet added via MetaMask presets
[ ] zkSync Era added via manual RPC entry
[ ] Argent X or Braavos installed for Starknet
[ ] Bridged 0.02-0.05 ETH to Base via bridge.base.org
[ ] Bridged 0.02-0.05 ETH to Arbitrum via bridge.arbitrum.io
[ ] Bridged 0.02-0.05 ETH to Optimism via app.optimism.io/bridge
[ ] Bridged to zkSync Era via zksync.io official bridge
[ ] Bridged to Starknet via starknet.io official bridge
[ ] Verified every deposit on its respective block explorer
[ ] Bookmarked L2BEAT for ongoing fee/TVL monitoring

With that checklist complete, you have a working multi-chain wallet spanning the five largest Ethereum L2s by combined value, ready for everyday transactions at a fraction of mainnet cost.

Frequently asked questions

Is bridging to a layer 2 network safe?

Official native bridges (bridge.base.org, bridge.arbitrum.io, the Optimism Superchain bridge) are maintained by the core teams behind each rollup and are the safest first option. Third-party aggregators add convenience but also add smart contract risk from the additional protocols they route through.

Which layer 2 network has the lowest fees right now?

Base has generally run the cheapest of the large general-purpose rollups for simple transfers, around $0.02, based on fee data referenced in a late-August 2026 fee analysis. Arbitrum and Optimism sit close behind at a few cents.

How long does a withdrawal from Arbitrum or Optimism to mainnet take?

Typically around seven days, due to the challenge window built into optimistic rollup security. This is a design tradeoff, not a bug, it’s what lets these networks avoid the cost of validity proofs on every transaction.

Do I need a different wallet for every layer 2 network?

No, for EVM-compatible L2s (Base, Arbitrum, Optimism, zkSync Era, Linea), MetaMask or Coinbase Wallet works across all of them once you add each network. Starknet is the exception, it needs a Starknet-native wallet like Argent X or Braavos.

Why did my layer 2 TVL numbers look different between two sources?

Total value locked (TVL) and total value secured (TVS) are measured differently, and methodology changes have caused reported figures to swing meaningfully in 2026. Treat any single TVL figure as a snapshot, not an absolute, and check L2BEAT directly for the current number.

Can I lose funds if I bridge to the wrong network?

Funds sent to a valid address on the wrong EVM-compatible chain are usually recoverable by bridging back out, since the address format is the same. Funds sent to a fundamentally different account model, such as attempting to bridge directly into a non-Starknet wallet on Starknet, can be far harder or impossible to recover. Always verify the destination network before confirming.

Are zkSync Era and Starknet fees always higher than optimistic rollups?

Generally yes, slightly, because generating a validity proof costs more than an optimistic rollup’s simpler batching. Fee data from August 2026 puts zkSync Era around $0.05 for a simple transfer versus roughly $0.02-0.04 for Base and Arbitrum, though the gap has narrowed as proof systems have become more efficient.

How often should I check L2 fee and TVL data before moving funds?

For routine transfers under a few hundred dollars, a periodic check (monthly) is plenty. For larger transactions, check L2BEAT’s live dashboard immediately before bridging, since fees and network conditions can shift within hours during periods of high mainnet congestion.

What happened to Polygon and other older L2 and sidechain options?

Older scaling networks that predate the rollup-centric era, Polygon PoS being the best-known example, still operate, but the ecosystem’s center of gravity has shifted firmly toward Ethereum-secured rollups like Base, Arbitrum, and Optimism. If you hold assets on an older sidechain, it’s worth periodically checking L2BEAT’s classification, since not every “layer 2” branded network uses the same security model, and some rely on separate validator sets rather than Ethereum’s own security guarantees.

Do I need to report layer 2 bridging for taxes?

Tax treatment of bridging varies by jurisdiction, and this tutorial isn’t tax advice. Generally, moving your own asset from mainnet to an L2 you control isn’t a taxable disposal in most frameworks, since you still own the same underlying asset, just on a different network. Keep records of bridge transactions regardless, including dates, amounts, and transaction hashes, and confirm the specifics with a tax professional familiar with your jurisdiction’s crypto rules.