debug-program

Get the exact error from the transaction signature using solana confirm -v, then simulate the transaction with connection.simulateTransaction to see full program logs. Inspect account state for existence, ownership, and balance before applying a fix.

Error 6000 is the first custom error in your program's #[error_code] enum, with 6001, 6002 mapping to subsequent variants. Error 2003 is ConstraintSeeds, meaning client-side PDA derivation seeds do not match what the program expects.

Read the invoke depth markers in transaction logs: invoke [1] is your program, invoke [2] is a CPI call, and deeper numbers are nested calls. The deepest failing invoke is usually the root cause, not your top-level program.

Recent blockhashes expire after roughly 60 seconds, so transactions that take too long to build or sign become invalid. Fetch a fresh blockhash with getLatestBlockhash right before sending and use lastValidBlockHeight for retry logic.

Yes, use Surfpool with surfpool start --network mainnet to fork mainnet state and replay the failing transaction locally. This gives you execution traces, compute unit usage per instruction, and account state changes without spending real SOL.