Sniper Guard
Sniper Guard
How Sniper Guard Works

During launch, Sniper Guard continuously tracks the total SOL amount bought by external wallets (wallets not part of your launch plan).
When the configured threshold is exceeded, Proxima automatically triggers the selected action.
This system operates in real time and only affects launch execution logic it does not modify on-chain rules or token mechanics.
Configuration
Enable Sniper Guard

You can enable sniper guard from Funding
When enabled, Sniper Guard becomes active immediately during launch execution.
Max External SOL

Defines the maximum total SOL that external wallets are allowed to buy before an action is triggered.
Example:
- If set to
4 SOL - Once cumulative external buys reach
4 SOL - The selected trigger action is executed instantly
This value represents a global threshold, not per-wallet.
Trigger Modes
When the external SOL threshold is exceeded, Sniper Guard executes one of the following actions:

Stop Buying
- Immediately stops further buy execution from your launch wallets
- External market activity continues normally
- Your remaining buy plan is halted
Recommended when you want to:
- Pause execution
- Preserve remaining capital
- Manually reassess the situation
Sell All
- Executes a full sell operation across participating wallets
- Designed as a last-resort safety mechanism
- Can optionally exclude the dev wallet
Dev Wallet Protection

Keep Dev Wallet
When enabled:
- Tokens held by the dev wallet are excluded from the Sell All action
- All other participating wallets are affected normally
This option only applies when Emergency Exit is selected as the trigger mode.
Whitelist (Optional)

Allows you to exclude specific wallet addresses from being counted as “external”.
- Whitelisted addresses do not contribute to the external SOL threshold
- Dev, funder, MEV, and holder wallets are automatically whitelisted
- Additional addresses can be added manually
Important Notes
- Sniper Guard only monitors buy activity
- It does not block external transactions at protocol level
- It reacts within your execution layer only
- All actions are logged and visible in launch activity