Why Token Support Differs by Network on zkSync
Why the same ticker can represent different contracts and why chain selection matters.
Why this matters on zkSync
The same ticker can exist as multiple contracts on multiple networks. Network-specific contract verification prevents one of the most common cross-chain mistakes.
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: 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
- Check that the token you hold on zkSync is supported for the route you are considering.
- Allow for a delay between sending and receiving; do not repeat a transfer while one is pending.
- Keep enough native balance on zkSync to pay for the transaction that starts the transfer.
- Review the final recipient address and network before confirming a cross-chain transfer.
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