Solana error codes › 0x7d3

custom program error: 0x7d3 (2003)

0x7d3 is decimal 2003. Its meaning depends on the program that failed: ConstraintRaw in Anchor Framework.

Codes 100 to 5999 are reserved by the Anchor framework. If the failing program is built with Anchor, this is a framework error (shown below when Anchor defines it). Native programs that are not built with Anchor can also use these numbers.

Anchor Framework: ConstraintRaw

A custom `constraint = ...` check on one of the accounts returned false.

What to do: Read the program logs: Anchor prints the account name that failed. Check that account's state against the constraint in the program source.

Anchor framework

Anchor FrameworkConstraintRaw
A raw constraint was violated
A custom `constraint = ...` check on one of the accounts returned false.

Applies to any program built with Anchor that does not define 2003 itself.

Same code, other formats

custom program error: 0x7d3 · {"Custom":2003} · Custom(2003) · Error Number: 2003

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.

← 0x7d2 · 0x7d4 → · 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.