SyncSwap lets you swap tokens by connecting a funded wallet, choosing an input and output token, reviewing the quote, approving token spending if required, and confirming the swap. Start with MetaMask on the network where you hold the input token. The trade is complete when the transaction succeeds and the intended output token appears in your wallet balance.
- You need an input token on a supported network and enough ETH on that network for gas.
- You finish with a successful transaction and an increased balance of the intended output token.
A Funded Wallet on the Right Network Is Ready to Swap
A SyncSwap swap is ready when MetaMask holds the input token and gas on the same supported network you intend to use. Select that network in the wallet before connecting. zkSync Era is one network you may use when your tokens are already there; assets held on another network are not part of that wallet balance.
Open the exchange’s official site at syncswap.xyz and connect MetaMask. Compare the network shown by the wallet with the network you intend to trade on. If the connection fails, confirm that MetaMask is unlocked and on the intended network, then reconnect. Keep some ETH for the approval, if one is needed, and the swap transaction. An input token balance alone cannot pay gas for those transactions.
Choose the input token by its verified contract address when names or symbols look alike. Confirm the output token’s contract too: a familiar symbol can belong to a different asset. Enter an amount that leaves enough gas in the wallet. A pool swap exchanges your input against liquidity supplied to one or more pools; the resulting output depends on the available liquidity and the route used.
The Quote Shows Both an Estimate and an Execution Floor
The swap quote tells you what the pool route currently estimates you will receive and the minimum received amount the transaction will accept. Read both numbers before authorizing anything. The estimate can move as pool prices change; the minimum received amount is the floor applied when the swap executes.
The exchange uses pool liquidity to turn an input token into an output token. Its token-swapping function at SyncSwap is where you make that trade. Review the token pair and amount alongside the quoted fees, price impact, Slippage setting, and minimum received amount before you submit it.
Price impact describes how much your trade moves the price along its pool route. Slippage sets the permitted movement between the quote and execution, which affects the minimum received amount. Say an illustrative quote estimates 98 output tokens and shows 96 as minimum received. You are considering a trade that can succeed at 96 or more, even though 98 is the current estimate. If 96 is too little for your purpose, change the trade size or wait for a better quote before signing.
The SyncSwap router contract shows the mechanism behind that floor: its swap function passes a minimum output value to the swap routine, which reverts when the actual output is lower. A wider Slippage setting can lower the floor. Read the displayed minimum as a decision about the least output you would accept, not as a prediction of what you will receive.
Approval Authorizes Spending; the Swap Executes the Trade
An approval gives the named spender permission to use an input token; confirming the swap is the action that trades it. For an ERC-20 input, review the spender and allowance requested in MetaMask. Approve only an allowance you intend to grant, then wait for that authorization to succeed before confirming the swap transaction. A native ETH input does not require an ERC-20 spending approval.
Review the fresh quote again after approval. Confirm the input amount, output token contract, minimum received, and gas cost, then submit the swap in MetaMask. Approval may be a separate transaction, so a successful approval by itself is not evidence that you bought the output token.
Take an illustrative wallet holding 100 input tokens, no output tokens, and some ETH for gas. After a successful swap of 40 input tokens, the same wallet holds about 60 input tokens, the received output tokens, and less ETH because gas was paid. The wallet address and network stay the same. Any unused allowance may also remain until you change or revoke it.
Transaction Success and the Output Balance Confirm Receipt
The swap is complete when the transaction shows success on the correct network’s block explorer and the wallet’s output token balance reflects the receipt. Open the transaction from MetaMask or search its hash in that network’s explorer. Match the wallet address and output token contract before relying on a displayed symbol.
If the explorer shows success but MetaMask omits the token, import the verified output contract into the wallet and check its balance again. A missing wallet display can be a token visibility issue; the on-chain transaction record and balance establish what happened.
For a pending swap, inspect its transaction status before submitting another. A second submission can create another trade if the first later succeeds. If it reverted, no swap output was delivered, although gas was spent. Review the failure cause and get a fresh quote. An allowance error calls for checking the approved spender and amount; an insufficient-funds error calls for more gas; an expired or minimum-output error calls for a new quote and a fresh review of Slippage and minimum received.
Questions After Your First Swap
How do I revoke an allowance?
Revoke the token’s allowance for the specific spender through a wallet allowance control or a reputable allowance manager on the same network. Verify the token and spender addresses first. Revocation is an on-chain transaction and uses gas.
Can I place limit orders?
A standard pool swap executes when submitted; it is not a standing limit order. Use a separate limit-order function if one is available for your intended pair. The Slippage setting only controls the minimum output accepted by a submitted swap.
How do I export trade history?
Look up your wallet address on the relevant network’s block explorer and use its export function if available. Retain the transaction hashes so each trade can be checked against its on-chain record.
How are multihop routes selected?
A multihop route passes through intermediate pools to reach the output token. Review the quoted output, price impact, and minimum received for the route offered before submitting; the router executes the supplied path and enforces its minimum output.