# Solana Pump AMM Account Parsing For any Solana dApp, trading bots, or real-time analytics platform, efficient account data access is important. Solana gRPC streaming, powered by technologies like the Geyser plugin and Yellowstone, provides a fast, low-latency way to get data, far better than older RPC calls or WebSockets. In this document, we will explore how we can stream and parse Pump Swap account data using Solana Yellowstone gRPCs {% hint style="success" %} The complete source code for this project is available on GitHub. * [TypeScript](https://github.com/Shyft-to/solana-defi/tree/main/PumpFun/Typescript/grpc-stream-and-parse-pump-fun-amm-account) * [Rust](https://github.com/Shyft-to/solana-defi/tree/main/PumpFun/Rust/grpc-stream-and-parse-pump-fun-amm-account) 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](https://github.com/Shyft-to/solana-defi). {% endhint %} ## Step-by-Step Breakdown This project consists of two key components: 1. Streaming Pump Swap Accounts via Yellowstone gRPC 2. 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](https://docs.shyft.to/docs#authentication) for more details. #### Initializing the Client Once you have the authentication details, you can initialize the client in the following manner, {% tabs %} {% tab title="TypeScript" %} ```typescript import Client from "@triton-one/yellowstone-grpc"; const client = new Client( "YOUR-GRPC-ENDPOINT", //yellowstone grpc url "GRPC-ACCESS-TOKEN", //authentication token undefined ); ``` {% endtab %} {% tab title="Rust" %} ```rust use yellowstone_grpc_client::{GeyserGrpcClient, Interceptor} async fn connect(&self) -> anyhow::Result> { 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) } ``` {% endtab %} {% endtabs %} 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 ](https://docs.shyft.to/docs#what-are-subscribe-requests)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. {% tabs %} {% tab title="TypeScript" %} {% code overflow="wrap" %} ```typescript const req: SubscribeRequest = { "slots": {}, "accounts": { "pumpfun": { "account": [], "filters": [], "owner": ["pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA"] // This field indicates } }, "transactions": {}, "blocks": {}, "blocksMeta": {}, "accountsDataSlice": [], "commitment": CommitmentLevel.PROCESSED, // Subscribe to processed blocks for the fastest updates "entry": {}, "transactionsStatus": {} } ``` {% endcode %} {% endtab %} {% tab title="Rust" %} {% code overflow="wrap" %} ```rust let mut accounts: AccountFilterMap = HashMap::new(); accounts.insert( "accountData".to_owned(), SubscribeRequestFilterAccounts { account: vec![], owner: vec!["pAMMBay6oceH9fJKBRHGP5D4bD4sWpmSwMn52FMfXEA"], 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, }) ``` {% endcode %} {% endtab %} {% endtabs %} For example, to stream Pump.fun transaction accounts, you can set the `owner` field to the Pump Swap program ID. This ensures that only accounts associated with the Pump Swap program are streamed in real-time—ideal for use cases like crypto trading bots, on-chain analytics, or DeFi dashboards requiring program-specific data. Once established, the stream will begin sending data directly to your application. You have the flexibility to [**modify your subscription**](https://docs.shyft.to/solana-yellowstone-grpc/docs/getting-started/modify-grpc-subscribe-request) **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**](https://docs.shyft.to/solana-yellowstone-grpc/docs/getting-started/replaying-slots-with-grpc)**, or** [**closing your gRPC connection**](https://docs.shyft.to/solana-yellowstone-grpc/docs/getting-started/gracefully-closing-a-grpc-connection), you can find additional information in our [documentation](https://docs.shyft.to/solana-yellowstone-grpc/docs). ### Decoding the received accounts As soon as the accounts are updated on chain, the updated account data is sent over the stream. The next step involves decoding the data. For JS/TS, we use `BorshAccountCoder` from @coral-xyz/anchor to parse the account data in the following manner. On Rust however, we can use the Solores generated IDL like in our [transaction parsing](https://docs.shyft.to/solana-yellowstone-grpc/examples/pumpfun/solana-grpc-pumpfun-transaction-parsing) example. {% tabs %} {% tab title="TypeScript" %} ```typescript import { BorshAccountsCoder } from "@coral-xyz/anchor"; const program_idl = JSON.parse(fs.readFileSync('./Idl/pump_amm_0.1.0.json', 'utf8')); const accountCoder = new BorshAccountsCoder(program_idl); const decodedData = accountCoder.decodeAny(data.account.account.data); ``` {% endtab %} {% tab title="Rust" %} ```rust use pump_interface::accounts::{BondingCurve, BondingCurveAccount, Global, GlobalAccount, BONDING_CURVE_ACCOUNT_DISCM, GLOBAL_ACCOUNT_DISCM}, pub fn decode_account_data(buf: &[u8]) -> Result { 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_ACCOUNT_DISCM => { let data = PoolAccount::deserialize(buf) .map_err(|e| AccountDecodeError { message: format!("Failed to deserialize Pool: {}", e), })?; println!("\nDecoded Pool Amm Structure: {:#?}", data); Ok(DecodedAccount::Pool(data.0)) } GLOBAL_CONFIG_ACCOUNT_DISCM => { let data = GlobalConfigAccount::deserialize(buf) .map_err(|e| AccountDecodeError { message: format!("Failed to deserialize GlobalConfigz: {}", e), })?; println!("\nDecoded GlobalConfig Structure: {:#?}", data); Ok(DecodedAccount::GlobalConfig(data.0)) } _ => Err(AccountDecodeError { message: "Account discriminator not found.".to_string(), }), } } ``` {% endtab %} {% endtabs %} ### Important Links * [**Solana gRPC Documentation**](https://docs.shyft.to/solana-yellowstone-grpc/docs) – In-depth technical docs for implementing real-time streaming with **Yellowstone gRPC** and **Geyser plugin** on Solana. * [**Blogs on Solana gRPC Streaming**](https://blogs.shyft.to/) – Guides, use cases, and performance benchmarks for building **low-latency Solana applications** using **gRPC-based infrastructure**. * [**Solana DeFi Code Snippets & Examples**](https://github.com/Shyft-to/solana-defi/) – Ready-to-use code snippets and integrations for common **DeFi protocols**, **transaction parsers**, and **real-time Solana data streaming** use cases.