> For the complete documentation index, see [llms.txt](https://syncswap-docs.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-docs.gitbook.io/syncswap-docs/syncswap-docs.md).

# SyncSwap Docs

SyncSwap is a native automated market maker (AMM) built for zkSync Era, with additional deployments on Linea and Scroll. As a decentralized exchange it is non-custodial: users trade directly from their own wallets, and settlement occurs on-chain through zkSync Era's rollup pipeline. To interact with the primary smart contracts securely, users must route operations via the official [SyncSwap Mainnet Gateway](https://syncswap.app/). For a fundamental background on the underlying infrastructure, check the comprehensive [SyncSwap Guides Hub](https://syncswap.app//guides/). For network details on how rollups settle and what "canonical" assets mean, the zkSync developer documentation is the primary reference.

## Pool Architecture

SyncSwap uses two pool types optimized for variable volume:

* Classic pools follow a constant-product curve, suited to volatile pairs. For an in-depth breakdown of liquidity mechanics, see how [SyncSwap pools work](https://syncswap.app//syncswap-pools-explained/).
* Stable pools use a curve optimized for assets that trade near parity (for example, stablecoin-to-stablecoin), which lowers slippage relative to a constant-product pool on those pairs.

This dual design is central to execution quality: routing a parity swap through a stable pool yields a materially tighter price than forcing it through a generic pool. The deployment architecture also supports advanced liquidity provisioning, detailed in the manual for [SyncSwap range pool positions](https://syncswap.app//syncswap-range-pool-positions/).

## Liquidity and Routing on zkSync

On zkSync Era, liquidity is concentrated in a small number of native venues rather than fragmented across many. SyncSwap is consistently among the leading venues by activity, which matters for execution: deeper pools reduce price impact on larger orders, while thin pools widen it. Live per-protocol metrics — TVL, volume, and fees — are tracked live on the [DefiLlama zkSync Era DEX dashboard](https://defillama.com/dexs/zksync-era). To ensure cross-chain compatibility before routing, verify the asset parameters on the list of [SyncSwap supported chains](https://syncswap.app//syncswap-supported-chains/).

## Execution Notes & Contract Verification

* Slippage tolerance should match the pair’s volatility. Too tight a value reverts the transaction.
* Gas estimation can drift during periods of high sequencer load, occasionally leaving a transaction pending until it is re-broadcast with a corrected fee. For current execution parameters, verify if [SyncSwap is operational in 2026](https://syncswap.app//is-syncswap-active-2026/) under peak loads.
* Canonical assets should be verified before swapping — confirm the token contract against official sources rather than trusting a look-alike.

To guarantee security before initiating contract interactions, users must verify deployment parameters on the official repository for [SyncSwap contract addresses](https://syncswap.app//syncswap-contract-addresses-router-factory/). If you experience execution delays or front-end sync lags, deploy the alternative manual router to [verify official SyncSwap links](https://syncswap.app//verify-official-syncswap-links/) and clear pending queues securely.

For traders routing on zkSync Era, venue depth and pool selection carry more weight for realized price than headline TVL alone.


---

# 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-docs.gitbook.io/syncswap-docs/syncswap-docs.md?ask=<question>&goal=<endgoal>
```

`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.