Sniping New

A snipe strategy watches new token launches and submits a buy as soon as one matches your rules. It is not tied to a token you already know: the strategy keeps evaluating new launches until you pause it, spend its budget, or reach its expiry.

Unlike Copy Trading, Sniping does not follow one source wallet. Its signal comes from the launch, token, pool, and deployer criteria you choose.

Define one snipe

Setting	Meaning
Name	A label that distinguishes this strategy from your others
Entry amount	The amount spent each time a launch matches
Total budget	The maximum the strategy can spend across all matches
Expired at	When matching stops automatically, Not set leaves it running until paused or exhausted

Total budget / Entry amount gives the maximum number of entries when every snipe uses the full entry amount. For example, 1 SOL with a 0.1 SOL entry amount allows up to 10 snipes.

Choose the execution wallet or wallets, then set slippage and gas fee for every buy submitted by this strategy. Higher fee priority can improve submission speed, while slippage controls how far the execution price may move; neither guarantees an early fill.

Match a launch

All enabled filters must pass. Filters left Off do not restrict matching.

Token and pool criteria

Filter	What it checks
Market Cap	Whether market cap is within your bounds
Liquidity	Whether the pool meets your minimum liquidity
Top 10 Holders	Whether holder concentration is within your bounds
Token Ratio	Whether the token ratio is within your bounds
Token Age	Whether the token is inside the selected age window
LP Burned	Whether liquidity is burned
Platforms	Whether the launch uses an allowed platform
Allowed assets	Whether the token is on your allowlist
Blocked assets	Whether the token is absent from your blocklist

Deployer and naming criteria

Filter	What it checks
Allowed deployers	The deployer is one of the addresses you listed
Blocked deployers	The deployer is absent from your blocklist
Exact name or ticker	The token name or ticker matches exactly
Name or ticker contains	The name or ticker contains one of your keywords
Migration stage	The launch has reached the selected migration stage

Several keywords can be entered under Name or ticker contains. A launch matches this field when any one of them appears, but it must still pass every other enabled filter.

Start and control the strategy

1. Open Sniping from the Home Page
2. Create and name the strategy
3. Set the entry amount, total budget, and optional expiry
4. Select the execution wallets, slippage, and gas fee
5. Configure the launch, token, pool, and developer filters
6. Review the rules and press Start sniping

Before it starts, the strategy remains an editable draft. Once active, its page shows the current status and Snipe history. Use Pause to stop matching without deleting the configuration, edit the rules while paused, and use See all to review previous entries.

The budget is a limit, not a reserved balance

Keep enough trade and execution-fee tokens in every selected wallet while the strategy is active. An empty wallet can miss a launch without stopping the strategy itself.

Skipped or failed?

A launch is skipped when it fails an enabled filter, the strategy is paused or expired, or the remaining budget is below the entry amount. No transaction is attempted.

A failed snipe matched the strategy, but the submitted buy could not complete. New pools move quickly and compete for execution, so route availability, liquidity, balance, slippage, and fee priority all matter at the moment of submission.

Control launch risk

• Start with a small entry amount and a firm total budget
• Add an expiry when the strategy targets a specific launch window or event
• Use liquidity, LP-burn, and holder-concentration criteria to reject unsuitable pools
• Keep naming keywords narrow; broad terms can match unrelated launches
• Pause before changing filters if the strategy must not fire mid-edit
• Check a failed transaction on-chain before submitting a replacement manually