Polygon → zkSync
Network-specific checks before a cross-chain transaction.
Polygon and zkSync have separate network contexts. A cross-chain route must account for the source environment, destination environment and the mechanism used to transfer or represent the asset.
Route Intelligence
Polygon: Polygon provides an EVM-compatible environment with its own network balances and token representations.
zkSync: zkSync is an Ethereum scaling ecosystem with its own network context and token representations.
On the source side, Confirm that the token is held on Polygon and verify its contract before moving or swapping it. On the destination side, Verify the asset contract on zkSync before assuming it matches another network.
Compare Polygon transaction costs with bridge and liquidity costs when consolidating small balances. On zkSync, Compare network fees with bridge and liquidity costs for the complete route.
Before You Bridge
- Source: confirm the asset is actually held on Polygon.
- Destination: confirm the wallet and destination network.
- Token: verify the exact asset representation rather than relying on ticker or logo.
- Costs: compare gas, bridge fees, liquidity, price impact and the final received amount.
- Security: Check network selection and contract addresses before signing, especially when an asset also exists on Ethereum. At the destination, Check the active network, contract and destination before signing.
Use the Live Bridge Tool
When a live route is available, open Dust Sweeper and review the current quote immediately before signing. Route availability, liquidity and network conditions can change.
OPEN BRIDGE TOOL