Slippage in Crypto: What It Is, How to Avoid It

What is slippage in crypto?

Slippage is the gap between the price you were quoted for a swap and the price you actually got when the transaction confirmed. You ask to buy a token at what looks like 0.0001 ETH each, the block confirms, and you find you paid 0.000103. That extra 3% is slippage.

It exists because a quote is a snapshot and a swap is a settlement. Time passes between the two. On Base and Ethereum that gap is at least one block, and a lot can change in a block: other people trade, the price moves, and your own order pushes the price as it fills.

Slippage is almost always expressed as a percentage. A swap that fills 1% worse than quoted has 1% slippage. It can occasionally break in your favor (positive slippage, where you get a better price than quoted), but on thin markets it usually runs against you. That is why every DEX makes you set a limit before it will send the trade.

Why slippage happens: three causes

Slippage has three separate sources, and it pays to keep them apart because you control some and not others.

• Price movement. Between the quote and the fill, the market moves on its own. Someone else's buy lands in the same block, a whale dumps, the pool re-prices. You had no part in it, but you settle at the new price.
• Thin liquidity. The less depth a pool has, the more any single trade moves the price. A pool holding millions of dollars of liquidity barely flinches at a 1 ETH buy. A pool holding a few thousand dollars lurches. Fresh launches sit at the thin end.
• Your own price impact. Every buy walks the price up and every sell walks it down. The bigger your order relative to the liquidity in front of it, the further you push. This is the part of slippage you cause yourself, and it is the part you can actually plan around.

Slippage vs price impact: not the same thing

People use these two words as if they mean the same thing. They do not, and confusing them leads to setting the wrong tolerance.

Price impact is the price you move by simply because your order eats into the pool's liquidity. It is deterministic. On a Uniswap v3 pool you can compute it exactly from the current liquidity and the size of your trade. A 5 ETH buy into a shallow pool might carry a 12% price impact, and that 12% shows up whether or not anyone else trades in your block.

Slippage, strictly speaking, is the extra movement on top of that caused by other activity between quote and execution: the price drift you did not cause. Most wallets fold both into a single number they label slippage, which is fine day to day, but the distinction matters when a swap fails. If your trade reverts with a large tolerance set, the culprit is usually price impact from your order size, not market noise. The fix for price impact is a smaller trade or a deeper pool, not a looser slippage setting.

Why fresh single-sided launches have high price impact for big buys

Bubblepad launches are single-sided: the pool starts seeded with 100% of the token supply and zero ETH. Price starts low and rises along the Uniswap v3 curve as ETH buyers come in. That design is honest and MEV-resistant, but it has a direct consequence for slippage.

At launch there is no ETH-side depth cushioning your buy. The first buyers are climbing the steep part of the curve, so a large order moves the price a long way in a single transaction. A 0.05 ETH buy might fill cleanly. A 5 ETH buy into the same minute-old pool can carry double-digit price impact, because there simply is not much liquidity between the current tick and where your order finishes.

This is not a bug or a hidden fee. It is the same v3 math that lets a launch start with no ETH at all. As real volume flows in and the pool climbs the curve, depth around the current price grows and price impact for a given order size falls. If you are early and buying big, size your entry to the depth that exists, or split it. Bubblepad's optional first-buy lets a creator ape a small amount in the same launch transaction with no MEV window, which is a cleaner way to take an early position than firing a huge market buy a few blocks later.

The takeaway: on a brand-new pool, high price impact on a large buy is expected, and cranking your slippage tolerance up to force it through is exactly the wrong move. Read the next section for why.

How slippage tolerance works and the MEV trap

Slippage tolerance is the worst price you are willing to accept, expressed as a percentage below the quote. Set it to 1% and the swap includes an on-chain minimum-output amount: if the trade would fill more than 1% worse than quoted, it reverts and you keep your ETH (minus gas). It is a floor, a protection, not a target.

Set it too low and legitimate trades fail. On a volatile token or a fast-moving launch, a 0.5% tolerance will bounce constantly because the price genuinely moved more than that between quote and block. Frustrating, but nothing is stolen.

Set it too high and you invite a sandwich attack. This is the real danger. A searcher bot watching the mempool sees your buy with, say, 20% tolerance. It front-runs you with its own buy (pushing the price up), lets your order execute at the inflated price you authorized, then sells into you in the same block. Your generous tolerance is the exact budget the bot extracts. You told the chain you would accept a 20% worse price, so the bot takes as close to 20% as it can. High tolerance does not make your trade clear faster in any useful sense; it just hands MEV bots a target.

The right tolerance is the smallest number that reliably lets your trade clear. For deep, calm pools that is a fraction of a percent. For a thin or newly launched token it may need to be higher to cover honest volatility, but every extra point is money you are offering to whoever is fastest. Never treat a large price impact as something to solve with tolerance. If the swap needs 15% tolerance to pass, the message is that your order is too big for the pool, not that you should sign away 15%.

How to avoid slippage: practical tips

You cannot eliminate slippage on a DEX, but you can keep it small and keep MEV bots away from it.

• Size to the pool. Before a big buy, check the price impact number your DEX shows. If it reads double digits, your order is too large for the liquidity in front of it. Shrink it.
• Split large orders. Breaking one 5 ETH buy into several smaller ones, spaced out, lets the pool and arbitrageurs restore depth between fills so each slice moves the price less.
• Set tolerance tight, then loosen only as needed. Start around 0.5% to 1% on liquid pairs. Raise it in small steps only if honest volatility keeps reverting your trade, never in one big jump.
• Trade the deeper fee tier when there is a choice. Bubblepad exposes 0.3% and 1% pools on Base, and 0.25% on PancakeSwap v3 on BSC. More liquidity concentrated near the price means less impact per trade.
• Avoid buying into the first seconds of a launch with size. On a single-sided seed the curve is steepest at the start. Waiting for real depth to build, or using a creator first-buy, costs far less than eating a huge impact and a possible sandwich.
• Use MEV-aware routing where your wallet offers it. Private transaction relays keep your order out of the public mempool so bots cannot see your tolerance to exploit it.
• Watch the network. Congestion widens the gap between quote and fill because your transaction waits longer, so quotes go stale. In busy periods, tighten your assumptions.

Slippage is not a fee Bubblepad or Uniswap charges you. It is a property of trading against a pool of finite depth, and the whole point of locked, single-sided launches is that the depth is real and permanent rather than something a team can pull. Understand the curve, size your trades to it, and keep your tolerance honest. Want to see the mechanics from the launch side? Head to /launch.