Sniping Configuration

What is sniping?

When a dev creates a new token or a new pool just goes live, the system quickly evaluates it against the rules you set in advance and buys when the conditions are met. You can combine speed with token filters, position sizing, slippage limits, and automatic sell strategies to keep execution as close as possible to your intended plan.

Sniping settings explained

Basic information

• Name: Give the sniping task an easy-to-remember name.
• Chain: The target chain. Currently, Solana is supported.
• Wallet: The wallet used to execute sniping trades, selected from your wallet list.
• Notes: Record any extra details or ideas for this sniping task.

Buy settings

• Enable buy: Turn this on before the system will automatically buy when conditions are met.
• Buy amount: The amount the wallet uses on each snipe trigger.
• DEX selection: Choose which new-token sources to monitor. At least one DEX is required. Pumpfun is supported.
• Token name or symbol filter: Only snipe tokens whose name or symbol contains these keywords.
• Exact match: When enabled, the token name or symbol must match the keyword exactly.
• Creator filter: Only snipe tokens issued by the specified creator address.
• Ignore freezable tokens: If the token's freeze authority has not been revoked, do not buy.
• Ignore mintable tokens: If the token's mint authority has not been revoked, do not buy.
• Ignore delegated tokens: If the token has been fully delegated to another address, do not buy.
• Min market cap: Only snipe tokens with a market cap above this value.
• Max market cap: Only snipe tokens with a market cap below this value.
• Min token age: Only snipe tokens that have existed longer than this duration.
• Max token age: Only snipe tokens that have existed for less than this duration.
• Min pool size: Only snipe pools with liquidity above this value.
• Max pool size: Only snipe pools with liquidity below this value.
• Max slippage: Controls the maximum allowed deviation between the expected price and the actual fill price. Lower values keep execution closer to the expected cost; higher values improve fill probability.
• Fast mode and anti-MEV mode:
  • Fast mode: Broadcasts transactions through multiple high-stake nodes in parallel to improve on-chain speed.
  • Anti-MEV mode: Submits transactions only through anti-MEV services to avoid sandwich attacks.
• Priority fee: The fee paid to validator nodes. Higher fees increase the chance that the transaction is ranked earlier.
• Tip: The fee paid to the transaction relay and anti-MEV service. Higher tips rank your transaction earlier inside the service.

Sell settings

• Enable sell: Turn this on to automatically sell according to take-profit and stop-loss rules. Otherwise, the system will only buy and not sell.
• Take-profit settings: You can add up to 3 take-profit tiers. Each tier supports the following:
  • Price increase: The percentage increase that triggers the take-profit trade. For example, 50% means the take-profit is triggered when price rises by 50%.
  • Sell quantity: The percentage of the current position to sell when this take-profit tier triggers. For example, 50% means selling half of the current position.
• Stop-loss settings: You can add up to 3 stop-loss tiers. Each tier supports the following:
  • Price decrease: The percentage drop that triggers the stop-loss trade. For example, 30% means the stop-loss is triggered when price falls by 30%.
  • Sell quantity: The percentage of the current position to sell when this stop-loss tier triggers. For example, 50% means selling half of the current position.
• Max slippage: The maximum allowed price deviation when selling. Selling is usually easier to fill than buying, so you can set a relatively higher slippage.
• Fast mode and anti-MEV mode:
  • Fast mode: Broadcasts transactions through multiple high-stake nodes in parallel to improve on-chain speed.
  • Anti-MEV mode: Submits transactions only through anti-MEV services to avoid sandwich attacks.
• Priority fee: The fee paid to validator nodes. Higher fees increase the chance that the transaction is ranked earlier.
• Tip: The fee paid to the transaction relay and anti-MEV service. Higher tips rank your transaction earlier inside the service.
• Enable retry: Turn this on to automatically retry when a transaction fails.
  • Max retries: Set the maximum number of retry attempts. Currently, 1 to 3 retries are supported.
  • Retry interval: The waiting time between retries, in seconds.
  • Ignore slippage on retry: When enabled, retries bypass slippage checks to prioritize execution.