Solana error codes › 0x1773

custom program error: 0x1773 (6003)

0x1773 is decimal 6003. Its meaning depends on the program that failed: MissingPlatformFeeAccount in Jupiter Aggregator v6, TooLittleSolReceived in Pump.fun Bonding Curve, TooLittlePoolTokenLiquidity in PumpSwap AMM and 29 more below.

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

Pump.fun Bonding Curve: TooLittleSolReceived

Selling would return less SOL than the minimum the transaction allowed (the sell's slippage limit).

What to do: The price moved down before the sell landed. Retry with a fresh quote.

Meteora DLMM: ExceededAmountSlippageTolerance

The swap amount is outside the slippage tolerance set in the transaction.

What to do: Retry with a fresh quote; a higher slippage allows a worse price.

0x1773 by program

ProgramError
Jupiter Aggregator v6MissingPlatformFeeAccount
Missing platform fee account
Pump.fun Bonding CurveTooLittleSolReceived
slippage: Too little SOL received to sell the given amount of tokens.
Selling would return less SOL than the minimum the transaction allowed (the sell's slippage limit).
PumpSwap AMMTooLittlePoolTokenLiquidity
Raydium CPMM (CP Swap)InvalidInput
Raydium AMM V3 (CLMM)AccountLack
Account lack
Meteora DLMMExceededAmountSlippageTolerance
Exceeded amount slippage tolerance
The swap amount is outside the slippage tolerance set in the transaction.
Meteora CP AMM (DAMM V2)PoolDisabled
Pool disabled
The name points to a feature or pool state that currently blocks this action.
Meteora Dynamic Bonding CurveExceedMaxFeeBps
Exceeded max fee bps
Orca WhirlpoolsTickArrayIndexOutofBounds
Attempt to search for a tick-array failed
Raydium LaunchpadInputNotMatchCurveConfig
The input params are not match with curve type in config
MoonshotSlippageOverflow
The cost amount is not in the allowed slippage interval.
The name points to a slippage or minimum-output check: the price moved past the limit set in the transaction.
Jupiter Aggregator v4MissingPlatformFeeAccount
Missing platform fee account
OKX DEX Aggregation Router V2MinReturnMustBeGreaterThanZero
min_return must be greater than 0
The name points to a slippage or minimum-output check: the price moved past the limit set in the transaction.
BoopConfigNotInitialized
Config not initialized
The name points to account state: an account was expected to exist (or not exist) already.
Meteora AMMFeeCalculationFailure
Fee calculation failure
BonkSwapTooMuchShares
Too much shares provided
Drift V2InsufficientCollateral
Insufficient collateral
Heaven DEXInvalidTaxationMode
Invalid taxation mode
Jupiter DCATooFrequent
Too frequent DCA cycle
Jupiter Limit OrderInvalidCalculation
Magic Eden V2IncorrectOwner
Metaplex Auction HouseIncorrectOwner
Metaplex AuctioneerAuctionActive
Auction has not ended yet
Metaplex BubblegumUnsupportedSchemaVersion
Metaplex Candy MachineIndexGreaterThanLength
Index greater than length!
Metaplex Fixed Price SaleDescriptionIsTooLong
Description string variable is longer than allowed
Metaplex HydraSharesArentAtMax
All available shares must be assigned to a member
Metaplex Token EntanglerIncorrectOwner
Obric V2InvalidConcentrationArg
Invalid concentration argument
OpenBook V2InvalidInputMarketFees
Taker fees should be positive and if maker fees are negative, greater or equal to their abs value
TensorWrongPoolType
operation not permitted on this pool type
TON Whales HoldersIncorrectWithdrawA

Same code, other formats

custom program error: 0x1773 · {"Custom":6003} · Custom(6003) · Error Number: 6003

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.

← 0x1772 · 0x1774 → · 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.