Overview

Rugger Protection allows the bot to automatically track wallet changes for your ruggers.

Why is it 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 necessary?
Sniping developers who change wallets	✅ Yes
Sniping developers who keep the same wallet	❌ No
Copy trading of traders’ wallets	❌ No (usually)

The settings

Parameter	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 fresh wallets (details)
📏 Transfer Ranges	Filter by exact transfer amounts (details)
🧹 Remove if no launch	Automatically remove inactive addresses after a delay (minutes, min 15, or hours, max 168h)

🧹 Remove if no launch

This feature automatically removes from monitoring addresses that have neither created nor bought any token for the duration you set.

The problem it solves: with Rugger Protection adding addresses as transfers happen, your list can quickly fill up with “dead” addresses — wallets that never launch anything. They take up your slots for nothing.

How it works: you define a probation period. A single number is read in minutes (minimum 15), and you can also write a unit like 2h or 48 hours. The maximum is 168h (7 days), and 0 = disabled. If the address has not created or bought any token during this period, the bot automatically removes it from monitoring.

Example: Remove if no launch set to 2h. Protection detects a transfer and adds Wallet B. If Wallet B does not create or buy anything for 2 hours, it is automatically removed — your list stays clean.

💡 By child address : if the Parameter Inheritance is OFF, each child address receives the Remove if no launch set in your Child Address Defaults — so you can have different durations from one address to another (see Rugger Config).

Parameter Inheritance

When Rugger Protection adds a new address (child address), that address can either inherit the parent settings, or receive your custom settings.

This behavior is controlled by the toggle Parameter Inheritance in the parent rugger config. See the page 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 matter of 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 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 settings

You receive a Rugger Protection notification with the transfer details and the action taken by the bot.