Bridge Guide • Route Intelligence

zkSyncEthereum

Network-specific checks before a cross-chain transaction.

zkSync and Ethereum 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

Source network

zkSync: zkSync is an Ethereum scaling ecosystem with its own network context and token representations.

Destination network

Ethereum: Ethereum is an EVM network and the base layer for a large ecosystem of tokens, applications and Layer 2 networks.

Asset considerations

On the source side, Verify the asset contract on zkSync before assuming it matches another network. On the destination side, Verify the ERC-20 contract address and distinguish Ethereum-native assets from representations on other networks.

Fee considerations

Compare network fees with bridge and liquidity costs for the complete route. On Ethereum, Ethereum gas can make very small balance movements uneconomical, so compare total execution cost with the balance value.

Before You Bridge

  • Source: confirm the asset is actually held on zkSync.
  • 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 the active network, contract and destination before signing. At the destination, Pay close attention to contract approvals, transaction details and the exact domain used to initiate a transaction.
Never use a seed phrase or private key to complete a bridge. A legitimate bridge flow should not require either.

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

Related Routes

Learn More