6000 per program. The same numeric code can mean different things in different programs - always pair the code with the program ID.
mint-redeem
Program ID (devnet):5MBjhNUUguLTPNR5WG6YBUUw7vUcxQ14ARw3NsS3rKu4
oracle
Program ID (devnet):5vxiCrDpFnQ2W5QtgZBC66K2XTC19bjVBjinGYYBsadC
clp
Program ID (devnet):8xauDRjw9XRyk4FE3hW1JKjD8nC87gfr59Xig1dJqLES
registry
Program ID (devnet):REGnHqnJMxLoRAKX5RqPd9VJGcZBNgmg4xs5bVGGTap
faucet
Program ID (devnet):9tUeQAPEtVSB68NSfvFAqfwaB74GuVxm6Zbp1hrMiNKY
How errors surface in clients
Anchor wraps program errors in transaction-level errors. The shape varies by SDK:web3.js error inspection:
Common error sequences
”User mint failed with OraclePriceUnavailable”
→ Oracle is Paused or stale beyond threshold. Likely the keeper is down or restarting. Wait 30 seconds, retry. If persistent, check the Discord #status channel.
”Mint failed with MintNotAllowedInStress”
→ Risk state is Stress. The keeper is detecting wide confidence or extended staleness. Check market.risk_state; surface to the user as “minting paused, redeem still works”.
”Mint failed with OICapExceeded”
→ The market has hit its cap. Either reduce your mint size (under-cap) or wait for OI to drop via redemptions.
”Mint failed with BelowMinimum”
→ Trying to mint less than 10 cUSDC. Bump up.
”All instructions fail with Unauthorized”
→ Wrong signer. Verify your keypair matches the expected authority for the instruction. For privileged ops, your pubkey must be market.keeper_authority (for keeper_*_single) or market.authority (for admin ops).
See also
FAQ
Common questions including error symptoms.
Glossary
What terms in error names mean.

