# Sniper Guard

<div data-with-frame="true"><figure><img src="https://19767660-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FhZA9uZY1DWCPEv0mhHVS%2Fuploads%2FQxWBgUshsVZRaEelav7V%2Fimage.png?alt=media&#x26;token=fe06c3c5-18ac-4ef5-89aa-69f96ddc7319" alt=""><figcaption></figcaption></figure></div>

### How It Works

1. You create a preset with your threshold and action
2. Enable Sniper Guard when launching your token
3. After launch, it monitors all incoming buys from external wallets in real time
4. If cumulative external SOL purchased crosses your threshold, it triggers your chosen action
5. Guard auto-expires after your configured duration (max 24 hours)

Monitoring happens in real-time — you can watch the progress live in the token dashboard sidebar.

### Configuration

#### Threshold

The maximum total SOL in external buys before protection triggers. For example, set this to 5 SOL, and if external wallets collectively buy more than 5 SOL worth of your token, the guard kicks in.

#### Trigger Action

Pick one:

* **Sell all** — dumps all positions across your launch wallets immediately
* **Stop buying** — halts any active buy automations or pending buys (Organic mode)

#### Sell Transaction Tip

Priority tip for sell transactions when the "sell all" action triggers. Defaults to 0.002 SOL. Set to 0 for no tip, or increase it for faster execution. Must be either 0 or at least 0.002 SOL.

#### Dev Wallet Protection

When enabled, the dev wallet is excluded from the "sell all" action. Your dev position stays intact even when all other wallets dump.

#### Expiration

How long the guard stays active after launch. Options: 1 hour, 6 hours, 12 hours, 24 hours, or a custom duration. Max is 24 hours — Sniper Guard is designed for launch protection, not long-term monitoring. You can cancel it manually at any time.

{% hint style="info" %}
It is recommended for users to disable it manually when they want to allow other buyers to enter in the token.
{% endhint %}

#### Whitelist

Wallet addresses excluded from the external buy count. Buys from whitelisted wallets don't count toward the threshold.

Three layers of whitelisting:

* **Dev wallet** — automatically excluded
* **Launch wallets** — all wallets used in the launch are automatically excluded
* **Custom addresses** — add team wallets, partner wallets, or known friendly buyers

You can update the whitelist even while the guard is active.

### Presets

Save your Sniper Guard configuration as a reusable preset. Each preset stores the threshold, action, tip, expiration, and dev protection settings. You can set one preset as your default so it's pre-selected on new launches.

Manage presets from the Sniper Guard config dialog — create, edit, delete, and set defaults.

### Live Monitoring

Once active, the Sniper Guard monitor appears in the token dashboard sidebar showing:

* **Progress bar** — how close external buys are to your threshold (turns yellow at 75%, red when triggered)
* **External SOL purchased** — cumulative amount vs your threshold
* **External buy count** — number of external buy transactions detected
* **Time remaining** — countdown to auto-expiry

If the guard triggers, you'll see the action taken and a detailed reason explaining what happened. If it hasn't triggered yet, you can cancel it manually.

### When to Use

Activate Sniper Guard on your token launch. It's most effective in the first minutes after deployment when sniper activity is highest. Enable it in the launch form by selecting a preset, optionally add extra whitelist addresses, and it starts monitoring as soon as the token goes live.