Real-Time Raydium Liquidity Events with Filtered gRPC

Raydium is the backbone of Solana DeFi. When a token graduates from Pump.fun, it lands on Raydium. When a new project launches, liquidity goes to Raydium first. If you're building a sniper bot, an LP tracker, or a rug-pull detector, Raydium liquidity events are your primary signal.

Raydium Events You Can Filter

Event	Description	Why It Matters
pool_create	New AMM pool initialized	First signal for new token listings — snipers react here
add_liquidity	LP tokens deposited	Growing liquidity = growing confidence
remove_liquidity	LP tokens withdrawn	Large removals can signal rug pulls
swap	Token swap executed	Volume tracking, price impact analysis

Pool Sniping Pattern

The most common use case: detect a new pool, verify the initial liquidity is above your threshold, and execute a buy within the same block. Here's the pattern:

const client = new Subglow({
  url: "grpc.subglow.io:443",
  apiKey: process.env.SUBGLOW_KEY,
  filter: ["raydium_v5"],
});

client.subscribe((tx) => {
  if (tx.type === "pool_create") {
    const { base_mint, quote_mint, initial_liquidity } = tx.parsed;

    // Skip low-liquidity pools (likely scams)
    if (initial_liquidity < 5_000) return;

    // Skip non-SOL quote tokens
    if (quote_mint !== "So11111111111111111111111111111111111111112") return;

    console.log(`New pool: ${base_mint}`);
    console.log(`Liquidity: $${initial_liquidity}`);
    // Execute buy logic here
  }
});

Rug Pull Detection

Monitor remove_liquidity events where a large percentage of total pool liquidity is being withdrawn. If a single wallet removes >50% of liquidity within minutes of pool creation, that's a strong rug signal.

Combining Pump.fun + Raydium Filters

The most powerful strategy uses both filters together: watch Pump.fun for tokens approaching migration (bonding curve >90%), then watch Raydium for the corresponding pool_create event. This gives you a 2-step early warning system.

With Subglow, you can subscribe to both filters on a single stream — no need to manage multiple connections.