Solana Raydium CPMM Account Parsing

Example code for parsing Solana Raydium CPMM accounts using Yellowstone geyser gRPC.

Beyond just tracking transactions, understanding the live state of Raydium's Constant Product Market Maker (CPMM) liquidity pools and their associated accounts is essential. These accounts hold critical, up-to-the-minute details about the pool's assets, configuration, and other vital metrics. This document will guide you through streaming and parsing real-time account updates for Raydium CPMM, providing immediate insights into its core liquidity mechanisms..

The complete source code for this project is available on GitHub.

Please feel free to clone the repository and try it out. Additionally, you will find other relevant and useful code examples related to gRPC and streaming here.

Step-by-Step Breakdown

This project consists of two key components:

Streaming Raydium CPMM Accounts via Yellowstone gRPC
Decoding those accounts using the program's IDL

Streaming Accounts Using gRPC

The first step involves initializing the Solana Yellowstone Client. You can get Solana Yellowstone gRPC access from the Shyft Dashboard. Please check out our gRPC Authentication Docs for more details.

Initializing the Client

Once you have the authentication details, you can initialize the client in the following manner,

import Client from "@triton-one/yellowstone-grpc";

const client = new Client(
  "YOUR-GRPC-ENDPOINT", //yellowstone grpc url
  "GRPC-ACCESS-TOKEN", //authentication token
  undefined
);

use yellowstone_grpc_client::{GeyserGrpcClient, Interceptor}

async fn connect(&self) -> anyhow::Result<GeyserGrpcClient<impl Interceptor>> {
     GeyserGrpcClient::build_from_shared(self.endpoint.clone())? //grpc url
            .x_token(Some(self.x_token.clone()))? //grpc auth token
            .connect_timeout(Duration::from_secs(10))
            .timeout(Duration::from_secs(10))
            .tls_config(ClientTlsConfig::new().with_native_roots())?
            .max_decoding_message_size(1024 * 1024 * 1024)
            .connect()
            .await
            .map_err(Into::into)
}

You can use any Yellowstone gRPC endpoint with this client. An access token is optional, as some gRPC services don't require authentication.

The Rust client supports several additional options, as demonstrated in the example above. Most of these options are also available for the TS client, where they are passed as the third argument to the Client constructor.

Specifying what data to stream from gRPC

To specify what on-chain data, we send a SubscribeRequest over the existing Solana Yellowstone gRPC client. These Request allows you to filter for specific accounts, transactions, slots, or other Solana on-chain events, giving you full control over the data you receive.

SubscribeRequests use filters to determine what type of on-chain data to stream. When streaming account-level data, the account filter plays a crucial role. Specifically, the owner field within the filter allows you to stream data for accounts owned by a particular Solana program.

const req: SubscribeRequest = {
  "slots": {},
  "accounts": {
    "pumpfun": {
      "account": [],
      "filters": [],
      "owner": ["CPMMoo8L3F4NbTegBCKVNunggL7H1ZpdTHKxQB5qKP1C"] // This field indicates 
    }
  },
  "transactions": {},
  "blocks": {},
  "blocksMeta": {},
  "accountsDataSlice": [],
  "commitment": CommitmentLevel.PROCESSED, // Subscribe to processed blocks for the fastest updates
  "entry": {},
  "transactionsStatus": {}
}

let mut accounts: AccountFilterMap = HashMap::new();

accounts.insert(
    "accountData".to_owned(),
    SubscribeRequestFilterAccounts {
        account: vec![],
        owner: vec!["CPMMoo8L3F4NbTegBCKVNunggL7H1ZpdTHKxQB5qKP1C"],
        nonempty_txn_signature: None,
        filters: vec![]
    },
);
Ok(SubscribeRequest {
    accounts,
    slots: HashMap::default(),
    transactions: HashMap::default(),
    transactions_status: HashMap::default(),
    blocks: HashMap::default(),
    blocks_meta: HashMap::default(),
    entry: HashMap::default(),
    commitment: Some(CommitmentLevel::Processed as i32),
    accounts_data_slice: Vec::default(),
    ping: None,
    from_slot: None,
})

Once established, the stream will begin sending data directly to your application. You have the flexibility to modify your subscription on the fly, allowing you to change the data specifications you receive without stopping your stream. For more details on reconnecting and re-starting the stream from a specific slot, or closing your gRPC connection, you can find additional information in our documentation.

Decoding the received accounts

When account data updates on-chain, it's immediately sent over the stream. To make sense of this raw information, we need to decode it. In JavaScript/TypeScript, we typically use BorshAccountCoder from @coral-xyz/anchor to parse the account data like this. But in cases where the IDL is not available, we define the account structure. This is one such case.

On Rust however, we can use the Solores generated IDL like in our transaction parsing example.


import base58 from "bs58";
import { blob, bool, i128, i64, publicKey, s32, seq, struct, u128, u16, u32, u64, u8 } from "../layout-type";
import { bnLayoutFormatter } from "./bn-layout-formatter";



export const CpPoolInfoLayout = struct([
  blob(8),

  publicKey("configId"),
  publicKey("poolCreator"),
  publicKey("vaultA"),
  publicKey("vaultB"),

  publicKey("mintLp"),
  publicKey("mintA"),
  publicKey("mintB"),

  publicKey("mintProgramA"),
  publicKey("mintProgramB"),

  publicKey("observationId"),

  u8("bump"),
  u8("status"),

  u8("lpDecimals"),
  u8("mintDecimalA"),
  u8("mintDecimalB"),

  u64("lpAmount"),
  u64("protocolFeesMintA"),
  u64("protocolFeesMintB"),
  u64("fundFeesMintA"),
  u64("fundFeesMintB"),
  u64("openTime"),

  seq(u64(), 32),
]);
export function decodeRaydiumCpPool(buffer: Buffer) {
  const cpDecode =  CpPoolInfoLayout.decode(buffer);
  bnLayoutFormatter(cpDecode);
  return cpDecode;
}

export function base64ToBase58(data: string) {
  return base58.encode(Buffer.from(data, 'base64'));
}

use raydium_cp_swap_interface::{accounts::{PoolState,
            AMM_CONFIG_ACCOUNT_DISCM,
            AmmConfig,
            AmmConfigAccount,
            PoolStateAccount,
            POOL_STATE_ACCOUNT_DISCM,
            OBSERVATION_STATE_ACCOUNT_DISCM,
            ObservationState,              
            ObservationStateAccount
}};

pub fn decode_account_data(buf: &[u8]) -> Result<DecodedAccount, AccountDecodeError> {
    if buf.len() < 8 {
        return Err(AccountDecodeError {
            message: "Buffer too short to contain a valid discriminator.".to_string(),
        });
    }

    let discriminator: [u8; 8] = buf[..8].try_into().expect("Failed to extract first 8 bytes");

    match discriminator {
        POOL_STATE_ACCOUNT_DISCM => {
            let data = PoolStateAccount::deserialize(buf)
                .map_err(|e| AccountDecodeError {
                    message: format!("Failed to deserialize PoolState: {}", e),
                })?;
            println!("\nDecoded PoolState Structure: {:#?}", data);
            Ok(DecodedAccount::PoolState(data.0))
        }
        AMM_CONFIG_ACCOUNT_DISCM => {
            let data = AmmConfigAccount::deserialize(buf)
                .map_err(|e| AccountDecodeError {
                    message: format!("Failed to deserialize AmmConfig: {}", e),
                })?;
            println!("\nDecoded AmmConfig Structure: {:#?}", data);
            Ok(DecodedAccount::AmmConfig(data.0))
        }
        _ => Err(AccountDecodeError {
            message: "Account discriminator not found.".to_string(),
        }),
    }
}

Important Links

Solana gRPC Documentation – In-depth technical docs for implementing real-time streaming with Yellowstone gRPC and Geyser plugin on Solana.
Blogs on Solana gRPC Streaming – Guides, use cases, and performance benchmarks for building low-latency Solana applications using gRPC-based infrastructure.
Solana DeFi Code Snippets & Examples – Ready-to-use code snippets and integrations for common DeFi protocols, transaction parsers, and real-time Solana data streaming use cases.

PreviousSolana Raydium CPMM Transaction Parsing NextRaydium Launchlab

Last updated 8 months ago

hashtagStep-by-Step Breakdown

hashtagStreaming Accounts Using gRPC

hashtagInitializing the Client

hashtagSpecifying what data to stream from gRPC

hashtagDecoding the received accounts

hashtagImportant Links