SyncSwap’s Three Pool Curves Serve Different Markets

SyncSwap’s Classic, Stable and Aqua pools use different pricing curves, so the right choice depends on how the two assets are expected to trade against each other. The distinction affects swap pricing and liquidity exposure: Classic uses a constant-product invariant, Stable uses a hybrid curve designed for assets near parity, and Aqua uses a dynamic hybrid curve with automatic rebalancing. For a specific trade, compare the quoted output and fee for the actual pool and route; the pool label alone cannot establish which execution is better.

What does each syncswap pool type do?

Each pool type applies a different curve to the same basic task: price a swap against the assets held in the pool. The protocol’s documentation describes Classic as an x*y=k pool, Stable as a Stableswap-style hybrid curve, and Aqua as a dynamic hybrid curve modeled on Curve v2’s twocrypto pools.

Classic’s constant-product curve supports general trading pairs. As a swap moves the reserves further from their starting ratio, the marginal price moves against the trader. This makes the curve broadly applicable when the assets can diverge in value, but a large trade relative to pool depth can incur substantial price impact.

Stable’s hybrid curve is designed for tokens expected to remain close in price, such as assets tracking the same unit. Around parity, it can offer a flatter price curve than constant product, which can reduce price impact for swaps that keep the pool near its intended balance. The benefit depends on the assets behaving as expected. If their market prices diverge, arbitrage trades against the pool’s stale price until the pool balance and external market converge; liquidity providers can be left holding more of the weaker asset.

Aqua is the V2 pool model. SyncSwap describes it as a dynamic hybrid curve with automatic rebalancing, intended for volatile assets and liquid-staking tokens. Aqua also supports dynamic swap fees. The protocol’s fee data includes minimum and maximum fee values and a gamma parameter; the documented fee behavior is more variable when gamma is lower. Classic and Stable pools generally use fixed fees, though fee settings can be pool-specific.

When should a trader choose Classic, Stable or Aqua?

Choose the pool whose assumptions match the pair, then compare the live quote. The broad distinction is asset behavior: Classic accommodates general pairs, Stable targets near-parity assets, and Aqua is designed for volatile or liquid-staking pairs.

• Classic: Consider it for pairs whose market prices can move independently. The constant-product curve does not assume that the tokens should stay near a fixed exchange rate.
• Stable: Consider it for assets designed to track the same value. Its curve is suited to swaps around parity, but that design cannot guarantee either token will maintain its peg.
• Aqua: Consider it when the pair is volatile or includes a liquid-staking asset and an Aqua pool is available. Its dynamic curve and fee model distinguish it from the other two types.
• Any type: Check the quoted output, fee, pool depth and route for the trade size you intend to make. A lower nominal fee does not by itself mean a better quote if the curve or available liquidity produces more price impact.

The syncswap interface presents pools and swap quotes, but a pool’s displayed type is only one input to a decision. For an execution, the amount received after fees matters more than the curve’s name. A route may also involve more than one pool, so inspect the full route and compare the final output rather than assessing one hop in isolation.

What trade-offs should liquidity providers weigh?

Liquidity providers take exposure to the pool’s inventory and to changes in the relative market prices of its tokens. The curve shapes how that inventory changes as traders swap; it does not remove the risk that the market price moves away from the pool’s balance.

In a Classic pool, arbitrageurs can trade against a reserve ratio that no longer matches external prices. In a Stable pool, the intended near-parity pricing is useful only while the assets remain close enough for that curve to fit their market relationship. A depeg or other sustained divergence makes the pool’s pricing assumption less suitable. Aqua’s automatic rebalancing and dynamic fee behavior are designed for a different market profile, but they do not guarantee a particular return or prevent losses when asset prices move.

Fees are also only one part of the provider’s result. Trading activity can generate fee revenue, while shifts in relative prices change the value and composition of the deposited position. The relevant comparison is between the pool’s fee income and the effect of those price changes over the time liquidity is supplied. No pool type can be judged from its curve alone without considering the tokens, pool depth, fee settings and market conditions.

For most traders, the practical choice is the pool and route that return the best live output for the intended swap, after fees and price impact. For liquidity providers, match the curve to the assets’ expected price relationship and treat incentives or recent volume as separate from the curve’s mechanics. Confirmed by SyncSwap’s documentation: the three pool models use distinct curves, and only Aqua currently supports dynamic fees. The actual fee, available liquidity, route and result for a particular transaction depend on the pool state and must be checked at execution.