How many wallets does a volume campaign need?

What the wallet count actually buys you

Wallet count and volume are different products. Volume is a currency figure; wallet count produces the metrics that sit next to it. Confusing the two is the most common reason a campaign hits its volume target and still fails to move anything anyone looks at.

Here is what a larger fleet actually changes:

• Unique participating addresses. The figure most screeners and listing filters read alongside volume, and the one a small fleet cannot fake by trading more.
• Trade count. More wallets sending smaller swaps produce more confirmed trades for the same total.
• Holder count, briefly. Wallets holding a balance mid-campaign register as holders. This reverses when they exit, which matters if someone screenshots the chart on the way down.
• Pattern plausibility. Forty addresses trading in sequence reads as forty addresses trading in sequence. Six hundred does not, provided the timing is not uniform.

What it does not change is the volume figure. Five hundred wallets sending 0.15 SOL and fifty wallets sending 1.5 SOL both produce 75 SOL of volume. Only one of them produces five hundred unique addresses.

What each wallet costs before it trades

Fleet size is not free, and the cost is not where people expect. It is not the swap; it is the deposit.

Holding an SPL token requires an associated token account, and every account on Solana must hold a rent-exempt minimum of 0.00203928 SOL. That is per wallet, per mint, charged the first time that wallet ever touches your token.

Two things soften that. The rent is a deposit, not a fee, and closing the token accounts returns it. And it is charged once per wallet per mint, so a fleet that already holds your token pays nothing the second time around. What it does mean is that fleet size has a working capital cost that scales linearly and independently of how much volume you route. The full breakdown of where the rest of the money goes is in the fee guide.

Why 500 is the floor here, not 50

Campaigns on this site start at 500 wallets, and the reason is not upselling. Below a few hundred addresses the campaign starts producing the wrong shape.

A small fleet has to send larger swaps to reach any given volume, which means more price impact per swap, higher slippage tolerance, and a higher failure rate in thin pools. It also means each address trades more times, which is the single clearest signature in the data: a normal token has a long tail of addresses that traded once, while a small fleet produces a short list of addresses that each traded twenty times. That distribution is visible to anyone who sorts the transfer list, and no amount of timing randomisation hides it.

Larger fleets fix this almost for free, because the marginal cost of another wallet is two thousandths of a SOL in recoverable rent and five thousandths of a lamport-scale fee.

Choosing a number, in three questions

1. What are you trying to move? If it is the volume column alone, wallet count barely matters. If it is trade count, unique addresses or a discovery surface that weights participation, wallet count is the variable and volume is the constraint.
2. How thin is the pool? Divide your target volume by the largest swap the pool absorbs without moving more than a percent or two. That quotient is roughly the minimum number of swaps, and therefore the minimum sensible fleet.
3. How long is the window? A four-hour campaign across six hundred wallets is comfortably paced. The same fleet across twenty minutes is a burst, and bursts read as bursts.

Worked through: 200 SOL of target volume into a pool that tolerates about 0.2 SOL per swap needs roughly a thousand swaps. At one round trip per wallet that is five hundred wallets, at two round trips it is two hundred and fifty. Both are defensible; the first produces twice the unique addresses for about a SOL more in recoverable rent. The sizing guide covers how to derive the 200 in the first place rather than guessing it.

Four ways fleets get wasted

• Funding every wallet identically. Six hundred addresses holding exactly 0.2 SOL is a fingerprint. Fund inside a band.
• Trading in wallet order. Sequential activity across a numbered fleet is the easiest pattern in the world to spot. Order should be random and spacing uneven.
• One swap per wallet, ever. Real addresses come back. A fleet where no address ever trades twice is as unnatural as one where every address trades twenty times.
• Never closing the accounts. Leaving five hundred token accounts open locks a SOL of your own money for no reason and leaves the fleet standing as a permanent, greppable artefact.

The fourth one deserves an extra sentence, because it is the one people dismiss as housekeeping. An open token account is a permanent public record that a specific address once held your mint. Closing them at the end of a campaign both returns your deposit and removes several hundred standing rows from the list anyone gets when they query holders of that token later. Leaving them open costs money and leaves evidence, which is an unusual combination of downsides for a step that takes one instruction.

What we do by default

The console starts at 500 wallets and a 0.1 SOL minimum swap because that combination is the smallest one that produces a believable distribution in most pools. Above that, the trade-off is straightforward: raising wallet count while lowering swap size buys trade count and unique addresses at the price of a slightly larger rent float, and raising swap size while lowering wallet count does the reverse.

The fee does not change either way. It is a flat percentage of target volume, so a thousand-wallet campaign and a five-hundred-wallet campaign at the same volume cost exactly the same. That is deliberate: the wallet count should be chosen on what you are trying to move, not on what it costs. You can move the slider and watch the estimated swap count and unique address figure update live in the console on the home page, with the exact SOL figure shown before anything is submitted.

If you take one thing from this page, make it the distribution point. The number of wallets matters far less than whether the activity across them looks like a population or like a script working through a list.