Solana error codes › JSON-RPC -32015
Transaction version (<n>) is not supported by the requesting client
Add maxSupportedTransactionVersion: 0 to getTransaction or getBlock so versioned transactions are returned.
JSON-RPC server errors come from the RPC node, not from a program. Codes −32001 to −32022 are defined by the Solana validator software (Agave).
| -32001 | BlockCleanedUp |
| -32002 | SendTransactionPreflightFailure |
| -32003 | TransactionSignatureVerificationFailure |
| -32004 | BlockNotAvailable |
| -32005 | NodeUnhealthy |
| -32006 | TransactionPrecompileVerificationFailure |
| -32007 | SlotSkipped |
| -32008 | NoSnapshot |
| -32009 | LongTermStorageSlotSkipped |
| -32010 | KeyExcludedFromSecondaryIndex |
| -32011 | TransactionHistoryNotAvailable |
| -32012 | ScanError |
| -32013 | TransactionSignatureLenMismatch |
| -32014 | BlockStatusNotAvailableYet |
| -32015 | UnsupportedTransactionVersion |
| -32016 | MinContextSlotNotReached |
| -32017 | EpochRewardsPeriodActive |
| -32018 | SlotNotEpochBoundary |
| -32019 | LongTermStorageUnreachable |
| -32020 | FilterTransactionNotFound |
| -32021 | NoSlotHistory |
| -32022 | LeaderScheduleIdentityNotFound |
Source: Agave rpc-client-api custom_error.rs, 2026-11-16.