Solana error codes › 0x1d

custom program error: 0x1d (29)

0x1d is decimal 29. Its meaning depends on the program that failed: InvalidInput in Raydium AMM V4, NoAuthorityExists in Token-2022, EndDateNotArrived in Metaplex NFT Packs and 1 more below.

Small numbers like this are used by native programs (System, SPL Token, Token-2022, Raydium AMM v4 and others), each with its own list, so the meaning depends on which program failed.

0x1d by program

ProgramError
Raydium AMM V4InvalidInput
Token-2022NoAuthorityExists
No authority exists to perform the desired operation
Metaplex NFT PacksEndDateNotArrived
Can't close the pack before end date
Metaplex Token MetadataOneTimePrintingAuthMintMismatch
The One Time Printing Auth mint does not match that on the master edition!

Same code, other formats

custom program error: 0x1d · {"Custom":29} · Custom(29) · Error Number: 29

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.

← 0x1c · 0x1e → · 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.