Sniping
FortiSwap Pro's sniping stack lets you buy new tokens the moment they list — either the second liquidity is added to a new AMM pool, or while a launchpad token is on its bonding curve and when it graduates. This guide covers both flavors and the rules that drive them.
Sniping is a genuinely advanced feature. It is highly competitive, has a high failure rate, and can lose money quickly. Start with tiny sizes, and use the launchpad sniper's observe-only mode before scaling up.
The sniper paths
FortiSwap Pro exposes three user-facing sniper modes:
- Auto Buy Rules — rule-based auto-sniper for freshly-created XDEX pools. Fires when a new pool is discovered and it matches all your rule filters.
- Snipe a Token — one-shot sniper for a specific token address you already know about. Arm it, and it buys when the token's liquidity appears.
- Launchpad Sniper — rules for launchpad tokens, before graduation (on the bonding curve), after graduation, or both. In Telegram this is the primary sniper.
Getting started
From the dashboard
Open Automations → Snipers. The Sniper tab has Arm Sniper (one token) and Auto Buy Rules; the Launchpad Sniper tab has your launchpad rules.
From Telegram
/snipe <token_address> <amount> [slippage_bps]Buys a specific token. Send /snipe alone for the interactive flow, /snipe_launchpad for your launchpad sniper status, and /autosnipe to turn the auto-sniper on or off.
Rules for "Auto Buy Rules"
Each rule is a filter set. The sniper watches every new XDEX pool and only fires when all filters pass.
| Filter | Description |
|---|---|
| Amount (XNT) | XNT to spend per snipe |
| Min / Max Liquidity | Skip pools with less (or more) liquidity than this |
| Require Mint Authority Disabled | Only fire if no new tokens can be minted |
| Require Freeze Authority Disabled | Only fire if token accounts can't be frozen |
| Require LP Burned | Only fire if the liquidity is permanently locked |
| Slippage % / Priority Fee | Execution settings |
| Wallet | Which of your wallets to buy from |
| Auto-Sell | Optional: sell a percentage of the position at a profit target |
| Rule Label | Human name so you can find it later |
In Telegram, /addrule <name> <buyAmount> <minLiquidity> creates a rule and /autorules lists yours.
Rules for the Launchpad Sniper
| Setting | Description |
|---|---|
| Launch Stages | Pre-Grad, Post-Grad, or both |
| Max Trade (XNT) | XNT to spend per snipe |
| Daily Cap (XNT) | Total spend per day |
| Min Deployer Score | Skip tokens from deployers with a weak track record |
| Preference Filters | Require socials, cap the share of brand-new buyer wallets |
| Slippage / Priority Fee | Execution settings |
| Observe-only | Record what the rule would have bought, without buying |
Some anti-rug checks are always on for the launchpad sniper and can't be turned off: bundled-launch detection, a deployer reputation floor, mint and freeze authority checks, and a wallet reputation floor. Your own filters can only make a rule stricter. In Telegram, manage rules with /launchpad_rules, /launchpad_rule_create, /launchpad_rule_pause, /launchpad_rule_resume and /launchpad_rule_delete; /launchpad_history shows recent decisions.
Anti-Rug guards
Snipes are checked before the buy is submitted:
- Ownership scan — check whether the token has an active mint/freeze authority. Optionally skip.
- LP check — check whether the LP tokens have been burned.
- Liquidity bounds — skip pools outside your liquidity range.
- Your anti-rug guard — the guard you set with
/anti_rug_statusand/anti_rug_severity(strict, balanced or permissive) also applies.
If a check fails, the attempt is logged as blocked. You can see the executions on the Sniper page.
Speed
Sniping is a latency race. Your priority fee decides how your transaction ranks: set it per rule, or pick a mode with /priority_fee_mode (safe, fast or degenerate). Confirmations usually take a few seconds, depending on the network. /snipermode switches the sniper's aggression preset.
Auto-Exit configuration
You almost never want a snipe to sit unmanaged. Auto Buy Rules can sell a set percentage of the position when it reaches a profit target. For more exits, attach your own:
- TP-Ladder — Sell 25% at 2×, 25% at 5×, etc. Configurable rungs.
- Trailing Stop — Follow the peak down by X%.
- Hard Stop-Loss — Sell 100% if price drops to a trigger.
See Orders & Positions and Automations.
Managing rules & snipes
List active rules
/autorules
/launchpad_rulesList queued snipes
/pendingsnipesSee your results
/sniperstatsRecent snipes and win rate for your account.
Pause or delete a rule
On the dashboard, use Pause, Edit or Delete on the rule. For launchpad rules in Telegram:
/launchpad_rule_pause <network>
/launchpad_rule_delete <network>Paused rules stop firing but keep their state. Deleted rules can't be recovered.
Execution statuses
| Status | Meaning |
|---|---|
| pending | Rule matched, buy in progress |
| blocked | A check failed |
| success | Buy confirmed, position open |
| failed | The buy did not land |
An honest note
Sniping is for advanced users. The anti-rug checks are strong, but we're not going to tell you it's risk-free. If you're new to sniping, run a launchpad rule in observe-only mode for a week, or keep Amount to a fraction of an XNT, before increasing size.
Common mistakes
- Filters too loose — sniper fires on every new pool including scams. Fix: raise the minimum liquidity, require mint and freeze authority disabled.
- Filters too tight — 0 fires in a week. Fix: relax the liquidity floor, or drop the LP-burned requirement.
- No auto-exit — you snipe well and then forget to sell. Fix: always attach a TP-Ladder and a trailing stop.
- Priority fee too low — you consistently get outbid. Fix: raise the priority fee for high-competition launches.
- Too much size per rule — one bad token survives the guards and eats a full snipe. Fix: keep per-snipe size small and use a daily cap.
Supported venues
- XDEX — new XNT-paired pools
- Launchpad — pre-graduation and post-graduation launches