JUMPBIT
Open app
FixesUpdated 23 Oct 20261 min read

Meteora DLMM slippage errors 6003 and 6004

The fix

The pool price moved before your transaction ran. 6003 means the amount would fill outside your slippage; 6004 means the active bin moved further than your bin tolerance.

Tools covered

  1. Meteora DLMMBuilding the most secure, optimized & composable yield layer on SolanaUpVisit

What the error means

Error Code: ExceededAmountSlippageTolerance. Error Number: 6003.  /  Error Code: ExceededBinSlippageTolerance. Error Number: 6004.

The pool price moved before your transaction ran. 6003 means the amount would fill outside your slippage; 6004 means the active bin moved further than your bin tolerance.

Where it comes fromMeteora DLMM program
Code6003 (0x1773) and 6004 (0x1774)

How to fix it

  1. Raise slippage, or the bin tolerance when adding liquidity.
  2. Trade or add a smaller amount.
  3. Retry with a fresh quote; DLMM fees and bins move quickly in volatile periods.

If that is not it

  • If the pool lacks liquidity in your direction, the error is PairInsufficientLiquidity (6012).

More fixes: how to decode any Solana error code and why Solana transactions fail.

Source

Error text and code from Meteora DLMM IDL (MeteoraAg/dlmm-sdk), read on 24 October 2026.

Questions people ask

What is DLMM bin slippage?

How far the active price bin may move from the one you quoted against.

Do pump.fun errors share these numbers?

Yes, 6003 and 6004 mean different things in each program; check the program ID.

Meteora DLMM slippage errors 6003 and 6004 | Jumpbit