Solana error codes › 0x1779

custom program error: 0x1779 (6009)

0x1779 is decimal 6009. Its meaning depends on the program that failed: NonZeroMinimumOutAmountNotSupported in Jupiter Aggregator v6, NewSizeShouldBeGreaterThanCurrentSize in Pump.fun Bonding Curve, InvalidQuoteMint in PumpSwap AMM and 29 more below.

Programs that use Anchor-style numbering start their own error list at 6000 (0x1770), so 6009 is the error at index 9 of the failing program's list. The same number means something different in every program.

0x1779 by program

ProgramError
Jupiter Aggregator v6NonZeroMinimumOutAmountNotSupported
Non zero minimum out amount not supported
Pump.fun Bonding CurveNewSizeShouldBeGreaterThanCurrentSize
new_size should be > current_size
PumpSwap AMMInvalidQuoteMint
Raydium CPMM (CP Swap)InitLpAmountTooLess
Init lp amount is too less(Because 100 amount lp will be locked)
Raydium AMM V3 (CLMM)TickUpperOverflow
The tick must be lesser than, or equal to the maximum tick(443636)
The name points to a checked arithmetic failure inside the program, often from extreme amounts or an outdated client.
Meteora DLMMBinArrayNotFound
Bin array not found
Meteora CP AMM (DAMM V2)InvalidAuthorityToCreateThePool
Invalid authority to create the pool
The name points to a permission check: the wrong signer or owner account was passed.
Meteora Dynamic Bonding CurveInvalidCollectFeeMode
Invalid collect fee mode
Orca WhirlpoolsTickNotFound
Tick not found within tick array
Raydium LaunchpadNoAssetsToCollect
No assets to collect
MoonshotInvalidCurveType
Invalid curve type.
Jupiter Aggregator v4NonZeroMinimumOutAmountNotSupported
Non zero minimum out amount not supported
OKX DEX Aggregation Router V2InvalidSourceTokenAccount
Invalid source token account
BoopInvalidBondingCurveStatus
Invalid bonding curve status
Meteora AMMMismatchedTokenMint
Token mint mismatched
BonkSwapPriceLimitExceeded
Price limit exceeded
Drift V2UserAccountAndUserPositionsAccountMismatch
User Account And User Positions Account Mismatch
Heaven DEXInvalidFeeMode
Invalid fee mode
Jupiter DCANoUserInATA
userInAta not passed in
Jupiter Limit OrderOrderNotExpired
Magic Eden V2CannotExchangeSOLForSol
Cannot exchange sol for sol
Metaplex Auction HouseCannotExchangeSOLForSol
Cannot exchange sol for sol
Metaplex AuctioneerCannotCancelHighestBid
The highest bidder is not allowed to cancel
Metaplex BubblegumCreatorHashMismatch
Provided creator Vec must result in provided creator hash
Metaplex Candy MachineTokenTransferFailed
Token transfer failed
Metaplex Fixed Price SalePiecesInOneWalletIsTooMuch
Pieces in one wallet cannot be greater than Max Supply value
Metaplex HydraInvalidHoldingAccount
Holding account does not match the config
Metaplex Token EntanglerMetadataDoesntExist
Metadata doesn't exist
Obric V2WithdrawCausesUnfairPrice
Withdrawal causes unfair price change
OpenBook V2InvalidInputPegLimit
Peg limit should be greater than zero
TensorArithmeticError
arithmetic error
TON Whales HoldersLimitReached

Same code, other formats

custom program error: 0x1779 · {"Custom":6009} · Custom(6009) · Error Number: 6009

How to tell which program failed

  1. Open the failed transaction in an explorer (or the simulation result in your code) and read the program logs.
  2. Find the line Program <address> failed: custom program error: 0x…. If several programs failed with the same code, the first one listed is the deepest call, the one that raised it.
  3. Look the code up for that program. Error processing Instruction 2 is a zero-based index, so it points to the third instruction (often the first one after two Compute Budget instructions).

Decode your exact error

Free, no sign-up, nothing to connect. Works offline from a bundled list; we do not look anything up on-chain.

Swapping a token you do not know? A free Rugsight check shows mint and freeze authority, Token-2022 extensions, holder concentration and liquidity before you trade.

← 0x1778 · 0x177a → · All Solana error codes

Data: program error lists from published IDLs (solana-idls 1.2.1, MIT) and the System, SPL Token, Token-2022 and Associated Token Account source code, snapshot 2026-11-16. Programs can be upgraded and add or change errors; the failing program's current IDL is the final word.