zkSync Wallets and the Base to Arbitrum Route
How zkSync balances relate to the Base to Arbitrum route.
Why this matters on zkSync
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.
zkSync is an Ethereum scaling ecosystem with its own network context and token representations.
zkSync is part of the Ethereum scaling ecosystem. The same ticker can exist on Ethereum and on zkSync 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.
zkSync and this route
zkSync is neither end of the Base to Arbitrum route, but a wallet that uses zkSync often holds balances on those networks too. If your assets are on zkSync, 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.
zkSync: what to pay attention to
- Costs: Compare network fees with bridge and liquidity costs for the complete route.
- Security: Check the active network, contract and destination before signing.
- Assets and tokens: Verify the asset contract on zkSync before assuming it matches another network.
A zkSync 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 zkSync is available; check the current interface and quote.
Bridge from zkSync
Compare network fees with bridge and liquidity costs for the complete route. On the Linea side: verify the token contract on Linea before moving it.
The bridge guide below is informational; any transaction depends on current network conditions and the route shown in the bridge interface.
zkSync → Linea BRIDGE GUIDE