The right SyncSwap liquidity pool depends mainly on how closely the two assets should track each other. Use a Stable Pool for tightly pegged assets, a Classic Pool for general-purpose pairs and simpler exposure, and an Aqua Pool when its dynamic design fits a more volatile or liquid-staking pair. Before depositing, compare the pool model, expected price movement, fee behavior, liquidity depth, and your tolerance for impermanent loss.
Start with the relationship between the two tokens
Do not choose a pool because it displays the highest fee or incentive figure. First ask whether the assets are supposed to remain near the same value.
| Token relationship | Likely starting point | Main reason |
|---|---|---|
| Two assets designed to track the same value | Stable Pool | Its pricing curve is designed for efficient trades near a 1:1 relationship. |
| Unrelated or materially different assets | Classic Pool | Its constant-product model supports broad pair types and does not assume a fixed peg. |
| Volatile assets or some liquid-staking pairs | Aqua Pool, if available and understood | Its documented design uses a dynamic hybrid curve and changing fee parameters. |
This is a starting rule, not a guarantee. A stablecoin can lose its peg, a liquid-staking token can diverge from its reference asset, and a volatile pair can experience a large one-sided move. The more the pair can separate in price, the less useful a “stable” label becomes for evaluating risk.
Stable Pools fit pegged assets, but only while the peg holds
A Stable Pool is generally the logical choice for pairs such as two dollar-denominated tokens that are expected to trade close to parity. Its hybrid curve can reduce the trading friction associated with a constant-product pool when prices remain near 1:1.
For a liquidity provider, the important limitation is the same assumption that makes the pool efficient: the assets should remain closely related. If one token loses its peg, the pool can become increasingly exposed to the weaker asset as traders arbitrage the changing price. Fees earned during that period may not compensate for the change in the value of the deposited assets.
Use a Stable Pool only after checking the identity of both tokens, their intended peg, and their current market relationship. Similar tickers are not sufficient. Confirm the contract addresses through a trusted source and examine whether the pair has meaningful recent liquidity and trading activity.
Classic Pools are the simpler choice for general pairs
Classic Pools use the familiar constant-product mechanism. They are better suited to pairs such as an established network asset and a token whose price can move independently. The model does not require the assets to stay near parity, but it does create the standard automated-market-maker trade-off: as one asset rises relative to the other, the pool composition changes.
That change is the basis of impermanent loss. Suppose a provider deposits equal values of Token A and Token B, then Token A doubles while Token B stays flat. Arbitrage trading tends to remove some Token A from the pool and add Token B. The provider may earn fees, but the final position can be worth less than simply holding the original tokens, depending on the size and timing of the price move.
Choose Classic when simplicity and broad pair compatibility matter more than specialized pricing behavior. Still check reserves and expected slippage. A pool can support a pair technically while remaining too shallow for the amount you plan to deposit or withdraw.
Aqua Pools require closer review before use
SyncSwap’s protocol documentation describes Aqua Pools as using a dynamic hybrid curve, with features intended for volatile assets and some liquid-staking pairs. The fee can also be dynamic, so a fee observed at one moment should not automatically be treated as a permanent rate.
This makes Aqua a poor choice for anyone who has not checked how its current parameters work. Review the pool’s displayed fee, the assets’ price relationship, the available liquidity, and how a large move could affect the position. A more sophisticated curve does not remove smart-contract risk, token risk, depeg risk, or impermanent loss.
If the pair is on a network or protocol version you have not verified, pause the pool comparison until that context is clear. Use the SyncSwap Protocol Guide to check the relevant SyncSwap context before deciding which pool information applies. That check confirms scope and compatibility; it does not establish that a particular pool is safe or profitable.
Use this decision rule before depositing
- Identify both contracts. Confirm that each token is the asset you intended to use and that both are on the same supported network.
- Classify the relationship. If the pair should stay near 1:1, investigate Stable. If prices are independent, start with Classic. Consider Aqua only after understanding its current parameters.
- Check the actual quote. Enter a small hypothetical trade and compare price impact, output, and fee details. A high advertised yield cannot repair poor execution.
- Model a price move. Ask what happens if one asset falls sharply, loses its peg, or becomes difficult to trade. Include the value of both assets, not only the fee income.
- Test the exit. Make sure the pool has enough liquidity for your intended withdrawal and that you understand any approval, gas, and transaction requirements.
For a user who only wants to swap, the best pool is usually the one that produces an acceptable verified quote at the chosen size and slippage limit. For a liquidity provider, the decision is stricter: select the pool whose asset relationship and risk profile you can tolerate, then recheck its fee and liquidity conditions immediately before depositing.