JUMPBIT
Open app
FixesUpdated 23 Oct 20261 min read

Meteora DLMM error 6055 (0x17a7): LiquidityLocked

The fix

You tried to remove liquidity in the same slot it was added. DLMM blocks that to prevent just-in-time liquidity; it works one slot later.

Tools covered

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

What the error means

Error Code: LiquidityLocked. Error Number: 6055.

You tried to remove liquidity in the same slot it was added. DLMM blocks that to prevent just-in-time liquidity; it works one slot later.

Where it comes fromMeteora DLMM program
Code6055 (0x17a7)

How to fix it

  1. Wait a moment and remove again in a later slot.
  2. If your bot adds and removes in one transaction or slot, separate the steps.

If that is not it

  • If the position is a locked position by design, it can only be withdrawn after its lock ends.

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); our mainnet-fork test, read on 24 October 2026.

Questions people ask

Why can't I remove liquidity I just added?

DLMM blocks removal in the same slot as the add; try again a moment later.

Where have you seen this?

Testing DLMM add and remove on a mainnet fork, where same-slot removal returned 6055 and worked one slot later.