Solana error codes › 0x1791

custom program error: 0x1791 (6033)

0x1791 is decimal 6033. Its meaning depends on the program that failed: EndTimeBeforeStartTime in Pump.fun Bonding Curve, TimeRangeTooLarge in PumpSwap AMM, InvalidRewardInitParam in Raydium AMM V3 (CLMM) and 17 more below.

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

0x1791 by program

ProgramError
Pump.fun Bonding CurveEndTimeBeforeStartTime
PumpSwap AMMTimeRangeTooLarge
Raydium AMM V3 (CLMM)InvalidRewardInitParam
Invalid reward init param
Meteora DLMMMissingOracle
Missing oracle account
Meteora CP AMM (DAMM V2)IdenticalRewardDuration
Reward duration is the same
Meteora Dynamic Bonding CurveSwapAmountIsOverAThreshold
Swap amount is over a threshold
Orca WhirlpoolsMultiplicationOverflow
Multiplication overflow
The name points to a checked arithmetic failure inside the program, often from extreme amounts or an outdated client.
OKX DEX Aggregation Router V2InvalidPlatformFeeRate
Invalid platform fee rate
BoopTokenNameTooShort
Token name too short
Meteora AMMUpdateTimeConstraint
Update time constraint violated
Drift V2ReferrerAndReferrerStatsAuthorityUnequal
Heaven DEXCannotUpdateLpOpenTime
Cannot update lp open time
Jupiter DCAKeeperShortchanged
Keeper Shortchanged
Magic Eden V2InvalidPlatformFeeBp
Invalid platform fee bp
Metaplex Auction HouseAuctionHouseNotDelegated
Auction House not delegated.
Metaplex BubblegumDecompressionDisabled
Decompression disabled for this tree.
The name points to a feature or pool state that currently blocks this action.
Metaplex Candy MachineNoChangingCollectionDuringMint
Can't change collection settings after items have begun to be minted
Metaplex Fixed Price SaleCreatorsIsEmpty
Creators is empty
OpenBook V2MarketHasNotExpired
The Market has not expired yet.
TensorMaxTakerSellCountExceeded
max taker sell count exceeded, pool cannot buy anymore NFTs

Same code, other formats

custom program error: 0x1791 · {"Custom":6033} · Custom(6033) · Error Number: 6033

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.

← 0x1790 · 0x1792 → · 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.