SnipeMint

Updated 8 min read

LaunchLab sniper bot: sniping Raydium's configurable curves

A LaunchLab sniper bot reads the curve configuration attached to each individual launch rather than assuming a fixed shape, because on Raydium's LaunchLab the threshold, the fee split and what happens to the LP at graduation are all chosen by whoever created the launch.

That makes LaunchLab the hardest of the major Solana launchpads to snipe correctly and the easiest to snipe badly. Two launches on the same program, in the same minute, can price your buy differently and end in a completely different liquidity arrangement.

  • A decoder that reads curve config per launch, not per venue
  • Awareness that mint authority lives until graduation
  • Fill maths for a quadratic curve, not a constant product one

Why there is no single LaunchLab curve

Most launchpads ship one curve. One supply, one formula, one threshold, the same on every launch, which is exactly why a bot can be written once and trusted afterwards. LaunchLab is built the other way round. It is infrastructure, and the parameters that decide how your buy is priced are configuration carried by each launch.

Raydium's own documentation describes the threshold as chosen so the curve's implied price at graduation matches the price the pool will open at, and gives a formula rather than a number. There is no published default because there is not supposed to be one.

What is configurable, and what it costs you to ignore

  • The graduation threshold, which decides how long the curve phase lasts and how close to the end you are arriving.
  • The curve formula and its constant, which decides how steeply your own buy moves the price against you.
  • The quote asset, so a curve may be denominated in SOL or in USDC and the same raised amount means two different things.
  • The LP disposition at graduation, which decides whether liquidity ends up locked, burned or held by a platform wallet.
  • The creator fee, which is optional and set at initialization rather than fixed by the venue.

How a quadratic curve prices your buy

The common LaunchLab implementation is quadratic: price rises with the square of the fraction of supply already sold. Written plainly, price is proportional to the ratio of tokens sold to maximum supply, squared. A constant product curve of the Pump.fun kind behaves differently, and the difference is not academic.

On a quadratic curve the early portion is unusually flat and the late portion is unusually steep. Being first costs you less than you might expect. Being late costs you more than you might expect.

Where you are on the curveWhat your buy doesWhat that means for sizing
Very earlyMoves price littleYou can take size without wrecking your own fill
MiddleMoves price noticeablySlippage starts to matter more than speed
Near thresholdMoves price sharplySmall buys, or wait for the pool
After graduationOrdinary pool behaviourCurve settings are now wrong

This shape is the argument for reading how far along a launch already is before deciding anything. On a venue with a flat early section, arriving at forty percent of the way to graduation is a genuinely worse trade than arriving at five percent, and the gap is much wider than the same comparison on a constant product curve.

The mint authority that survives the curve

This is the detail that catches people who learned to snipe on Pump.fun. There, mint and freeze authority are revoked at launch, which is why those checks are useless as filters. On LaunchLab, the documented migration sequence revokes the base mint's authority permanently at graduation, not at creation.

So during the curve phase the answer to the question every screener asks is not automatically no. That inverts the usual advice: on this venue, the contract level check is worth running, because it can actually return different answers on different launches.

It does not follow that a live mint authority means a launch is a scam. It means the usual reassurance is not available yet, and the weight of your decision shifts back onto who deployed the launch and what they have deployed before.

Locked, burned or kept: what happens to LP at graduation

When a LaunchLab curve completes, the program snapshots the curve reserves, creates a CPMM pool seeded from them, revokes the mint authority and marks the launch graduated. What happens to the resulting LP position is configured rather than fixed.

Raydium's platform configuration carries three scales that sum to one million: a platform share, a creator share and a burn share. The first two are locked through an LP lock that issues a fee key, and the burn share is destroyed outright with no fee key attached. A September 2026 upgrade made CPMM the only graduation target and locks the creator LP at migration, applying to future migrations rather than retroactively.

LP dispositionWhat it meansRisk that remains
BurnedPosition destroyed, nobody can withdrawConcentrated supply, not liquidity
LockedHeld under a lock with a fee keyFees accrue to the key holder
Platform heldSits in a platform walletDepends entirely on that platform

The practical instruction is the same as the one about thresholds. Do not read an article that says LaunchLab burns LP and treat it as a property of the venue. Read what this launch configured, because that is what will actually happen.

The three way fee split during the curve

Curve phase fees on LaunchLab divide three ways. A share goes back into the curve itself, raising its constant and tightening prices for everyone who buys after you. A share goes to the protocol. A third, optional share goes to the creator as an ongoing revenue stream, configured when the launch is initialized.

The first of those is unusual enough to be worth pausing on. Fees that feed the curve mean that trading activity itself changes the curve's shape, so the price you are quoted late in a busy launch reflects not only the tokens sold but the volume that moved them.

After graduation the pool runs on standard CPMM fee configuration, commonly the quarter percent tier. That is a different cost structure from the curve phase, and another reason to treat the two halves of the trade as separate instruments.

LetsBonk and the other front ends

LaunchLab is not only used by Raydium. Other launchpads build on it, register their own platform configuration and present their own brand, which is why the same program emits launches belonging to several venues at once. LetsBonk is the largest example.

For a sniper this cuts both ways. One decoder gives you coverage of several venues at once, which is efficient. It also means a listener that does not filter is buying launches from front ends you never intended to trade, with flow profiles you have not studied.

QuestionWhere the answer lives
Is this LaunchLab at all?Program ID
Which front end created it?Platform config account
How far to graduation?Curve config plus current reserves
SOL or USDC denominated?Quote mint
What happens to LP at the end?Platform config scales

What LaunchLab snipers get wrong

  1. 1Hardcoding a thresholdThere is no venue wide default. A fixed number means misreading how far along every launch that does not happen to match it is.
  2. 2Carrying Pump.fun authority assumptions overMint authority is revoked at graduation here, not at creation. The check you correctly ignore elsewhere is a real signal during the curve.
  3. 3Using constant product fill mathsA quadratic curve is flatter early and steeper late. Sizing built for the wrong shape misses in both directions.
  4. 4Assuming LP is always burnedBurn is one of three configured outcomes. Locked LP with a fee key is a different arrangement with different incentives.
  5. 5Skipping the platform filterSeveral front ends share this program. Without the filter you are trading venues you did not choose.

Questions people ask

These come up in the ticket queue often enough to answer once, properly. If yours is not here, send it over and it probably ends up on this page.

It is Raydium's bonding curve launch infrastructure, where tokens are sold against a configurable curve priced in SOL or USDC and migrate into a CPMM pool once the curve completes.

Key takeaways

  • LaunchLab is infrastructure, so threshold, curve shape, quote asset and LP disposition are set per launch rather than per venue.
  • The curve is commonly quadratic, which is flat early and steep near the threshold, so arriving late is more expensive than on a constant product curve.
  • Mint authority is revoked at graduation, not at creation, which makes the authority check a genuine signal during the curve phase.
  • LP at graduation splits across platform, creator and burn shares, so burned liquidity is one configured outcome rather than a guarantee.
  • Several front ends including LetsBonk share this program, so a platform config filter is what separates one venue from another.