HostHostDeFi › Features › Sniper Bot
A Solana sniper bot that plans the exit before the entry
Filter-driven snipes on launches and migrations — the engine buys in seconds, then arms take-profit, break-even and timeout exits on every fill.
Most snipers answer "how fast can I buy". The question that actually decides the trade is "how does this position close" — and a snipe without an exit plan is just a faster way to hold a bag. HostDeFi's launch sniper treats the exit as part of the order: the moment a snipe fills, its take-profit, break-even and timeout exits arm themselves into the order book.
Filters are the edge, not the speed
Every sniper on Solana is fast — speed stopped being a differentiator a long time ago. What decides whether a snipe is worth taking is which launches you let it touch. A setup carries the filters that matter on new pairs: liquidity floor and ceiling, market-cap band, maximum token age, minimum buy count, a keyword the name must contain, blocked words, deployer allow- and blocklists, and required socials. Every band you set fails closed — a liquidity cap that can't read the launch's liquidity doesn't get the benefit of the doubt, so an unreadable figure never clears a gate you armed.
| Filter | What it screens out |
|---|---|
| Liquidity band | Dust pools you can't exit and mega-launches with no upside left |
| Market-cap band | Entries above your conviction and below viability |
| Max age + min buys | Dead launches and zero-interest mints |
| Keyword / blocked words | Narrative targeting, minus the clones and test mints |
| Deployer allow / block | Only wallets you've verified — or everyone except the serial ruggers |
| Required socials | Launches that never published a Twitter, a site, or a Telegram |
Two hunts: the launch and the migration
A setup picks its moment. Launch mode hunts brand-new curve creations — the mint exists for seconds before the engine sees it, because the create landing on the launch stream is what pokes the sniper. There is no poll and no feed lag between "the token exists" and "the filters ran". Migrate mode hunts the other event — a watched token graduating off the curve onto the AMM, the exact block where a launch either becomes a market or dies. Same filters, same armed exits, different prey.
Every fill arrives with its exits armed
The fill is the start, not the trade. Each snipe writes its exits into the same engine-watched order book as your resting orders: a first take-profit that sells a slice — you pick 10–90% of the position — into the initial pump, a second target that closes the rest higher, a stop-loss below, and a timed exit so a stalled launch can't hold your SOL hostage. When that first take fires with a stop still standing, the stop moves itself to break-even and the runner rides risk-free. They fire server-side, which means the whole arc — entry, profit-take, stop — completes while your phone is in a drawer.
Honest limits: up to five setups, a per-day snipe cap clamped to twenty across the account, and a lifetime fill cap that pauses the setup when it hits. Fills follow the liquidity the launch actually has — a filter set can't make a bundled launch safe, it can only keep you out of most of them. Sniper bots and bundled launches covers what coordinated entries do to fresh books.
Sniping launches you haven't screened?
Filters catch the obvious junk. The scanner reads the contract — run the mint through it before it earns a setup.
Frequently asked
How does the HostDeFi sniper bot work?
You configure a setup — SOL size plus filters on liquidity, market cap, token age, buy count, keywords and deployer wallets — and the engine buys launches and migrations that match, in seconds. Every fill auto-arms take-profit, break-even and timeout exits.
Does it snipe while I'm offline?
Yes — setups live on the 24/7 engine against your account wallet. The entry and all armed exits fire server-side whether or not any device is connected.
What limits does the sniper have?
Five setups, a per-day snipe cap clamped to twenty across the account, and a lifetime fill cap per setup that pauses it when hit. If the sniper engine is ever paused site-wide, setups stay saved and fire when it resumes.
What does a snipe cost?
The same flat 1% platform fee as every HostDeFi trade lane, applied to executed fills only — a setup that never triggers costs nothing.
Do the filters prevent rugs?
No — they screen shape, not intent. A bundled launch or a live freeze authority can still pass liquidity and age filters; that's what the token scanner and rug checks are for.
What's the difference between launch and migrate mode?
Launch mode hunts brand-new curve creations — the buy fires seconds after the mint exists. Migrate mode hunts a watched token's graduation onto the AMM — the moment a launch becomes a real market. Same filters, same armed exits, different prey.