Amount Signatures
This snipes a launch by how much SOL got bought, not by a wallet you already track. You describe the shape of the create. If a new token matches, the bot buys.
Open it from the rugger list: 🎯 Amount Signatures. It is not inside one rugger. It sits on the wallet, next to Presets and Groups.
1 opens that rule. 2 adds another. A wallet holds 10 rules. The 11th is refused.
It is in beta. A match can miss the slot, buy a launch that only looked right, or sell late. Keep the size small until you trust the rule.
Packed, Full slot, Single
Tap Mode on the signature. It cycles through the three.
Packed only looks at buys that were inside the create transaction. Those are the wallets bundled with the dev. Your buy is aimed at that same slot, Block 0. Buys that show up a moment later, in the next slot, are invisible to Packed.
Full slot looks at every buy in the create’s slot, including ones that were not packed into the create transaction. It waits about 250 ms (one slot) before it decides. Your buy then lands in the following slot. It is never Block 0. Use it when the bundle is real but the buys are not all inside the create tx.
Single looks for one buy inside one range. That can be any buy in the create, or the dev’s own buy. One wallet is enough. It does not wait for a bundle.
| Mode | What has to be true | Where you land |
|---|---|---|
| packed (Block 0) | The ranges are filled by buys inside the create tx | Same slot as the create |
| full slot (Block 1) | The ranges are filled by buys in that slot | The next slot, about 250 ms later |
| single | One buy sits in the one range | The create transaction |
Three ranges on Packed are one condition
On one Packed signature, the Amount field holds every range, with a comma between them. This example is one test, not three:
| Wallet | Buys between |
|---|---|
| first | 2.6 and 2.8 SOL |
| second | 1.0 and 1.2 SOL |
| third | 3.0 and 3.4 SOL |
You type that as 2.6-2.8, then a comma, then 1.0-1.2, then a comma, then 3.0-3.4.
The bot treats that as a single test. All of it has to pass, or it buys nothing.
- The create needs at least three different wallets
- Each range has to catch a different buy. One 2.7 SOL buy cannot fill two ranges
- A fourth wallet can buy 9 SOL, or 0.2 SOL, or anything else. Extra snipers do not cancel the match
- If one of the three ranges has nobody in it, the whole signature stays quiet
Wallets is that minimum. If you type three ranges and leave Wallets empty, it becomes 3. You can set it higher if you want more wallets in the tx than you have ranges.
1 is Mode. 2 is the ranges. 3 is how many wallets are required.
Single is one range
Single fires when one buy is inside the range you typed. You do not need a second wallet.
Do not type three ranges on a Single signature. Single still wants one buy, so that list does not fire. Three separate triggers means three Single signatures, one range each. Any one of them can buy on its own. The other two do not have to match.
30 buys an hour, per signature
Each saved rule can buy 30 times in the last 60 minutes. It is a rolling hour, not a clock hour. The 31st match of that same rule is skipped. An hour after one of the buys, that slot frees up and the rule can fire again.
The three ranges on one Packed signature share those 30. They are one rule, so they do not each get a budget.
A second signature has its own 30. Ten signatures on the wallet means ten separate budgets. Hitting the cap is the rule working, not a missed button.
The other buttons
| Button | What it does |
|---|---|
| Buy | Your size in SOL when this rule fires. This is what you spend, not the size you are matching |
| Delay | Wait after the match, in milliseconds. 0 sends immediately. A delay can push a Packed buy out of Block 0 |
| Dev | Only fire if the dev’s own buy in the create is this exact SOL. Off means you do not care what the dev bought |
| Min MC / Max MC | Skip the launch if the market cap is outside this band |
| Wait fill | Wait until the buy you matched is actually filled, then send yours |
| ⚙️ Config | The hidden settings for this rule only: TP, SL, sell-after, and the rest. It does not change your other ruggers |
Examples
| You want | What to save |
|---|---|
| Block 0 only when three wallets buy 2.6–2.8, 1.0–1.2, and 3.0–3.4 | One Packed signature, those three ranges, Wallets 3 |
| Buy when the dev buy is about 1 SOL, even if nobody else matches | One Single signature, range 1.0–1.2, and set Dev if it has to be the dev |
| Buy on any of three sizes, each with its own 30 | Three Single signatures |
| The same three-wallet bundle, but you can accept landing one slot later | The same ranges, mode full slot |