SnipeMint

Updated 11 min read

Solana sniper bot: how to snipe new tokens on Solana

A Solana sniper bot watches the chain for new token mints and new liquidity pools, screens each one against the contract, and places a buy in the same slot the launch appears.

The exit is armed at the same moment as the entry, so take profit, stop loss and a maximum hold are already running before you look at a chart.

  • A wallet it can sign with
  • Rules it follows without asking you
  • A connection that sees a mint in the block it was created

What a Solana sniper bot is

A sniper bot is a program that trades new launches for you. It sits on a Solana RPC connection, parses program logs as blocks land, and reacts to a mint or a pool that did not exist a second earlier. There's no chart to read and no Telegram call to wait for. The account data is the signal.

Four stages run in order, and any one of them can end the trade before money moves.

  1. 1DetectLogs from the launchpad and AMM programs are parsed as they arrive. A new Pump.fun curve or a new Raydium pool shows up as an instruction, and that instruction carries the mint address.
  2. 2ScreenThe mint account, the pool account and the deployer's past launches get read before any SOL is committed. Anything that fails a rule is dropped, and the reason is kept.
  3. 3ExecuteThe buy is built with your size, your slippage and your compute unit price, then sent as a public transaction or inside a private bundle.
  4. 4ExitTake profit, stop loss, trailing stop and a maximum hold start the second the buy confirms. Nothing waits for you to open the panel.

People underrate that last stage. A bot that buys well and exits badly is just a faster way to lose the same money.

How it differs from the other bots people call snipers

  • A volume bot buys and sells a token you already own so the chart looks busy. That's a marketing tool, not a trading one.
  • A copy trader mirrors a wallet you follow. It's only as good as that wallet, and it's always at least one block behind it.
  • A sniper bot has no wallet to follow and no token to promote. It reacts to launches nobody has traded yet, and since there is no trading history to judge a brand new mint by, the screening step carries almost all of the weight.

How to set up a Solana sniper bot in five steps

The steps below are the ones in our panel. The shape is the same wherever you run one: prove who you are, fund something the bot can spend, write the rules, then let go of it.

  1. 1Connect a walletPhantom or Solflare is enough. Connecting reads your public key and nothing else. It costs no SOL, approves no transaction, and there is no email or password anywhere in the flow.
  2. 2Activate a planThe panel reserves an address for your order and shows a round amount in SOL. Pay it from the wallet you connected or from any other wallet you like, because the match is made on the amount arriving at a reserved address rather than on who sent it. The plan switches on by itself once the transfer confirms, usually inside a minute.
  3. 3Link a trading walletCreate a fresh Solana wallet, move in what you are willing to trade, and paste its private key. A browser extension cannot sign while your laptop is asleep, so the engine needs a key of its own. Ours is sealed with AES-256-GCM before it touches disk and is never sent back to the browser.
  4. 4Write the rulesStart on a preset, then change whatever you disagree with. Entry size, slippage, which venues are armed, which checks have to pass, where profit is taken and where the stop sits. Every field has a plain sentence next to it explaining what it does.
  5. 5Arm it and close the tabThe engine runs on a server, not in your browser. Shut the laptop and it keeps reading blocks. Everything it buys, sells or skips is written into the live console with a timestamp.

What speed actually means on Solana

Solana targets a 400 millisecond slot. That is roughly two and a half blocks a second, each with its own leader. Sniping is a question of which slot your transaction lands in, and very little else.

Three things decide that.

  • How you hear about the mint. A websocket subscription on a dedicated node sees the log in the slot it happened. Polling a public API once a second means you're already up to 1,000 milliseconds behind before you've built anything.
  • What you pay for block space. The base fee is fixed at 5,000 lamports per signature. The part you bid on is the compute unit price, and during a contested launch that bid is the difference between inclusion and a dropped transaction.
  • Whether you go public or private. A public transaction sits in a queue where other people can build around it. A Jito bundle lands atomically, pays a tip instead of competing on fee, and is invisible until it is already on chain.

Is first the same as right? No. A bot that buys everything in slot zero will lose money faster than one that waits two seconds and reads the mint account first. Paying for speed only makes sense once the screening in front of it is good.

The twelve checks that run before a lamport moves

Screening is where most of the value sits, and it happens to be the part that comparison posts skip, because listing features takes a paragraph while explaining what each check actually reads out of an account takes a table. Each check below reads something specific out of the chain. None of them is an opinion about the token.

CheckWhat it reads on chainWhy it matters
Mint authority revokedThe mintAuthority field on the mint accountWhile it is set, the creator can print more supply and dilute every holder at will
Freeze authority revokedThe freezeAuthority field on the mint accountA live freeze authority can lock your token account so the position cannot be sold at all
LP burned or lockedLP token supply and the account holding itIf the deployer still holds pool tokens, the liquidity can be withdrawn in one transaction
Sell simulationA dry sell routed through the venueIf the simulated sell reverts, the token is a honeypot and the buy is never sent
Creator holding capThe deployer's share of total supplyA creator sitting on 30% of supply is a seller waiting for your buy to arrive
Bundle detectionBuys landing in the same slot as the mintA launch opened by a bundled buy already has its supply placed before anyone else sees it
Top ten concentrationThe largest holder accounts on the mintTen wallets holding most of the float can end a chart with a single transaction
Deployer historyEarlier mints signed by the same walletA wallet that pulled three pools last week is likely to pull the fourth
Metadata and socialsThe metadata URI, image and linksA mint whose metadata does not resolve rarely has anyone standing behind it
Token-2022 extensionsTransfer fee, transfer hook and permanent delegate flagsToken-2022 lets a creator tax every transfer or move your balance without asking
Sniper cluster mappingThe funding graph behind the earliest buyersTwenty wallets funded from one source are one seller wearing twenty hats
LP lock depthThe lock program, the amount locked and the unlock dateA lock that expires in an hour isn't a lock, it's a countdown

Six of these run on the entry plan. Four more come with the middle one and the last two with the top. A launch that fails any active check is skipped, and the console records which check refused it, so the log is a record of what the bot chose not to buy rather than a list of fills.

Where a Solana sniper bot can trade

A launch doesn't stay where it starts. On Pump.fun a token opens on a bonding curve, trades there while the curve fills, then graduates into a real pool. Plenty of the move happens in the minutes around that handover, so a bot that only watches the launchpad sees the entry and misses the exit, while a bot that only watches the AMM turns up after the part that mattered.

We cover 42 venues today, split four ways.

GroupCountExamplesWhat happens there
Launchpads10Pump.fun, LetsBonk, Bags, Believe, Boop.fun, LaunchLab, Jupiter Studio, Heaven, Daos.fun, VectorTokens are created and trade on a bonding curve before any pool exists
AMMs26Raydium, Meteora, Orca, Lifinity, Invariant, FluxBeam, Saros, Crema, CropperGraduated tokens and everything else trade against pooled liquidity
Order books3OpenBook, Phoenix, DriftResting bids and asks, which behave differently from a curve under pressure
Routers3Jupiter, DFlow, TitanRoute a single fill across several pools at once for a better price

How many of those you can arm depends on the plan: ten on Scout, twenty-four on Striker, all forty-two on Overwatch. Turning on every venue isn't automatically better. A bot armed on 42 venues with loose rules simply finds more ways to buy something it should have skipped.

The settings that decide whether you make money

Defaults get you running. They do not get you profitable. These are the eight numbers worth understanding before you arm anything, with the range most accounts settle into after a week.

SettingWhat it controlsA sane starting point
Entry sizeSOL spent on a single launch0.1 to 0.25 SOL while you learn what your rules reject
Buy slippageHow far past the quote you will still fill10% into a graduated pool, 15% to 25% into a fresh curve
Priority feeYour bid for block space, paid to the validator0.0005 to 0.002 SOL, higher only when launches are contested
Take profitWhere a green position closes40% to 100%, lower than most people guess
Stop lossWhere a red position closes25% to 35%
Trailing stopHow much of a peak a runner may give back15% to 25%, and 0 turns it off
Maximum holdA time cap on any position20 to 45 minutes
Daily loss limitWhere the engine stops itself for the dayWhatever number would make you close the laptop

The one people get wrong is entry size. Sniping is many small losses paying for a few large wins, and the quickest way to break that arithmetic is a position big enough that you start managing it by hand. If a single fill can ruin your week, the size is wrong, not the bot.

What a Solana sniper bot costs

There are two bills. Ours, and the chain's.

PlanPriceVenuesOpen positionsRouting
Scout1 SOL a month103Shared priority lane
Striker3 SOL a month2410Private Jito bundles
Overwatch5 SOL a month4230Staked sender connections

Nothing is taken out of a trade. No percentage of profit, no fee per fill, no cut on the way out. The month is the whole price.

The chain charges you whichever bot you run, and these are the numbers worth knowing before you size a wallet:

  • 5,000 lamports of base fee per signature, which is 0.000005 SOL.
  • The priority fee you set, which goes to the validator and not to us.
  • 0.00203928 SOL of rent for each new token account the wallet opens. You get it back when the account is closed.
  • The venue's own trading fee, taken by the launchpad or the pool you fill against.
  • A Jito tip, if you route privately. You choose that number and can set it to zero.

A wallet with 2 SOL in it can trade all day at 0.1 SOL a fill. Fees are not what stops most people. Position sizing is.

Can you actually make money with one?

Sometimes. Not reliably, and not by leaving the defaults alone.

Most new mints on Solana go to zero. That's not a flaw in the software. It's the shape of the market the software works in. What automation buys you is narrow, and worth naming honestly:

  • Screening removes contract-level traps before they cost anything. A honeypot you never bought is a free win, and those are the cheapest wins available.
  • Exits fire without hesitation. The distance between an 80% gain on screen and a 30% loss realised is usually a person deciding to wait one more minute.
  • Size stays constant. Software doesn't double up because the last fill hurt.

What it can't do is pick which meme coin the internet decides to love this week. Anyone selling you that is selling a story. You can lose the entire balance in the trading wallet, so that wallet should hold only what you were prepared to lose before you started.

Sniper bot, Telegram bot, or your own script?

Four ways people actually snipe on Solana, and what each one costs you beyond money.

ApproachWhere the key livesRuns while you sleepScreeningCut of your trades
Telegram trading botOn their server, with your SOL in a custodial balanceYesUsually mint and freeze authority onlyCommonly 0.5% to 1% of every trade
Browser extensionIn the extension, on your machineNo, it stops when the tab closesVaries, often noneUsually a percentage
Your own scriptWherever you put itOnly if you host it somewhereWhatever you build and maintainNone, but you pay for nodes
Hosted engineSealed on the server, funds stay in your walletYesUp to twelve checksNone, flat monthly price

The trade-off in the last row deserves saying out loud rather than burying. A hosted engine holds a key it can sign with, so you are trusting how that key is stored. Ours is encrypted with AES-256-GCM before it is written and never returned to any browser, and you can replace it whenever you want. It's still a key on someone else's machine, so the wallet you link should be funded for trading and nothing else.

Five mistakes that cost people money

  1. 1Sizing at a third of the walletOne bad launch and the rules stop mattering, because now you are trading a position instead of running a system.
  2. 2Slippage at 50%You will fill on everything, including the launches your slippage setting was quietly protecting you from.
  3. 3No maximum holdLiquidity pulls happen in the first minutes far more often than in the first hour. A position with no time cap is a position waiting for one.
  4. 4One set of rules for curves and poolsA fresh bonding curve moves in a way a Raydium pool holding 400 SOL simply doesn't. Slippage and take profit should not be identical across both.
  5. 5Linking the key of your main walletFund a fresh wallet for the engine. Nothing about convenience is worth putting the rest of your holdings behind one paste.

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.

No. A hosted sniper bot is a settings panel: you pick venues, set entry size and slippage, choose where profit is taken, and arm it. Writing your own is a different job that means running a node connection, tracking launchpad program changes and handling key storage yourself.

Key takeaways

  • A Solana sniper bot detects new mints, screens the contract, buys, and arms the exit in one uninterrupted sequence.
  • Screening matters more than raw speed. Buying first into a honeypot is still a loss.
  • Solana slots target 400 milliseconds, so inclusion is decided by your connection and your compute unit bid, not by your reflexes.
  • Twelve contract checks cover the traps that are visible on chain: mint and freeze authority, LP burn, sell simulation, holder concentration, deployer history and Token-2022 extensions.
  • Entry size is the setting that decides whether the maths works. Everything else is tuning.
  • Plans run 1, 3 and 5 SOL a month with no cut of any trade, and the only other costs are the chain's own fees.