Solana: I try getTransaction and save to DB, I can’t find accountKeys in message, only staticAccountKeys

Troubleshooting: Getting Account Keys from getTransaction in Solana

As a developer working with the Solana blockchain, it’s not uncommon to encounter issues when trying to interact with the Solana network. In this article, we’ll delve into one common problem that can arise when using the getTransaction method on a Solana WebSocket connection: finding account keys in the message.

The Issue

When you call getTransaction on a Solana WebSocket connection, it returns a transaction object with various properties, including accountKeys. However, sometimes this information is not visible to your code. Specifically, if your application doesn’t set staticAccountKeys correctly, you won’t see the account keys in the message.

The Solution

To resolve this issue, let’s assume that the following lines of code are part of your Solana WebSocket connection:

const WS_URL = process.env.SOLANA_WS_URL || '

const connection = new Connection(WS_URL, 'confirmed');

const RAYDIUM_AMM_PROGRAM_ID = new PublicKey(...); // Initialize a public key for the AMM program

In this case, you’ll notice that staticAccountKeys is set to an empty array. This means that any account keys passed from the client to your Solana WebSocket connection will be ignored.

To fix this issue, you can either set staticAccountKeys correctly in your code or update the API endpoint to include account keys in the response data.

Option 1: Set staticAccountKeys Correctly

If you don’t want to expose any account keys from your AMM program, you can modify the API endpoint to omit them. For example:

const WS_URL = process.env.SOLANA_WS_URL || '

const connection = new Connection(WS_URL, 'confirmed');

const RAYDIUM_AMM_PROGRAM_ID = new PublicKey(...); // Initialize a public key for the AMM program


// API endpoint response data

const responseData = {

  transactions: [

    { account_keys: [new PublicKey('account-key-1')], type: 'getTransaction' },

    { account_keys: [new PublicKey('another-account-key-2')], type: 'getTransaction' }

  ]

};

Option 2: Update API Endpoint to Include Account Keys

If you want to include the account keys in your API endpoint response data, you can modify it as follows:

const WS_URL = process.env.SOLANA_WS_URL || '

const connection = new Connection(WS_URL, 'confirmed');

const RAYDIUM_AMM_PROGRAM_ID = new PublicKey(...); // Initialize a public key for the AMM program


// API endpoint response data

const responseData = {

  transactions: [

    { account_keys: [new PublicKey('account-key-1'), new PublicKey('another-account-key-2')], type: 'getTransaction' }

  ]

};

By setting staticAccountKeys correctly or updating the API endpoint to include account keys, you should now be able to see the account keys in your message when using the getTransaction method on a Solana WebSocket connection.

ethereum send miner pool processing