Living on more than one chain

What changes when you cross a chain

The beginner guide to bridges covers why chains cannot see each other and how bridges work around it. Living across several chains adds practical differences you meet every day: each chain has its own gas token, its own identifier, and its own copy of every asset, at its own contract address.

Your balance on one chain is invisible from another. USDC on Base and USDC on Arbitrum are separate tokens that happen to share a name, and a wallet showing "USDC" is showing you the one on the network it is currently set to. Most multichain mistakes come from forgetting one of those facts at the wrong moment.

Canonical bridges and fast bridges

A rollup’s canonical bridge is its own set of contracts on Ethereum. Depositing locks assets there; withdrawing proves to those contracts that you burned the assets on the rollup. You are trusting the rollup itself: its proof system and whoever can upgrade it. L2BEAT grades exactly that with its stages framework. As of September 2026 it rates Arbitrum One, OP Mainnet and Base at Stage 1, and ZKsync Era and Linea at Stage 0, where operators still hold broad powers. The layer 2 directory and the guide to admin keys explain what the stages mean.

Third party bridges come in several designs. Liquidity networks hold pools on both chains. Intent based bridges let a relayer deliver your funds on the destination from its own capital and get repaid later: Across, for example, uses relayers repaid from pooled liquidity, with an optimistic oracle checking the claims. Messaging bridges lock an asset on one chain and mint a wrapped copy on the other. The expert guide to cross chain security sorts them by who verifies what.

Exit times, chain by chain

Deposits from Ethereum to a rollup are quick: Arbitrum’s docs put them at roughly 15 to 30 minutes. Withdrawals through the canonical bridge are where the waiting is.

Fast bridges exist because a week is expensive. Waiting seven days on $10,000 that could earn 5% a year costs about $9.59 in forgone yield, so a fee of 0.05% ($5) is cheaper than the wait, before counting the value of having the money when you need it (illustrative rates). The tradeoff is trust, and exposure to it lasts only while the transfer is in flight, which is why the beginner rule of moving in small tranches still applies.

Sources: OP Stack withdrawal flow, Base Beryl, and project pages on L2BEAT.

Native USDC, bridged copies and CCTP

A stablecoin is only as good as the claim behind it, and a bridged copy is a claim on a claim. On Arbitrum One there are two tokens a wallet may simply label USDC:

Circle launched native USDC on Arbitrum on June 8, 2023, and the bridged version still exists. The difference matters when you deposit to an exchange, which may credit only one of them, when you look for DeFi liquidity, and in a crisis, when the bridged copy depends on the bridge as well as on Circle. Check the contract address, not the label.

Circle’s Cross-Chain Transfer Protocol (CCTP) avoids bridged copies. It burns USDC on the source chain, Circle attests to the burn, and native USDC is minted on the destination. There is no wrapped token and no pool to drain. Version 2 launched on March 11, 2025, and according to Circle’s documentation it offers two speeds:

• Standard Transfer waits for the source chain to finalize, about 15 to 19 minutes from Ethereum and its layer 2s. Circle charges no fee beyond gas.
• Fast Transfer settles in seconds for a small fee that depends on the source chain: 1 basis point from Ethereum or Solana as of September 2026, so about $1 on $10,000, and more from some chains. Circle says fees are dynamic.

CCTP covers Ethereum, Solana, Arbitrum, Base, OP Mainnet, Polygon PoS, Avalanche and many more chains. Version 2 is now the canonical one: Circle plans to reduce the old version’s limits from October 31, 2026 and pause its contracts on December 1, 2026. You rarely call CCTP yourself; many wallets and bridge apps route USDC through it, and the better ones say so. For sending value to someone else, the transfer cost calculator shows how much the choice of chain changes the fee.

Keeping gas on every chain

A token with no gas beside it is stuck. You cannot swap, bridge or even send it without the chain’s own gas token, and that token differs: ETH on most Ethereum rollups, POL on Polygon PoS, BNB, AVAX, SOL.

• Keep a float. Enough for several transactions on every chain you use, including one exit.
• Withdraw gas directly. Many large exchanges can withdraw a gas token straight to a layer 2 or Solana, which skips a bridge.
• Take gas with you. Some bridges and aggregators offer to deliver a little of the destination gas token alongside a transfer.
• Pay in USDC where supported. Smart accounts with a paymaster can charge fees in a stablecoin; see smart accounts.
• Remember Solana token accounts. The first time an address receives a token, a token account has to be created for it, with a small refundable deposit in SOL paid by whoever creates it.

The gas tracker shows what a transaction costs right now.

Chain IDs, RPCs and adding networks

Every EVM chain has a numeric chain ID, and since EIP-155 it is part of what you sign, so a transaction signed for Base cannot be replayed on Ethereum. When a dapp offers to add a network, it uses a standard wallet request (EIP-3085) that proposes a name, a chain ID, an RPC URL and an explorer. Your wallet then sends everything through that RPC.

The RPC endpoint is not neutral. It sees your IP address and every address you query, and a malicious one can show you false balances or a fake transaction status, though it can never sign for you. Add networks from the chain’s official docs or a well known registry such as Chainlist, check the chain ID against the table above or the chain’s own docs, and be wary of a familiar name with an unfamiliar ID. Public RPCs are rate limited, so a wallet that feels broken may simply need a different endpoint.

One address everywhere, with one big exception

A plain wallet, an externally owned account, is derived from a private key, and the same key produces the same 0x address on every EVM chain. That is why sending to your own address on the wrong EVM chain is recoverable. Solana uses a different key type and encoding, so the same recovery phrase gives you a separate Solana address, and the two formats are never interchangeable.

The exception is a smart contract wallet. Its address comes from how it was deployed, not from a key. For a Safe, the Safe docs list the ingredients: the factory address, the singleton contract, the salt, the initialization data and the proxy code. Your Safe existing on Ethereum says nothing about whether it exists on Arbitrum.

The costly lesson came in 2022. The Optimism Foundation lent market maker Wintermute 20 million OP, sent on Optimism to the address of Wintermute’s Ethereum Safe, which had never been deployed on that chain. Wintermute’s account describes how an attacker replayed the old Safe deployment transactions from Ethereum and created Safes in batches until one landed on that address, then started selling the tokens. Newer Safes (version 1.3.0 and later) can now be deployed on another chain at the same address with an identical configuration, which is also the recovery route if funds land there by mistake.

Delegated addresses under EIP-7702 add a twist: the delegation is set chain by chain, but an authorization signed with chain ID 0 is valid on every chain that supports it. The guide to reading what you sign explains why that matters.

Sent to the wrong chain: what can come back

The wrong address guide walks through each case, including the published recovery fees of one major exchange.

A multichain checklist

• Name the bridge. Know whether a route is canonical or third party, and how long its exit takes.
• Check the token address. Native or bridged, on the chain you are on.
• Prefer native stablecoins. For USDC, a route that uses CCTP delivers the native token.
• Gas first. A float on every chain you hold anything on, plus ETH on Ethereum for claims.
• Official networks only. Chain ID and RPC from the chain’s own docs or a trusted registry.
• Contract wallets per chain. Deploy and test before receiving.
• Test, then send. A small transfer first, every time a route is new to you.

Common questions

Where to go next