How to Detect New Solana Token Launches Instantly (2026)

Every day, hundreds of new tokens launch on Solana — mostly through Pump.fun's bonding curve mechanism. For traders, the question isn't whether to monitor launches. It's how fast you can detect them.
Method 1: RPC Polling (Slowest)
The simplest approach: poll getSignaturesForAddress on the Pump.fun program ID every second.
setInterval(async () => {
const sigs = await connection.getSignaturesForAddress(PUMP_FUN_PROGRAM);
for (const sig of sigs) {
const tx = await connection.getTransaction(sig.signature);
// Parse instruction data manually...
}
}, 1000);
Problems: 1-2 second detection lag, rate limit issues at scale, requires full Borsh deserialization of every transaction, misses events between poll intervals.
Method 2: WebSocket Subscription (Better)
Subscribe to the Pump.fun program via logsSubscribe:
connection.onLogs(PUMP_FUN_PROGRAM, (logs) => {
// Parse log messages to identify create events
if (logs.logs.some(l => l.includes("create"))) {
// Still need to fetch full transaction for details
}
});
Problems: 50-200ms latency, connection drops require reconnection logic, log messages don't contain structured data — you still need a second RPC call to get details.
Method 3: Filtered gRPC (Fastest)
Subscribe to pre-parsed Pump.fun events via Subglow:
const client = new Subglow({
url: "grpc.subglow.io:443",
apiKey: process.env.SUBGLOW_KEY,
filter: ["pump_fun"],
});
client.subscribe((event) => {
if (event.parsed.type === "create") {
console.log("NEW TOKEN:", event.parsed.name, event.parsed.symbol);
console.log(" Creator:", event.parsed.creator);
console.log(" Token:", event.parsed.token);
// Trade immediately — all data is here
}
});
Advantages: Sub-5ms delivery, structured JSON with all fields pre-extracted, persistent connection with auto-recovery, no second RPC call needed.
Latency Comparison
| Method | Detection Latency | Data Quality | Reliability |
|---|---|---|---|
| RPC Polling | 1,000-2,000ms | Raw (needs parsing) | Moderate (rate limits) |
| WebSocket | 50-200ms | Logs only (needs 2nd call) | Good (reconnect needed) |
| Filtered gRPC | <5ms | Full structured JSON | Excellent (auto-recovery) |
What You Get in Each Create Event
With Subglow's Pump.fun filter, every create event includes:
token— the mint address (what you need to buy)nameandsymbol— for filtering or displaycreator— the wallet that launched (useful for watchlists)bonding_curve— the curve addressslotandtimestamp— for timing your entry
No Borsh. No discriminator mapping. No second RPC call. Just data, ready to act on.
Filtering the Noise
Not every launch is worth sniping. Smart filters after detection:
- Creator history: Has this wallet launched rug pulls before?
- Name/symbol patterns: Skip obvious scams and duplicate names
- Early buyer velocity: Track the first 10 buys — fast accumulation signals demand
- Social signals: Cross-reference with Twitter/Telegram mentions
Start Detecting Today
The difference between detecting a launch in 5ms vs 2 seconds is the difference between buying at the bottom of the curve and buying after the first wave. Set up your filtered gRPC connection and start catching launches before your competition even knows they exist.
Ready to try it?
Get your API key and start receiving filtered data in under 5 minutes. Free tier available.
Get started →