Transaction signature verification failure (-32003)
Last updated:
At a glance
| Property | Value |
|---|---|
| Code | -32003 |
| Message | Transaction signature verification failure |
| Category | transaction |
Cause
One or more required signatures are missing or invalid: a signer keypair did not sign, the wrong message was signed, or the fee payer / required signer set does not match the transaction's account metas.
Solution
- Confirm every account marked as a signer actually signed the message.
- Verify the fee payer is included and signs first.
- Re-derive and re-sign the exact serialized message (no post-sign mutation).
- Check you are signing the v0/legacy message format your client expects.
Example
{
"id": 1,
"error": {
"code": -32003,
"message": "Transaction signature verification failure"
},
"jsonrpc": "2.0"
}FAQ
- Why does "Transaction signature verification failure" happen?
- One or more required signatures are missing or invalid: a signer keypair did not sign, the wrong message was signed, or the fee payer / required signer set does not match the transaction's account metas.
- How do I fix "Transaction signature verification failure"?
- Confirm every account marked as a signer actually signed the message. Verify the fee payer is included and signs first. Re-derive and re-sign the exact serialized message (no post-sign mutation). Check you are signing the v0/legacy message format your client expects.
- What is RPC error -32003?
- -32003 means: Transaction signature verification failure. One or more required signatures are missing or invalid: a signer keypair did not sign, the wrong message was signed, or the fee payer / required signer set does not match the transaction's account metas.