Before you start
You'll need three things: a multi-chain wallet, some crypto on the source chain, and the native gas token of the source chain (on Ethereum that's ETH, on Polygon it's POL). If you're starting from a US exchange account, our wallet guide covers the funding path in detail.
Step 1 — Set up a multi-chain wallet
Install a wallet that speaks EVM: MetaMask, Rabby or Coinbase Wallet all work. Write the recovery phrase on paper — never in a screenshot, cloud note or password manager shared across devices. The wallet will show one address (0x…) that works across all EVM chains; the networks are just different views of the same account.
Step 2 — Fund the source chain
Buy or transfer your starting asset onto the chain you're bridging from. A common US path: buy USDC or ETH on a major exchange, withdraw to your wallet address, and choose the cheapest network the exchange supports for that withdrawal — often directly Arbitrum or Base, skipping mainnet gas entirely.
Step 3 — Open the bridge interface and connect
Open the aggregator's website — by bookmark you saved yourself, never by clicking a search ad or a Discord link (see our security guide for why). Click "Connect Wallet", pick your wallet, and confirm the connection prompt. Connecting shares your address; it cannot move funds.
Step 4 — Set the route
Pick the source chain and token, the destination chain and token, and the amount. If you want to sanity-check the market before touching the interface, run the same route through our liquidity calculator first — the numbers should be in the same ballpark.
Step 5 — Read the quote like an underwriter
Before signing, check four numbers:
- You receive (est.) — the projected landing amount.
- Minimum received — the worst case under your slippage tolerance. If price moves past it, the transfer reverts rather than filling badly.
- Estimated time — L2-to-L2 routes are minutes; anything touching mainnet takes longer.
- Fees and gas — the all-in cost. If it looks high, compare with an alternative token pair, e.g. bridging USDC instead of ETH.
Step 6 — Approve, then confirm
Token transfers need two signatures the first time: an approval (permission for the route's contract to spend that token — you can limit it to the exact amount) and the actual send. Native tokens like ETH skip the approval. Read what each prompt asks for; a legitimate approval request names the token and amount, never your seed phrase.
Step 7 — Wait for the destination
The status panel tracks the transfer. Most L2-to-L2 routes finish in minutes; mainnet legs can take 15–30. Don't close the tab in a panic — even if you do, the transfer completes on-chain and the funds land in your wallet either way.
Step 8 — Verify arrival (and add the network)
If your wallet doesn't show the destination network, add it — the wallet will prompt you when the site offers. Your address stays the same; switch networks to see the new balance. If tokens arrived but you expected the gas token too, some routes let you swap a sliver for gas on arrival — otherwise send a little from an exchange later.
Troubleshooting
- Transfer "stuck" for hours — check the status link in the interface first; mainnet congestion stretches ETAs. True failures auto-refund on the source chain for most routes.
- "Insufficient [token]" — you need the source chain's native gas token to pay for the send. Top up a small amount.
- Received less than quoted — you hit the slippage tolerance boundary; the minimum-received figure is the floor that was honored. Set a tighter tolerance next time on quiet pairs.
Last reviewed: September 2026.