SyncSwap is a non-custodial decentralized exchange running on Ethereum ZK-rollups, while ZKsync is one of the networks that can carry its transactions. Before starting, the user must select the right chain, hold the correct token there, allow for gas and trading costs, and distinguish a token swap from a cross-chain bridge transfer.
Is SyncSwap the same as ZKsync?
No. SyncSwap is the application and smart-contract system; ZKsync is an Ethereum layer-2 network. SyncSwap uses ZK-rollup networks to execute trades cheaply, but changing from SyncSwap to ZKsync is not the same as changing networks in a wallet.
| Item | What it does | What the user checks |
|---|---|---|
| SyncSwap | Quotes and executes token trades | Pool, route, fee and minimum received |
| ZKsync | Processes and settles transactions | Wallet network and native gas asset |
| Wallet | Controls funds and signs approvals | Account, balance and permissions |
| Bridge | Moves assets between networks | Source chain, destination chain and finality |
Which networks does SyncSwap support now?
The current SyncSwap documentation lists five supported networks: ZKsync Era, Linea, Scroll, Sophon and Creator Chain. Availability is not universal across them: a token pair, pool type or feature can exist on one chain but not another, so the network selector and the pool page must agree before any approval is signed.
- Confirm that the wallet is connected to the intended chain.
- Check the token’s contract address on that chain, especially for bridged assets with similar symbols.
- Verify that the selected pair has usable liquidity rather than merely appearing in search.
- Keep the chain’s required native gas token available unless the interface explicitly offers a paymaster option.
What must be ready before using SyncSwap?
The preparation is complete only when the trade can survive the approval, quote and confirmation stages without needing a second deposit or network change.
- Fund the wallet on the same network shown in the trade interface.
- Check the input balance after reserving enough for gas and any approval transaction.
- Read the quoted output, price impact, route and pool fee before approving the token.
- Set slippage deliberately. A wider tolerance may execute a volatile trade, but it also accepts a worse price.
Why can a SyncSwap trade fail after the quote?
A quote is a temporary calculation, not a reservation. It can expire when another trade changes the pool balance, when the chosen route no longer meets the slippage limit, or when the wallet has approved less than the requested amount. The displayed cost can also contain three different components: the pool’s swap fee, the network gas charge and price impact caused by the order size. A low gas fee does not make an illiquid pool safe to trade.
Is bridging the same as swapping on SyncSwap?
No. A swap exchanges one asset for another on the same network. A bridge transfers an asset from one network to another, often creating or releasing a corresponding representation. Someone holding ETH on Ethereum mainnet cannot assume that a swap screen on ZKsync can spend it directly; the funds must first arrive on ZKsync through a suitable bridge, and the destination balance must be confirmed before trading.
What should be checked on the final confirmation?
Before signing, compare the input token, output token, network, recipient, minimum received and contract interaction with the intended trade. After signing, wait for the transaction to complete and verify the resulting balance on the same chain. If the result is missing, switching networks in the wallet is the first check; submitting another transaction is not.
Once those checks are satisfied, https://syncswap.dev/ opens the SyncSwap interface where the reader can select the network, inspect the route and review the transaction before signing.