What happens to a swap when the pool ratio is heavily one-sided

05 September 2026

A swap executes, but you get significantly less of the output token than a simple price quote would suggest - and in extreme cases, the transaction may fail outright. The ratio determines the effective price you pay, not just the "fair" price of the token.

Why the ratio matters

Liquidity pools use a constant product formula: the product of the two token reserves must stay the same after a trade. If a pool holds 100 Token A and 10,000 Token B, the product is 1,000,000. When you buy Token A with Token B, you add B to the pool and remove A, keeping the product constant. The more imbalanced the pool, the more drastically each trade shifts the ratio.

A heavily one-sided pool means one token dominates. For example, a memecoin pool where 99% of the liquidity is in the memecoin and 1% is in ETH. That imbalance tells you two things. First, the memecoin is priced very cheap relative to ETH. Second, any significant buy or sell of the memecoin will move the price substantially.

The price impact curve

Price impact is the difference between the current market price and the price you actually get. In a balanced pool, a small trade barely nudges the ratio. In a lopsided pool, even a modest trade can cause a 10% or 20% price swing. The formula is mechanical: the deeper you go into the thin side, the more each additional unit of input buys less output.

If you are swapping out of a memecoin (selling it for a stable asset like USDC or ETH), a heavily one-sided pool for the memecoin means you are selling into a shallow buy side. Your sell pushes the price down sharply. You might receive only a fraction of what a simple "rate × amount" calculation would suggest.

If you are swapping into a memecoin (buying it), the same imbalance works against you. The pool has very little of the memecoin, so each unit you buy requires more of your input token to extract it.

When the swap fails

If the ratio is so skewed that the pool lacks enough of the output token to satisfy your swap, the transaction will revert. This is common when trying to sell a large amount of a memecoin into a pool where nearly all liquidity is in the memecoin itself. The pool simply does not have enough of the other token to give you. The DEX returns an error like "insufficient liquidity" or "exceeds reserve."

Even if the swap does not fail, slippage protection may cancel it. You set a maximum slippage tolerance, say 1% or 5%. The actual price impact exceeds that tolerance, so the smart contract rejects the trade.

What you can do

First, check the pool's composition before swapping. DEX aggregators or block explorers show the reserve ratio. If one side dominates by more than 90%, expect heavy price impact. Second, consider swapping in smaller chunks. Each trade pushes the ratio back toward balance, but only if there is enough depth to absorb it. Third, use a route that passes through a more liquid intermediate token - this is the subject of the sibling page "What does it mean when a swap route uses multiple hops." Fourth, if the pool is too thin, you may need to find a different DEX that has the token you hold, as covered in "How do I find a DEX that actually has the token I hold."

The underlying logic

The constant product formula does not care about your intentions. It is a mathematical constraint. A heavily one-sided pool is a warning that the token's liquidity is concentrated in one direction. That is typical of memecoins that have been heavily dumped or barely traded. If you are moving between low-liquidity tokens and assets that can actually be spent or held, expect the pool ratio to be your primary cost. The "Swapping in and out of memecoins" hub page discusses the broader strategy for navigating these trades.

A heavily one-sided swap is not a glitch. It is the pool telling you the truth about supply and demand. The price you see on a ticker is never the price you will get.

Back to ledger