Four Checks for Choosing Stable or Volatile Pools

Choose a stable pool when the assets are expected to trade near a fixed ratio, and a volatile pool when their relative price can move materially. The pool contract’s invariant sets how liquidity responds to trades: a stable-swap curve concentrates pricing efficiency near its target ratio, while a volatile pool commonly uses the constant-product rule, x × y = k. Four checks make the choice concrete: the pair’s price relationship, the contract’s curve, executable liquidity and expected net fees.

Are the two assets expected to keep a fixed ratio?

Choose the pool type from the pair’s economic relationship, not from token names or labels. Two dollar-pegged tokens are candidates for a stable pool because arbitrage and redemption can keep their market prices near parity. Wrapped versions of the same asset may also track closely, but only if their redemption, custody and contract risks do not break that link.

A stable pool assumes that the target ratio is meaningful. If one asset loses its peg, the curve can continue offering it cheaply against the asset that still holds value. Arbitrageurs then remove the stronger asset and leave LPs with more of the impaired one. That is adverse selection: the pool’s pricing rule helps traders exchange against liquidity after the external price has moved.

For a pair such as ETH and a dollar stablecoin, the relative price changes as ETH moves. A volatile pool is built for that movement. The assets do not need to be uncorrelated; the relevant question is whether the pair can depart substantially from the ratio that a stable curve assumes.

What invariant does the pool contract enforce?

Read the pool’s contract type and invariant before depositing. A volatile constant-product pool constrains reserves with x × y = k, so a trade shifts the reserve ratio and moves the marginal price along the curve. A stable-swap pool uses a different invariant, designed to make trades cheaper near a target ratio and progressively more expensive as reserves move away from it.

The stable curve can reduce price impact for swaps near parity, but it does not guarantee a peg, prevent a depeg or remove inventory risk. Its behavior away from the target depends on the exact invariant and its parameters. A pair that no longer tracks closely can push the pool into the curve’s less efficient region while leaving LPs exposed to the asset losing value.

BaseSwap mechanics depend on the pool and product version. For the general flow of swaps, reserves and liquidity positions, see how BaseSwap swaps and liquidity work. Then verify the specific pool’s contract and supported position type; a DEX interface can list pools that follow different designs.

How much liquidity can a trade actually use?

Compare the pool’s executable depth at the trade size you care about. Total value locked is only a broad measure of assets in the pool; it does not directly show the price impact of a particular swap. In a constant-product pool, reserves and trade size determine how far the reserve ratio moves. In other designs, liquidity may be concentrated around a price or target ratio and thin out beyond it.

Check the quote for the intended trade size, including the fee and expected price impact. Compare it with other routes available for the same tokens, and note whether the pool has enough liquidity on both sides of its current price. A large displayed balance can still produce a poor execution price if the relevant side is shallow or the pool’s liquidity is concentrated elsewhere.

For LPs, depth also affects how much capital is exposed to trades and how much fee income a given volume may generate. A pool with more liquidity is not automatically more profitable: it may share fees across more LP capital, while low depth can make returns volatile and increase the cost of exiting.

Do fees and incentives compensate for the exposure?

Estimate net fee income against the risk of holding the pool’s changing token mix. Swap fees accrue when trades use the pool, but volume and fees can change. Any emissions or external rewards are separate from swap fees and may change under the protocol’s rules. Treat advertised rates as a snapshot, not a fixed return.

Compare fee history and trading activity with the pool’s liquidity, and account for the possibility that a stable pair depegs or a volatile pair moves sharply. LP positions can end with a different ratio of assets than a simple hold position. Fees may offset some of that difference; they do not ensure that they will.

• Use a stable pool only when the pair has a credible mechanism or history for maintaining its target ratio.
• Use a volatile pool when the pair’s relative price can move materially.
• Verify the contract’s invariant and pool version before supplying assets.
• Compare executable depth and fee income with the inventory and exit risks.

The confirmed choice is mechanical: the pool invariant encodes assumptions about how the pair’s price behaves, and those assumptions shape trade pricing and LP exposure. Whether a particular pool will earn enough fees, keep its liquidity, or withstand a future depeg or price move remains unverified by the pool type alone.