RPC error -32015: Transaction version is not supported

Last updated: November 1, 2026

At a glance

Cause

Versioned transactions can load extra accounts through address lookup tables, which changes how account keys are read. A client written for legacy transactions could misread them, so the node refuses to return one unless the request says it understands the format. Without maxSupportedTransactionVersion, the node only returns legacy transactions and answers -32015 for the rest. Routers and bots commonly send version 0 transactions, so code tested against old legacy signatures can start failing on new ones.

Solution

1. Add "maxSupportedTransactionVersion": 0 to the config object of getTransaction and getBlock.
2. Update every call site, including retries and backfill jobs that build their own request.
3. Read meta.loadedAddresses as well as message.accountKeys, or you will miss accounts loaded from lookup tables.
4. Check the version field in the response before assuming the legacy layout.

curl https://triport.io/sol \
  -H "x-token: $TRIPORT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0", "id": 1,
    "method": "getTransaction",
    "params": ["<signature>", {
      "encoding": "jsonParsed",
      "maxSupportedTransactionVersion": 0
    }]
  }'

Example

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32015,
    "message": "Transaction version (0) is not supported by the requesting client. Please try the request again with the following configuration parameter: \"maxSupportedTransactionVersion\": 0"
  }
}