Overview
Rugger Protection allows the bot to automatically track wallet changes of your ruggers.
Why is this necessary?
When you snipe a token developer, they regularly change wallets to cover their tracks. They transfer their SOL from wallet A to wallet B, then create their next tokens from wallet B.
Without Rugger Protection, you would lose track of the dev. With it, the bot detects the transfer and automatically adds the new address.
Who needs it?
| Situation | Protection required? |
|---|---|
| Sniping developers who change wallets | ✅ Yes |
| Sniping developers who keep the same wallet | ❌ No |
| Copy trading traders’ wallets | ❌ No (usually) |
Settings
| Setting | Description |
|---|---|
| 🔀 Mode | How the bot detects wallet changes (details) |
| 📌 Keep Address | Keep the old address in addition to the new one |
| 🆕 Fresh Wallet | Only add new wallets (details) |
| 📏 Transfer Ranges | Filter by specific transfer amounts (details) |
Settings inheritance
When Rugger Protection adds a new address (child address), this address can either inherit the parent’s settings, or receive your custom settings.
This behavior is controlled by the toggle Settings inheritance in the parent rugger config. See the page Per-Rugger Config for details.
⚠️ Important : If you use Keep Address ON, remember to disable inheritance to prevent child addresses from inheriting Keep Address ON and filling all your 30 slots in a few minutes.
How it works
Your rugger (Wallet A) sends 2.3 SOL → Wallet B
↓
The bot detects the transfer
↓
The bot checks the criteria:
✓ Amount within the Transfer Ranges?
✓ Is Wallet B a Fresh Wallet? (if enabled)
↓
✅ Criteria met → Wallet B added to monitoring
Keep Address OFF → Wallet A removed
Keep Address ON → Wallet A kept + Wallet B added
↓
Inheritance ON → Wallet B receives Wallet A's settings
Inheritance OFF → Wallet B receives your custom settingsYou receive a Rugger Protection notification with the transfer details and the action taken by the bot.