Why did I receive fewer tokens than the bridge quote showed?

01 October 2026

You received fewer tokens than the bridge quote showed because of slippage, which is the difference between the expected price of a trade and the actual price at the moment the transaction executes. Slippage happens in any bridge that uses an automated market maker (AMM) or liquidity pool to swap tokens, and it is not a scam, though it can feel like one. The quote you saw was an estimate based on current pool conditions; by the time your transaction confirms, those conditions may have changed.

How Slippage Occurs in a Bridge Transaction

A cross-chain bridge that uses a liquidity pool works like a decentralized exchange. When you bridge token A on chain X to token B on chain Y, the bridge does two things:

1. Locks or burns your token A on the source chain.
2. Releases token B from a liquidity pool on the destination chain.

The exchange rate between token A and token B is determined by the ratio of tokens in that pool. This is not a fixed price. Every trade shifts the ratio. If someone else trades before your transaction confirms, the pool's balance changes, and your trade executes at a worse rate.

Common causes of slippage

• Large trade size relative to pool depth. A small pool cannot handle a big swap without moving the price significantly. If you try to bridge $10,000 of a token with only $50,000 in the pool, you will move the price roughly 20% against yourself.
• Volatile market conditions. During rapid price movements, arbitrage bots and other traders act faster than your transaction can confirm. The quote you saw might be several seconds old by the time your transaction lands.
• Network congestion. On Ethereum or other proof-of-work chains, high gas prices cause transaction delays. The longer your transaction waits in the mempool, the more likely the pool state changes.
• Multi-hop routes. Some bridges route your token through intermediate pools or other bridges. Each hop introduces its own slippage.

Why the bridge quote misleads you

Most bridge interfaces show you a quote that reflects the current pool state at the moment you load the page. That quote is not a guaranteed execution price. It is a snapshot. The bridge protocol will typically execute your trade at whatever the pool rate is when your transaction is included in a block.

Some bridges display a "slippage tolerance" setting, often defaulting to 0.5% or 1%. This is the maximum deviation from the quoted price that you are willing to accept. If the actual price moves more than that, the transaction will revert (fail) rather than execute at a worse rate. If you set slippage tolerance too low, your transaction may fail repeatedly. If you set it too high, you accept the risk of a bad execution.

How to reduce slippage when bridging

You cannot eliminate slippage entirely, but you can control how much you lose to it.

1. Check the Liquidity Pool Depth

Before you bridge, look at the total value locked (TVL) in the pool you are using. Most bridge interfaces show this. A general rule: your trade should be no more than 1-2% of the pool's total liquidity to avoid significant slippage. If you are moving a large amount, consider splitting it into multiple smaller transactions spaced minutes apart.

2. adjust your slippage tolerance

Set your slippage tolerance to a realistic value. For most trades on well-capitalized pools, 0.5% to 1% is safe. For volatile tokens or illiquid pools, you may need 2% or 3%. Do not set it to 10% or higher unless you understand you are giving the protocol permission to execute at any price.

3. Use a Bridge That Offers Fixed-Rate Swaps

Some newer bridges use a "relay" or "intent-based" model where a third party quotes you a fixed rate and commits to executing it. These are not immune to slippage, but the risk shifts from you to the relayer. The tradeoff is that these services often charge a higher fee or take a spread.

4. bridge during low network activity

Network congestion increases the delay between your quote and execution. Check gas prices on the source chain. If they are spiking, wait. Tools like Etherscan's gas tracker or L2 fees dashboards can help.

5. Use a DEX Aggregator for the Swap Step

If your bridge allows you to choose which pool handles the swap, use an aggregator like 1inch or Paraswap to route through the pool with the best price. Some bridges integrate this automatically.

What to do if you already received fewer tokens

If the difference is small (under 2%), this is normal slippage. If it is large (5% or more), check the transaction details on a block explorer. Look at the swap event to see the exact rate at which the trade executed. Compare it to the quote you saw. If the rate is worse than your slippage tolerance setting, the transaction should have failed. If it executed anyway, the bridge interface may have had a bug or you may have set slippage too high.

There is no way to reverse a completed bridge transaction. The tokens are already on the destination chain at the rate the pool offered. The lesson is to verify pool depth and slippage settings before you confirm the next time.

Slippage vs. Spread vs. Fees

Do not confuse slippage with the bridge's built-in spread or fee. Most bridges charge a small percentage (often 0.1% to 0.5%) as a protocol fee. That is separate from slippage. The quote you see may or may not include this fee. Check the bridge's documentation. Slippage is the additional loss from market movement, not the fee.

The honest answer: if the quote said you would receive 1,000 USDC and you got 980 USDC, the most likely cause is that someone else traded before you in the same pool, moving the price. The bridge did not steal from you. The market did.

Back to bridges