Scroll Wallets and the Base to Arbitrum Route

Why this matters on Scroll

Base and Arbitrum are both L2 environments, but that does not make their token contracts interchangeable. Treat the destination token as a network-specific asset.

Scroll is an Ethereum Layer 2 environment with its own transaction and asset context.

Scroll is part of the Ethereum scaling ecosystem. The same ticker can exist on Ethereum and on Scroll as separate token contracts, so a balance seen on one network cannot be assumed to exist, or to be redeemable at the same value, on the other.

Scroll and this route

Scroll is neither end of the Base to Arbitrum route, but a wallet that uses Scroll often holds balances on those networks too. If your assets are on Scroll, they would first have to be on Base for this route to apply.

Leaving Base

Consider Base transaction costs together with bridge and route costs when moving small balances. Use trusted interfaces and verify destination network and token before signing.

Arriving on Arbitrum

Confirm the Arbitrum token contract rather than assuming an identical ticker represents the same asset everywhere. Compare L2 transaction costs with any bridge or liquidity costs required to reach the destination.

Scroll: what to pay attention to

• Costs: Compare Scroll gas with bridge, liquidity and destination costs.
• Security: Confirm network and transaction details before signing.
• Assets and tokens: Verify the exact token contract on Scroll.

A Scroll checklist for this topic

• Verify the source network, the destination network and the destination address before signing.
• Compare quotes and the minimum received amount, since the final amount can differ from the estimate.
• Keep enough native balance on the source network to pay for the transaction.
• Do not assume a route from Scroll is available; check the current interface and quote.

Bridge from Scroll

Compare Scroll gas with bridge, liquidity and destination costs. On the Blast side: verify the token contract on Blast.

The bridge guide below is informational; any transaction depends on current network conditions and the route shown in the bridge interface.

Related guides