Solana SPL op failing with 'IncorrectProgramId' or a transfer-fee error? Token-2022 vs Token

Solana has two token programs now: the classic SPL Token program and Token-2022 (Token Extensions). They look alike, but they're different on-chain programs — and code written for one breaks on the other with IncorrectProgramId, or silently under-delivers because of a fee it didn't account for.

IncorrectProgramId: wrong program for the mint

'incorrect program id for instruction' means you routed an instruction to the classic SPL Token program for a mint that's owned by Token-2022 (or the reverse). The two programs have different program ids and aren't interchangeable.

Fix: detect which program owns the mint (check the mint account's owner) and route every instruction — transfer, ATA creation, approve — to the matching program. Don't hardcode the classic Token program id.

Transfer fees: use TransferCheckedWithFee

Other Token-2022 extensions to expect

• Transfer hooks. The mint requires extra accounts on transfer (extra-account-metas) — your transfer must include them or it fails.
• Non-transferable / permanent-delegate. Some mints are non-transferable, or have a permanent delegate that can move tokens. Handle these as intended behaviour, not a bug.

For agents handling Solana tokens

An agent that assumes every mint is classic SPL will break on Token-2022. diagnose_infra_error returns the token2022 family and points at the specific extension — wrong program, transfer fee, hook — with the fix:

diagnose_infra_error({error: "incorrect program id for instruction token-2022"})
// → { family: "token2022",
//      fix: "mint is Token-2022 — route instructions to the Token-2022 program, not classic SPL Token" }