Custom program error

0x55

Appears in logs as custom program error: 0x5. Defined by 2 programs: SPL Token, System. Check which program failed in your logs.

Which one is yours?
The log line Program <id> failed: custom program error: 0x5 names the program that returned the code. Match that id to the program below. Anchor programs also print Error Code: … Error Number: … right above the failure.
SPL TokenTokenkegQfeZyiNwAJbNbGKPFXCWuBvf9Ss623VQ5DA

FixedSupply

“Fixed supply”

The mint has no mint authority, so no more tokens can ever be minted.

Common causes

  • Mint authority was set to None to make the supply fixed, and a later MintTo was attempted.

How to fix it

  • This is permanent by design. If you need more supply you must create a new mint.
Source definition ↗All SPL Token errors →
System11111111111111111111111111111111

AddressWithSeedMismatch

“provided address does not match addressed derived from seed”

The address you supplied does not equal the address derived from the given base, seed and owner.

Common causes

  • Deriving the address with one owner/program id and then passing a different one to the instruction.
  • A typo or encoding mismatch in the seed string between derivation and instruction.

How to fix it

  • Derive the address with PublicKey.createWithSeed(base, seed, programId) using exactly the same inputs you send on-chain.
  • Log both addresses client-side and compare before sending.
Source definition ↗All System errors →

Decode another error

Try:

Nearby codes

0x2InvalidMint0x3MintMismatch0x4OwnerMismatch0x6AlreadyInUse0x7InvalidNumberOfProvidedSigners0x8InvalidNumberOfRequiredSigners