Zero-Latency DeFi: Parsing Raw Solana AMM Accounts in Rust

Originally published on xroot.dev.

In high-frequency Web3 infrastructure, relying on a TypeScript SDK or a third-party pricing API means you are already too late.

If you are building an arbitrage bot, a sniper, or a real-time indexer on Solana, reading data through abstracted REST endpoints introduces hundreds of milliseconds of latency. To build institutional-grade infrastructure, you have to bypass the middleman. You need to pull the raw binary state of the Automated Market Maker (AMM) directly from the RPC node and deserialize it natively in memory.

Here is how to reverse-engineer Solana DeFi pools and parse raw account data in Rust at microsecond speed.

The Anatomy of a Solana Account & The Anchor Discriminator

Beneath the abstractions of the Solana ecosystem, an account's data is fundamentally just a continuous array of bytes (&[u8]). When a smart contract writes to an account, it serializes its state into this raw byte buffer.

If the AMM was built using the Anchor framework — which the vast majority of modern Solana DeFi protocols are — the account data doesn't just start with the struct variables. Anchor prepends an 8-byte discriminator to the beginning of the data payload.

This discriminator is calculated using the first 8 bytes of the SHA256 hash of the string "account:StructName". It acts as a safety check: if you try to deserialize an AMM pool account but the first 8 bytes don't match the expected hash, the program knows you passed the wrong account type and immediately aborts.

Bytes 0–7 (Anchor Discriminator) → Bytes 8–N (Raw struct data (Borsh-serialized))

To parse the account data yourself, your first step is always identifying and slicing off those first 8 bytes.

Reverse-Engineering the AMM Struct

You cannot parse binary data without knowing its exact memory layout. We need to map the byte layout of the DeFi pool — such as a Raydium CPMM or a pump.fun bonding curve — into a tightly packed Rust struct.

Instead of paying the "Borsh tax" (the CPU overhead of standard deserialization), we will engineer this for zero-copy deserialization. By using the bytemuck crate and #[repr(C)], we force the Rust compiler to lay out our struct exactly as it appears in the raw memory buffer.

use bytemuck::{Pod, Zeroable};
use solana_program::pubkey::Pubkey;

// #[repr(C)] guarantees predictable memory alignment
// matching the on-chain byte array.
#[repr(C)]
#[derive(Clone, Copy, Debug, Pod, Zeroable)]
pub struct BondingCurveState {
    pub virtual_token_reserves: u64,
    pub virtual_sol_reserves:   u64,
    pub real_token_reserves:    u64,
    pub real_sol_reserves:      u64,
    pub token_total_supply:     u64,
    pub complete:               u8, // u8 instead of bool for predictable byte sizing
}

By deriving Pod (Plain Old Data) and Zeroable, we are making a strict contractual promise to the Rust compiler: this struct contains no pointers, no dynamic strings, and is simply a safe bag of bytes. The compiler enforces this at compile time — if you accidentally include a Vec or a String, it will refuse to compile.

Rule: Every field in a Pod struct must have a known, fixed size. Use u8 instead of bool, and [u8; 32] instead of Pubkey if Pubkey doesn't implement Pod. Predictable sizing is the contract.

Deserialization at Microsecond Speed

When you request an account from a Solana RPC node, the node returns the data as a base64-encoded string. A junior developer would decode the string, parse it into JSON, and map it to a TypeScript object. We are going to decode the base64 string, strip the 8-byte Anchor discriminator, and instantly cast the remaining bytes directly to our Rust struct memory using a zero-copy pointer.

use base64::{Engine as _, engine::general_purpose::STANDARD};

pub fn parse_bonding_curve(base64_data: &str) -> BondingCurveState {
    // 1. Decode the base64 RPC response into a raw byte vector
    let raw_bytes = STANDARD
        .decode(base64_data)
        .expect("Failed to decode base64");

    // 2. Strip the 8-byte Anchor Discriminator
    //    (sha256("account:BondingCurveState")[..8])
    let account_data = &raw_bytes[8..];

    // 3. Zero-Copy Cast: reinterpret the bytes directly as the struct.
    //    This bypasses heap allocation entirely — nanosecond execution.
    let curve_state: &BondingCurveState = bytemuck::from_bytes(account_data);

    *curve_state
}

Because we aren't allocating new memory or reading field-by-field, this execution takes nanoseconds. The bytemuck::from_bytes call does not copy a single byte — it reinterprets the existing memory address as a pointer to our struct. We didn't move the library; we just pointed our code to the shelf.

TypeScript SDK (REST + JSON parse) — 200–800 ms

Rust + Borsh deserialization — ~10–50 µs

Rust + bytemuck zero-copy cast — ~100–500 ns ✓

Calculating Real-Time Price (The Business Value)

Data engineering is useless without applying business logic. Now that the raw AMM state is held securely in our Rust backend's memory, we can calculate the real-time token price instantly. Standard AMMs use the constant product formula (x × y = k). By extracting the virtual reserves from our parsed struct, calculating the exact price natively in Rust becomes trivial.

impl BondingCurveState {
    pub fn get_token_price_in_sol(&self) -> f64 {
        // Prevent division-by-zero panics
        if self.virtual_token_reserves == 0 {
            return 0.0;
        }

        // Apply the constant product ratio: price = y / x
        let sol_reserves   = self.virtual_sol_reserves as f64;
        let token_reserves = self.virtual_token_reserves as f64;

        sol_reserves / token_reserves
    }
}

If we hook this logic up to a NATS/WebSocket pipeline — as covered in the Solana Firehose ingestion series — we can stream raw base64 account data, zero-copy deserialize it, calculate the price, and fire it to a trading algorithm before a standard SDK even finishes opening its HTTP connection.

Note: For real-world use, you should validate the discriminator manually before calling bytemuck::from_bytes. A mismatched account type will cause a panic in debug mode and undefined behavior in release. Always assert: &raw_bytes[..8] == EXPECTED_DISCRIMINATOR.

Conclusion & System Impact

By reverse-engineering the binary state of Solana accounts and leveraging Rust's bytemuck, we achieve a fundamental infrastructure advantage:

• Zero RPC Pricing Overhead: We don't pay for third-party price feed APIs. We read directly from chain truth.
• Microsecond Deserialization: Dropping standard JSON/Borsh parsing reduces CPU overhead to near zero — from milliseconds to nanoseconds per event.
• Direct Chain Truth: We read the exact mathematical reserves of the pool, making our metrics immune to frontend lag or aggregator delays.
• Composable with NATS Pipelines: This parsing layer slots directly into the high-throughput pipeline described in the 3-part Solana data pipeline series.