# Sniper Mode

Sniper mode watches for new token launches on DexScreener and automatically executes a buy the moment a trading pool is detected. This lets you get into a token within seconds of its launch — before the price spikes from early buyers.

Sniper mode is ideal for new meme coins, fair-launch tokens, and any token where being early significantly impacts your entry price.

***

## How Sniper Mode Works

This section details how the sniper system operates from the moment you configure it to when the trade executes.

### The Core Loop

1. You configure a token address and buy amount
2. ARCHONE monitors DexScreener for new trading pools on that token
3. The moment a pool is detected, ARCHONE executes your buy
4. TP/SL targets activate immediately after entry
5. You receive a notification with the result

The entire process — from pool detection to transaction confirmation — typically takes 3–15 seconds depending on network congestion.

### What "New Token" Means

Sniper mode targets tokens that are freshly launched. DexScreener shows new pairs as "LABEL: new" in their pair listings. ARCHONE tracks these and executes when your configured token matches.

***

## Setting Up Sniper Mode

### Step-by-Step

1. **Send `/snipe`** — Opens the sniper configuration panel.
2. **Enter the token address** — Paste the token's mint address you want to snipe. For example, if you're looking at a pump.fun token, paste the mint address.
3. **Set your buy amount** — Choose how much SOL to spend when the pool is detected. This is a fixed amount for every sniper entry.
4. **Configure TP/SL (optional)** — Set take profit and stop loss just like a regular trade:
   * TP1: Sell X% when price is +Y%
   * TP2: Sell X% when price is +Y%
   * Stop Loss: Sell all if price drops X%
   * Trailing Stop: Lock in profits dynamically
5. **Enable sniper mode** — Tap "Activate Sniper" to arm it.
6. **Wait for detection** — The bot confirms your sniper is armed. You're now waiting for a pool to appear.

***

## Sniper Settings

This section details each configurable sniper option.

| Setting           | Description                                  | Recommended                       |
| ----------------- | -------------------------------------------- | --------------------------------- |
| **Buy Amount**    | Fixed SOL amount to spend on sniper entry    | 0.05–0.2 SOL to start             |
| **Auto-Sell TP**  | Take profit targets after entry              | TP1 at +50%, TP2 at +100%         |
| **Priority Fee**  | Extra fee to validators for faster inclusion | High or Turbo for new tokens      |
| **Slippage**      | Max acceptable price impact                  | 3–5% for new tokens               |
| **Min Liquidity** | Minimum pool liquidity to trigger buy        | $5,000–$10,000 to avoid honeypots |
| **Max Token Age** | Max age of the pair in minutes               | 60 min default                    |

### Priority Fee for Snipers

New token launches are competitive. Other traders are also trying to buy. Higher priority fees increase your chances of being included in the next block before the price moves against you.

**Recommended settings:**

* For low-liquidity new tokens: **Turbo** (highest chance)
* For established new tokens: **High**
* For anything over 10 minutes old: **Medium**

### Slippage for Snipers

New tokens have low liquidity. A 1% slippage will likely fail. Use higher slippage to ensure your trade executes:

* **3% (300 bps)** — Minimum for most new tokens
* **5% (500 bps)** — For very low liquidity or high-demand launches
* **10% (1000 bps)** — Only for extremely illiquid tokens

Be aware: higher slippage means you may get a worse price if the trade executes.

***

## Pool Detection

### How Detection Works

ARCHONE polls DexScreener for new pairs matching your token address. When a new liquidity pool is detected:

1. **Pool detected** → ARCHONE calculates optimal swap route via Jupiter
2. **Route found** → Builds transaction with your configured priority fee
3. **Transaction built** → Signs with your encrypted wallet key
4. **Transaction sent** → Broadcasts to Solana via Jito bundle (if MEV enabled)

### Detection Latency

Detection takes 2–5 seconds from pool creation to ARCHONE receiving the signal. Execution then takes another 3–15 seconds depending on network conditions and priority fee.

Total time from pool creation to confirmed buy: **5–20 seconds**.

### After Detection Executes

Once your sniper buy confirms:

* A position is created in your portfolio
* TP/SL monitors activate automatically
* You're notified with the transaction hash
* Sniper mode automatically deactivates for that token

***

## MEV Protection for Snipers

Jito block engine bundles your transaction with others for better ordering. This reduces the chance of front-running — where another trader sees your buy and buys first, driving the price up before you.

### Enabling MEV Protection

Enable it in `/settings` → **MEV Protection: ON**

Jito adds a small tip to your transaction (set via Jito Tip setting). This tip is paid to validators for including your bundle.

### When to Use MEV Protection

**Use it for:**

* High-value sniper entries
* New tokens with high demand
* Any trade where front-running would significantly impact your price

**Skip it for:**

* Small entries where the extra tip costs more than you'd lose to slippage
* Tokens over 5 minutes old (less competitive)

***

## Preventing Duplicate Alerts

After ARCHONE restarts, it rebuilds its list of already-sniped tokens from your recent trade history. This prevents the system from alerting you about tokens you already own.

If you used sniper mode before a restart, those tokens are tracked in your database and excluded from duplicate notifications.

***

## Common Sniper Issues

| Problem                               | Cause                                         | Solution                      |
| ------------------------------------- | --------------------------------------------- | ----------------------------- |
| Sniper fires but trade fails          | Slippage too low                              | Increase slippage to 3–5%     |
| Sniper fires but insufficient balance | Buy amount > available SOL                    | Reduce buy amount             |
| Sniper doesn't fire                   | Token already has pool when you configured it | Sniper only catches NEW pools |
| Sniper doesn't fire                   | RPC stuck                                     | Try a different RPC or wait   |
| TP/SL doesn't trigger                 | Bot needs to be running                       | Restart bot                   |
| No MEV protection                     | Jito URL not configured                       | Enable MEV in settings        |

***

## Sniper vs Regular Trade

| Aspect             | Sniper Mode                     | Regular Trade         |
| ------------------ | ------------------------------- | --------------------- |
| **Timing**         | Waits for pool creation         | Executes immediately  |
| **Speed**          | 5–20 seconds from pool creation | Instant               |
| **Best For**       | New token launches              | Existing tokens       |
| **Competition**    | Other sniper users              | No direct competition |
| **Fees**           | Higher (priority fee)           | Lower                 |
| **Slippage**       | Must be higher                  | Can be lower          |
| **Pool Detection** | Automatic                       | Manual paste          |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.archone.trade/core-features/sniper.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
