Decentralized exchanges and slippage

In short

You have probably typed in a trade on a crypto exchange and watched the price change right before your eyes. That little surprise has a name. It is called slippage. A decentralized exchange, which most people call a DEX, runs without a company in the middle, and slippage shows up there more often and more sharply than most new traders expect. Understanding it before you trade can save you real money. Read the next few paragraphs slowly, and you will leave with a clear picture of what is happening and why.

The whole of it

What it is

A friend of mine once described slippage as ordering a sandwich and being charged a different price by the time the cashier rings you up. The price moved while you were waiting. On a DEX, slippage is the gap between the price you expected to pay and the price you actually paid. It is not a fee, though it can feel like one. It is simply what happens when supply and demand shift in the seconds between when you click and when your trade settles on the blockchain. Sometimes slippage works in your favor. Usually it does not.

I once watched a newer trader put in a large order on a small token and walk away stunned. He expected to pay one price. He paid a much higher one. That is slippage at its harshest, and it almost always comes down to two things: how fast the market moves and how much money is already in the pool you are trading against. Those two ideas will make sense in the next section.

How it works

If you are holding even a little curiosity about how a DEX actually runs, here is the honest picture. Most decentralized exchanges do not use a traditional order book, which is the list of buyers and sellers you would find on a stock exchange. Instead they use something called an automated market maker, or AMM. An AMM holds two tokens in a pool. A math formula keeps the ratio balanced. When you swap one token for the other, the formula adjusts the price automatically.

The formula most AMMs use is simple: multiply the amount of token A by the amount of token B, and keep that product constant. If you add a lot of token A to the pool, token B gets more scarce inside the pool, so its price rises. That price rise is slippage. The bigger your trade is relative to the pool, the more you push the price against yourself. Small pools make this problem much worse. This is worth repeating. Pool size matters enormously.

Many major DEX interfaces also let you set a slippage tolerance before you trade. That is a ceiling you choose. You are telling the exchange, do not fill my order if the price moves more than this percentage against me. Set it too tight and your trade fails. Set it too loose and the exchange fills your order at a bad price, or a bot called a sandwich bot can jump in front of you and steal the difference. That bot situation has a name too: front running. It is a real risk on public blockchains where anyone can see your pending trade. Check the documentation for the platform you use to confirm whether it offers this setting and how it works.

The numbers, and where to find yours

I once sat with a stack of papers trying to understand fee schedules, and I felt the same frustration you might be feeling now. The good news is that the main numbers you need are visible right on the trading screen of any major DEX. Look for the words price impact or slippage before you confirm a swap. Those are your two key figures.

Price impact is the percentage by which your specific trade moves the pool price. Most DEX interfaces calculate this for you in real time. A trade with a price impact above one or two percent is worth slowing down on. Some platforms will display a colored warning when price impact climbs into territory they consider high. Read that warning. It means something.

For slippage tolerance, defaults vary across platforms and token types. For smaller or newer tokens, traders sometimes raise the tolerance setting, but raising it invites front running. The official documentation for the exchange you use will explain their default settings and what they recommend. For Uniswap, that documentation lives at docs.uniswap.org. For PancakeSwap, it is at docs.pancakeswap.finance. Read the primary source for the platform you choose. Do not rely on secondhand summaries, including this one, for exact current figures.

A worked example

Maria decides to swap some ether for a smaller token on a DEX. The pool she is trading in holds tokens worth about 200,000 dollars total. She wants to swap tokens worth 10,000 dollars. That is 5 percent of the pool size. The AMM formula means her trade will move the price noticeably before it settles.

Before she confirms, she checks the screen. The interface shows a price impact figure she did not expect. That means if the token was priced at 1.00 dollar per unit before her trade, she will effectively pay more per unit by the time the trade is done. On a 10,000 dollar swap, even a few percentage points of slippage adds up to hundreds of dollars of cost, before any fees. She sees this and decides to split her trade into two smaller swaps done an hour apart. Each swap is 5,000 dollars. Because each swap is smaller relative to the pool, the AMM formula pushes the price less on each one. She still pays some slippage, but she reduces the total cost meaningfully. Splitting a large trade is one of the simplest moves available to you.

Where it goes wrong

You have probably seen warnings and skipped them. Most of us have. On a DEX, skipping the slippage warning is where things tend to fall apart. The first mistake people make is setting slippage tolerance very high, sometimes 10 or 15 percent, just to get a trade through on a volatile token. That wide window is an invitation to a sandwich attack. A bot sees your pending transaction, buys the token ahead of you to push the price up, lets your trade fill at the worse price, then sells immediately. The bot profits. You pay more than you had to.

The second place it goes wrong is thin pools. A thin pool is one with very little total value locked in it. Even a modest trade can cause severe price impact in a thin pool. Check the pool size before you trade. If the pool holds less than a few times your trade value, expect meaningful slippage. That check takes ten seconds and can save you real money.

A third problem is network congestion. Your trade sits in a queue on the blockchain. If the network is busy, your transaction waits. Prices move while it waits. By the time your swap executes, the price may have shifted past your tolerance, and the trade fails. You still pay the gas fee. Nothing went through. This can repeat several times on a busy day and add up to a real cost in failed transaction fees alone.

Questions to answer before you leave this page

Before you place your next trade on a DEX, sit with these questions for a moment, because they are the difference between going in clear eyed and going in hopeful: Do you know the total size of the liquidity pool you are trading in, and have you compared it to the size of your planned trade so you can get a sense of your price impact before you click confirm? Have you looked at whether the platform you are using offers a slippage tolerance setting, and if so, have you thought about whether the default makes sense for the token you are trading, given how active or how new that token is? If the platform showed you a price impact warning in red or orange, do you have a real reason to proceed, or are you pressing forward out of impatience? Have you considered splitting a large trade into smaller ones and spacing them out to reduce the pressure you put on the pool? And finally, have you read the official documentation for the specific DEX you are using, so that your understanding comes from the source and not from memory or rumor?