// Use case
Every new token.
The instant it launches.
Monitor Pump.fun token creates, bonding curve buys, Raydium migrations, and Jupiter routing events in real-time. Pre-parsed JSON, under 5ms from slot confirmation — so your scanner sees every launch before the crowd.
Why token launch speed matters
On Pump.fun, every token starts life on a bonding curve. The price begins near zero and rises predictably as buyers pile in. Early participants — those who buy in the first few hundred milliseconds — routinely see 10-100x returns when a token catches momentum. Buyers who arrive even half a second late often pay 2-5x the initial price, and the math only gets worse from there.
The bonding curve lifecycle is ruthlessly time-sensitive. Once a token is created, the first wave of buys determines whether it graduates to Raydium or dies on the curve. Over 500 tokens launch on Pump.fun every single day, and more than 80% rug or flatline within the first few hours. The tokens that do survive can move from a $5k market cap to $500k in minutes. If your detection latency is measured in seconds, you are already priced out of the opportunity.
Hundreds of tokens created daily, each with a unique bonding curve and momentum profile
The vast majority of launches fail fast — early detection lets you filter signal from noise
Sub-5ms event delivery means you see the token create before the first speculative buy lands
Token lifecycle tracking
A Solana memecoin doesn't just appear on a DEX. It moves through a multi-stage lifecycle that starts on Pump.fun's bonding curve and — if it survives — graduates to Raydium and eventually routes through Jupiter. Subglow streams every stage of this lifecycle as structured events so you can build logic around each transition.
Token Create on Pump.fun
The moment a new token is created, Subglow delivers the mint address, token name, symbol, creator wallet, and bonding curve address. This is the earliest possible signal — the token exists on-chain but has zero buys. Your scanner evaluates the creator's history, token naming patterns, and metadata before the first speculative buyer arrives.
Early buys on bonding curve
As buyers start accumulating on the bonding curve, you receive each buy event with the buyer wallet, SOL amount, token amount, and current curve progress percentage. Tracking the rate of unique buyers and total volume in the first 30 seconds gives you a high-confidence signal for whether this token has real momentum or is a solo-wallet pump.
Migration to Raydium
When a Pump.fun token fills its bonding curve, it graduates — migrating liquidity to a Raydium pool. This is the inflection point where real money enters. Subglow fires a Migration event with the mint, the newly created Raydium pool address, and the initial liquidity amount. Graduation means larger position sizes become viable and AMM-based price discovery begins.
Pool Create on Raydium
The new Raydium pool goes live with a specific token pair and initial liquidity depth. You receive the pool address, base mint, quote mint, and the exact initial liquidity amount. This event is critical for bots that only trade tokens with confirmed DEX liquidity rather than bonding curve speculation.
Jupiter routing begins
Once a Raydium pool has sufficient liquidity, Jupiter's aggregator starts routing swaps through it. You receive each swap event with token-in, token-out, amounts, and the executing wallet. Sustained Jupiter volume is the strongest post-graduation signal that a token has real market demand beyond initial hype.
What data you get
Every event arrives as structured JSON with human-readable field names. No Borsh deserialization, no instruction discriminators, no byte-level parsing. Plug the data directly into your decision engine.
| Event | Source | Key fields |
|---|---|---|
| Token Create | Pump.fun | mint, name, symbol, creator, bondingCurve, timestamp |
| Early Buy | Pump.fun | mint, buyer, solAmount, tokenAmount, curveProgress |
| Migration | Pump.fun → Raydium | mint, raydiumPool, liquidityAmount |
| Pool Create | Raydium | poolAddress, baseMint, quoteMint, initialLiquidity |
| Swap | Jupiter | tokenIn, tokenOut, amountIn, amountOut, wallet |
Build with token launch data
Token launch monitoring is the foundation for an entire category of Solana trading tools. Subglow's pre-parsed event streams let you skip months of infrastructure work and go straight to building the logic that matters.
Sniper bot
Auto-buy on token create events that match your filters — creator history, naming patterns, metadata signals. Execute within the same slot window as the launch itself.
Launch scanner dashboard
Real-time feed of every new Pump.fun token with live metrics: unique buyers, volume, curve progress, and time-to-graduation. Surface the tokens gaining traction before they trend on social.
Rug detector
Cross-reference creator wallets against historical launch data. Flag tokens from wallets with patterns of quick dumps, recycled names, or bundled buys from connected addresses.
Graduation tracker
Alert when tokens approach the bonding curve threshold for Raydium migration. Graduation is the strongest signal that a token has real community demand and is about to gain DEX liquidity.
Volume alerts
Notify when a newly launched token hits configurable volume thresholds within its first minutes. Early volume spikes combined with diverse buyer wallets are a high-signal indicator.
Copy trading
Follow wallets that consistently buy winning launches early. When they enter a new token, your bot mirrors the trade automatically with configurable position sizing and exit rules.
Filtering out noise
With over 500 tokens launching on Pump.fun every day, the raw firehose is overwhelming. More than 90% of launches are low-effort rugs, test tokens, or projects that never attract a single organic buyer. If your scanner processes every token equally, you waste compute, bandwidth, and attention on noise that will never produce a tradeable opportunity.
Subglow's server-side filtering solves this at the infrastructure layer. Instead of receiving every event and filtering client-side, you define criteria that run on Subglow's servers. Only events that pass your filters reach your application. This means less bandwidth, lower latency on the events that matter, and dramatically simpler bot logic.
Common filtering strategies include checking creator wallet history (has this wallet launched tokens before, and did they rug?), initial liquidity thresholds (skip tokens with negligible starting capital), naming pattern analysis (filter out obvious spam and test tokens), and early buyer diversity (ignore tokens where the first ten buys come from the same wallet cluster). Because Subglow delivers pre-parsed JSON, all of these checks operate on clean field values rather than raw binary data — no Borsh decoding, no custom instruction parsers.
Raw Pump.fun launch volume that your scanner would need to process without server-side filters
The share of daily launches that are rugs, tests, or dead-on-arrival tokens with zero organic demand
Every event arrives as structured JSON — filter on field values, not byte offsets
Frequently asked questions
How fast can I detect a new Pump.fun token launch?
Subglow delivers Token Create events in under 5 milliseconds from slot confirmation. You receive the mint address, token name, symbol, creator wallet, and bonding curve address as structured JSON — the earliest possible signal that a new token exists on-chain.
What data do I get for each new token launch?
Each Token Create event includes the mint address, token name, symbol, creator wallet, bonding curve address, and timestamp. Subsequent lifecycle events add buy/sell amounts, curve progress percentages, migration details, Raydium pool addresses, and Jupiter swap data. Everything is pre-parsed JSON.
Can I filter token launches by specific criteria?
Yes. Subglow supports server-side filtering so only events matching your criteria reach your application. Filter by creator wallet, token naming patterns, liquidity thresholds, and protocol type. This reduces the 500+ daily Pump.fun launches to only the ones your strategy cares about.
Do I need to parse Borsh or binary data?
No. Subglow handles all on-chain data parsing on the server side. Every event arrives as clean JSON with human-readable field names like mint, symbol, solAmount, and curveProgress. No Borsh deserialization, no instruction discriminators, no raw byte arrays.
How do I track when a Pump.fun token migrates to Raydium?
Subglow streams Migration events when a token's bonding curve fills and liquidity moves to a Raydium pool. The event includes the mint, new Raydium pool address, and initial liquidity amount. You can build graduation alerts, auto-buy triggers, or analytics dashboards around this single event.
What programming languages are supported?
Subglow uses standard gRPC with JSON-encoded events. Client libraries exist for TypeScript, Python, Rust, Go, Java, C#, and virtually every other language with gRPC support. If your language can open a gRPC stream and parse JSON, it works with Subglow.
First to see it. First to trade it.
Every Pump.fun launch, every Raydium migration, every Jupiter swap — pre-parsed and streaming in under 5ms. Start monitoring token launches today.