> For the complete documentation index, see [llms.txt](https://syncswap-1.gitbook.io/syncswap-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://syncswap-1.gitbook.io/syncswap-docs/syncswap-preflight-checklist-for-august-2026.md).
# SyncSwap: Preflight Checklist for August 2026
**SyncSwap** is usable only when the wallet is already on the correct Layer 2 network, holds the intended token there, and has enough native gas to complete every required transaction.
In practical terms, syncswap is a decentralized exchange and liquidity hub; its official interface is [SyncSwap](https://syncswap.dev/) The decisive dependency is not the browser, the quote, or the approval screen. It is chain location. If the wallet is connected to the wrong network, every later check is irrelevant.
### What network does SyncSwap use?
The wallet must be connected to a network that SyncSwap currently supports, with the assets already deposited on that network. SyncSwap’s official documentation lists zkSync Era, Linea, Scroll, Sophon, and Creator Chain as supported environments; check the application’s network selector before moving funds. [SyncSwap’s protocol documentation](https://docs.syncswap.xyz/syncswap/about-syncswap) is the authoritative place to compare that list with the current interface.
Do not treat “Ethereum-compatible” as “the same network.” ETH or USDC held on Ethereum Mainnet is not automatically available to a SyncSwap pool on zkSync Era. The same ticker can exist at several addresses across several chains, and the balances are not interchangeable until bridged or transferred through the correct route.
A useful preflight is simple: open the wallet’s network selector, note the exact chain name and chain ID, then compare it with the network selected in SyncSwap. If either side is ambiguous, stop there. Changing networks after opening a quote can invalidate the route and force a new approval.
### How much gas does SyncSwap need?
The wallet needs the chain’s native token separately from the token being swapped. A wallet containing 1,000 USDC but no ETH, ETH-equivalent, or other native gas asset on that same Layer 2 cannot approve or execute the trade.
One swap can require more than one transaction. A token may need an approval first; a new token, a different spender, or a changed allowance can trigger another approval. Keep at least two to three times the gas estimate displayed by the wallet or application. That is a practical buffer for a routine trade, not a SyncSwap fee quote.
Check the gas balance after switching networks, not before. Wallets often retain the previous chain’s balance on screen, which creates the most avoidable failure: the user sees funds, submits an approval, and discovers that the active network has no spendable gas.
### Why is my token not showing on SyncSwap?
The token must be held at the exact contract address supported by the selected network, and the wallet must have a spendable balance after reserving gas. Matching the symbol alone is not enough.
Before selecting a token, verify three fields:
* the network where the token balance exists;
* the token contract address, especially for similarly named or bridged assets;
* the amount available after leaving native gas untouched.
If the token does not appear, do not import the first contract address found in a search result. Confirm it through the project’s official channels or a reputable block explorer for the selected chain. A wrong token can be technically swappable while being economically worthless or impossible to sell back.
### What should a SyncSwap quote show?
A usable quote should show the route, expected output, fee, price impact, slippage setting, and minimum amount received. The number that matters is the minimum received, because that is the protection applied when the transaction executes—not the attractive headline estimate displayed before confirmation.
Reject a route when price impact is large enough to change the trade thesis. A low network fee does not rescue a poor pool. For a liquid, ordinary market, 0.5% slippage can be a reasonable starting point; it is not a universal setting. Stable pairs may justify less, while thin or volatile markets may need more. Set it from liquidity and volatility, not from habit.
Also compare the trade size with the pool’s available liquidity. Splitting a large order can reduce price impact, but each additional transaction consumes gas and introduces another execution point. The best preparation is to decide the maximum acceptable loss before signing, then reject any quote that exceeds it.
### Does SyncSwap approval require another transaction?
Usually, an ERC-20 approval is a separate on-chain transaction unless the wallet already granted a sufficient allowance. The approval authorizes the exchange contract to spend a specified token amount; it does not execute the swap.
That distinction matters operationally. The approval must be sent on the same network, confirmed successfully, and directed to the expected contract. After approval, refresh the quote rather than assuming the original route is still valid. A delayed approval can leave the quote stale, particularly in a fast-moving market.
For recurring use, an unlimited allowance saves future approval transactions but increases exposure if the approved contract is later compromised. A limited allowance costs more attention and sometimes more gas, but keeps the permission narrower. The sensible choice depends on frequency and risk tolerance; neither option removes the need to inspect the spender.
### What should be checked before swapping on SyncSwap?
The trade is ready only when every row below passes at the same time.
| Check | Pass condition |
| -------- | ------------------------------------------------------------------------------------------------ |
| Network | Wallet and application show the same supported chain. |
| Gas | Native token is available on that chain, with a two-to-three-times buffer. |
| Asset | Contract address and balance are verified; gas is reserved separately. |
| Quote | Fee, price impact, route, and minimum received fit the trade plan. |
| Approval | Allowance covers the intended amount and the spender is expected. |
| Exit | The user knows which explorer will confirm the transaction and what to do if it remains pending. |
### What is a ZK-rollup in the SyncSwap setup?
A ZK-rollup is a Layer 2 system that executes transactions off-chain in batches and submits cryptographic validity proofs to Ethereum; [Ethereum’s explanation of ZK-rollups](https://ethereum.org/developers/docs/scaling/zk-rollups) covers the settlement model. For the trader, the practical consequence is that the chain still determines the asset location, gas token, transaction status, and bridge path.
That is why the network check comes first. Once the wallet, funds, gas, token contract, allowance, and minimum received are all aligned, the remaining task is routine. Until they are aligned, clicking “Swap” is only a faster way to discover which prerequisite was missed.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://syncswap-1.gitbook.io/syncswap-docs/syncswap-preflight-checklist-for-august-2026.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.