How to spot a bundled launch before it dumps

A bundled launch is one where the deployer — or allies working with the deployer — used Jito's block engine to buy large amounts of the token in the same Solana block as the token creation. Understanding bundles is one of the fastest ways to improve your odds on pump.fun.

Jito is a Solana validator client that offers a block engine: validators using Jito allow searchers to submit "bundles" — atomic groups of transactions that execute together in the same block slot, in a specific order, or not at all.

On pump.fun, this means a coordinated group can submit a bundle that includes both the token creation transaction and a series of buy transactions — all landing in the same block. The result: by the time any public Solana explorer shows the token existing, the bundlers already own a significant portion of the supply at the lowest possible price (the starting bonding curve price).

No organic buyer can react this fast. The public never gets the bottom of the curve.

The bearish case for bundled launches comes down to supply concentration and incentives:

• Team controls early supply. The bundlers — often the deployer and allied wallets — hold a disproportionate share of the token at cost basis far below any organic buyer. Their average price might be 5–10× lower than the first public buyer's entry.
• Exit pressure is front-loaded. For the bundlers to profit, they need to sell into organic demand. Every buyer who enters after launch is providing liquidity for the bundlers to exit.
• Organic buyer base is smaller. Supply held by bundlers is supply unavailable to organic buyers, which means the token's visible market cap understates the supply overhang.

Bundled ≠ instant rug. Some bundled tokens do graduate, especially if the project has genuine external demand. But the incentive structure works against organic holders.

Soliscope checks the Solana slot of each early buy transaction and compares it to the token creation slot. When multiple wallets buy in the same slot, they were bundled. The signals to check:

• isBundled flag — fires when Soliscope detects same-slot buying at launch. Red chip in the token detail view.
• Sniper count — the number of wallets that bought in the launch slot. A sniper count of 1–2 is low risk (could be a single fast bot). A count of 5+ means coordinated accumulation.
• Deployer in early holders — if the deployer wallet itself appears in the top early holders, they kept supply for themselves beyond the creation transaction. Combined with bundling, this is a strong exit signal.

A practical threshold: sniper count ≥ 5 with isBundled = true is a skip for most risk tolerances. The coordinated accumulation is too large to expect organic demand to absorb the eventual exit pressure.

Sniper count 1–3 with isBundled is more nuanced — a small bundle might just be a fast individual trader, not the deployer team. In this case, weight the other signals more heavily: is the deployer clean? Is concentration low? Is the curve gaining?

The clearest green signal is a token with isBundled = false and sniper count 0 — the market had equal access from the start. When combined with a clean deployer and rising curve, this is the setup you're looking for.

To understand how bundle detection fits into the broader gem-finding framework, read how to find gem tokens on Solana.

See bundle detection live on new launches → Open the Soliscope feed