SyncSwap pool types change the liquidity you need by changing the pricing curve and, in some cases, where that liquidity is concentrated. The detail that made this click for me was that “liquidity” is not simply the dollar value deposited: it is the usable depth the pool’s invariant presents at the price a trader actually needs.
What required liquidity really means
SyncSwap is an automated market maker on zkSync Era, a Layer 2 network secured with Zero Knowledge Proofs. It does not use one universal pool formula. The pool type determines the token ratio you deposit, the slippage a trade creates, and how much of your capital remains useful as the market moves.
The common explanation gets this wrong by treating every pool as a larger or smaller version of the same thing. A $10,000 deposit in a Classic Pool does not provide the same trading depth as $10,000 in a Stable Pool, and neither behaves like a concentrated Aqua or Range position.
Classic, Stable, Aqua, and Range compared
A Classic Pool uses the constant-product invariant, x × y = k, and is designed for general-purpose pairs. Liquidity is spread across the full possible price curve, so it can support volatile or unrelated assets such as ETH and USDC. The cost is capital efficiency: to deposit $10,000 into an ETH/USDC pool, you normally need roughly $5,000 of each asset at the pool’s current price. As trades move the reserves apart, the same pool produces increasing slippage.
A Stable Pool uses a hybrid curve. Near a 1:1 peg it behaves more like a constant-sum pool, which means a USDC/USDT trade can use the deposited capital far more efficiently than the same trade in a Classic Pool. When the assets depeg, the curve falls back toward constant-product behavior. The required liquidity is therefore not merely “less”; it is liquidity in the right kind of pair, with both tokens remaining economically similar. Using Stable for ETH/USDC defeats the mechanism.
Aqua is intended for volatile assets and liquid-staking-token pairs. Its algorithm dynamically concentrates liquidity around the market price and adjusts as that price moves, rather than requiring the provider to manage a fixed range manually. That can make a given deposit act deeper near the current market than a Classic Pool, but it does not remove market risk: a sharp move can force the pool to widen its effective liquidity and charge dynamic fees.
Where the interface offers a Range or Concentrated Pool, the provider chooses the price band. This can be the most capital-efficient option while the market stays inside that band, but liquidity outside it is inactive. “Required liquidity” then includes a management requirement: the position may need rebalancing when the market leaves the chosen range.
The first time I looked at providing liquidity, I expected the deposit screen to tell me how much was enough. What actually mattered was the pair’s expected trading range. My earlier self needed one rule: choose the pool from the assets and price behavior first, then choose the amount. Do not choose a pool because its displayed fee or return is higher.
If you want to compare a pair’s available pool models and use the exchange interface, Syncswap is the site to open.
How to choose and deposit liquidity
- Connect MetaMask Wallet to zkSync Era, verify the token contracts, and keep enough ETH for network fees.
- Find the exact pair and inspect its pool type, reserves, fee, and current price. Check whether the pair is correlated, volatile, or likely to depeg.
- For Classic or Stable, supply the two assets in the ratio the pool requires. For Range, select a price band; for Aqua, let the model handle concentration automatically.
- Approve the tokens, confirm the deposit, and record the LP token or position you receive. That represents your share of the pool, not a fixed dollar claim.
- Monitor price movement, fee income, and the assets you would receive on withdrawal. Remove liquidity when the pool no longer matches the market you intended to serve.
My practical verdict is simple: use Classic for flexibility, Stable for genuinely pegged assets, Aqua for automated concentration in volatile pairs, and Range only when you are willing to manage the band. I would change that rule only if execution data showed a different pool consistently offered better depth after fees and price movement, not merely a higher advertised rate.
Top comments (0)