Solana error codes › JSON-RPC -32003

Solana RPC error -32003 TransactionSignatureVerificationFailure

Transaction signature verification failure

A signature does not match the transaction. A required signer is missing or the message changed after signing.

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).

All Solana RPC errors

-32001BlockCleanedUp
-32002SendTransactionPreflightFailure
-32003TransactionSignatureVerificationFailure
-32004BlockNotAvailable
-32005NodeUnhealthy
-32006TransactionPrecompileVerificationFailure
-32007SlotSkipped
-32008NoSnapshot
-32009LongTermStorageSlotSkipped
-32010KeyExcludedFromSecondaryIndex
-32011TransactionHistoryNotAvailable
-32012ScanError
-32013TransactionSignatureLenMismatch
-32014BlockStatusNotAvailableYet
-32015UnsupportedTransactionVersion
-32016MinContextSlotNotReached
-32017EpochRewardsPeriodActive
-32018SlotNotEpochBoundary
-32019LongTermStorageUnreachable
-32020FilterTransactionNotFound
-32021NoSlotHistory
-32022LeaderScheduleIdentityNotFound

Source: Agave rpc-client-api custom_error.rs, 2026-11-16.