What is slippage in crypto? Why your meme coin buy fills at a worse price and how to set your tolerance

You tap Buy with a quote of 1,000,000 coins for $50, and the confirmation shows 940,000. Nothing went wrong, in the sense that the contract did exactly what it was asked, but you paid 6% more per coin than the screen said a second earlier. That gap is slippage, and on meme coins it is the most common source of the feeling that the market is against you. This guide explains where the gap comes from, what the tolerance setting on a swap screen actually controls, why a transaction fails with 'slippage exceeded' and what to set it to on a brand-new coin without becoming a sandwich bot's lunch. If you want the pool mechanics first, read what is a liquidity pool.

Slippage, defined precisely

A swap quote is a snapshot of the pool at the moment you asked. Your transaction executes later, after it has been sent, picked up and included in a block. In between, other transactions may have traded against the same pool. If they bought, the price is higher when your turn comes and you receive fewer coins than quoted; if they sold, you receive more. Slippage is that difference, expressed as a percentage of the quoted amount. It can be positive, but on a coin that is being bought heavily it is almost always against you, because the trades landing before yours are the same crowd you are part of.

The amount of slippage depends on three things: how long your transaction waits, how much volume hits the pool in that window, and how small the pool is relative to that volume. A busy coin on a thin pool in its first two minutes can move 10% between blocks; the same coin an hour later with a deeper pool and calmer flow moves a fraction of a percent.

Three things people call slippage that are not

• Price impact: the price move caused by your own trade's size. It is known before you send and shown on the swap screen. A 4% impact on a $200 buy into a small pool is a fact of the pool, not a timing loss. The difference is covered in price impact vs slippage.
• Transfer taxes: some tokens take a percentage of every transfer in the contract, so you receive fewer coins than the pool sent. A swap screen cannot see this in the quote and your transaction will fail unless your tolerance covers the tax. On an unknown coin, a swap that only succeeds at 10% or higher tolerance is a strong sign of a tax; check the contract before buying. sasa's automated safety check covers transfer taxes for this reason.
• Fees: the pool's swap fee and the app's fee are deducted on every trade at a known rate. They lower what you receive, but predictably, and they are included in a correct quote.

What the tolerance setting actually does

The slippage tolerance is not a target or a speed setting. When you send a swap, the app computes the minimum output you will accept: quoted amount times one minus the tolerance. At 1% tolerance on a 1,000,000 coin quote, the transaction says 'give me at least 990,000 coins'. The DEX router checks the actual output at execution time; if it is below the minimum, the whole transaction reverts. You keep your ETH or USDC, you pay the network fee for the failed transaction, and the pool is untouched. Uniswap documents this parameter as the minimum amount out in its swap guide.

So a low tolerance protects you from bad fills at the cost of more reverts, and a high tolerance gets you filled at the cost of accepting whatever the pool is doing when your turn comes. Neither setting changes the order of transactions or how fast yours is included; that is decided by the chain and the fee you pay.

Why 'slippage exceeded' is usually good news

A revert with a slippage error means the pool moved further than you were willing to accept. On a new coin that almost always means a burst of buys landed just before yours, and the price you would have paid was higher than you planned. The revert cost you a network fee, usually cents or less on Base, Robinhood Chain and BNB Chain; see Robinhood Chain gas fees for what those numbers look like. The alternative, filling at any price, costs more on average. Treat a revert as the system working and decide again with the new price, rather than raising tolerance until something goes through.

The sandwich: why high tolerance costs money

A pending transaction with a high tolerance is a public promise to accept a bad price: a bot that sees it can buy ahead of you and sell right after, inside the same block, and its profit is bounded by your tolerance. With 1% there is no room to extract anything after fees; with 25% there is a lot. MEV in meme coin trading works through the numbers, which chains expose your transaction and the defenses; the point here is that the tolerance setting has a safety role, not just a convenience role.

Settings that work, by situation

1. Established coin, deep pool, normal volume: 0.5% to 1%. Reverts will be rare and any fill inside that range is fair.
2. New coin, first hour, active buying: 3% to 5%. Expect occasional reverts; resend with the fresh quote rather than raising the number.
3. Launch race or the first minutes after graduation: 5% is the ceiling worth using. Beyond that you are paying more to the crowd ahead of you than any fill is worth.
4. Selling into a falling coin: tolerance works the same way, as a floor on the ETH or USDC you receive. Set it to the amount you are genuinely willing to accept, and if it reverts, the price fell past your floor; decide again.

Reducing slippage without raising tolerance

• Trade on deeper pools. The same volume moves a $200,000 pool a tenth as much as a $20,000 pool, so your quote survives longer.
• Trade smaller. A trade that is a small fraction of the pool is less likely to be targeted and reverts less often.
• Use a route that submits privately or through the sequencer rather than a public mempool, where the chain allows it.
• Read the expected fill before confirming. Apps built for meme coins show it on the buy screen; on sasa the quote is in USDC, so the number you see is the dollar cost of the coins you will receive, and the fee details are on the Help page.
• Avoid the exact second of a scheduled event. The minute a coin graduates or a race ends is when the most transactions compete for the same pool; a trade thirty seconds later usually fills closer to quote.

A worked example from a launch

A coin launches with a pool of 2 ETH and 800 million coins, ETH at $3,000. You are quoted 19.3 million coins for 0.05 ETH, including a 1% fee. You set 3% tolerance, so your minimum output is about 18.7 million. Before your transaction lands, four buys totaling 0.4 ETH hit the pool, taking the ETH reserve to 2.4 and the coin reserve to about 667 million. Your 0.05 ETH now buys about 13.5 million coins, far below the floor, and the transaction reverts. You spent a cent on the failed transaction and were spared a fill about 30% smaller than quoted. You requote, see the new price, and decide whether the coin is still worth it at a market cap that just doubled. That decision, made with current information, is what the tolerance setting bought you. The same check belongs in any rug pull check: a coin that needs you to accept any price is asking you to stop looking.

Slippage on USDC-only apps

If you trade through an app that holds your balance in USDC and pays network fees from it, slippage still exists, because the swap still goes through a pool. What changes is who manages it: the app quotes in dollars, sets the floor and resends or reports the revert for you. On a four-chain launch race, each chain's pool has its own price, so a buy on the busiest chain carries more slippage risk than a buy on a quieter one; the race page shows the four pools live so you can pick. The underlying rule does not change: the floor is yours to set, and a fill below it is a fill you did not want.