TxWhy

Error codes / Meteora Dynamic Bonding Curve

InsufficientLiquidity

Meteora Dynamic Bonding Curve · Custom(6033) · 0x1791

custom program error: 0x1791

What it means

The pool does not have enough liquidity left to fill a trade of this size. On a launch pool (a bonding curve such as Meteora DBC) it means the buy is larger than what is left before the pool graduates, and the program refuses the whole swap rather than fill part of it.

The program's own message: “Liquidity in bonding curve is insufficient”

What to do

Trade a smaller amount. On Meteora DBC, buy at most what is left before graduation, or use swap2 in partial-fill mode, which buys what is left and returns the rest. Paste the failed transaction into TxWhy to see the exact room left.

Seen on mainnet

On a dynamic bonding curve this is a buy larger than what is left before the pool graduates, not an empty pool. TxWhy reads the pool account through Meteora's SDK and answers with the room left (SOL raised so far, the graduation threshold, what the buy puts in): buy at most that, or send swap2 in partial-fill mode, which takes what the curve can still give.

From replaying real landed failures through the repair engine, around the clock since September 21, 2026. Every verdict and its reason is on the failure index.

Have the transaction that failed with this?

Paste its signature. TxWhy shows the exact instruction and inner call that raised the error, and rebuilds the transaction when the cause is one it can fix (compute limit, expired blockhash, priority fee, a stale swap quote or a moved limit).

Code 6033 means something else in other programs

Custom codes are private to each program. Check which program actually raised it: it is the innermost failed call, not necessarily the program you called.