How many wallets does a volume campaign actually need?

Wallet count is the setting with the largest effect on both what your campaign signals and what it costs, and it is usually chosen by accepting a default. Fleet size drives maker counts, account rent, funding overhead and self-contention all at once. Here is how those four pull against each other, and where the useful range sits.

Volion Research Updated Jul 30, 2026 4 sections

What wallet count actually buys

Fleet size buys unique makers, which several discovery rankings weight separately from volume, and it buys credibility, because a pair showing substantial volume from a handful of wallets reads as synthetic to anyone who checks. It does not buy volume: volume is wallet count multiplied by trades each multiplied by trade size, so the same volume is reachable from any fleet size.

Put plainly, wallets are how you buy breadth and trades are how you buy volume. Since these are separate signals scored separately, fleet size is not a proxy for campaign scale; it is a distinct dial. The distinction is worked through in makers vs volume.

Volion campaigns run from 500 to 10,000 wallets with a minimum trade of 0.1 SOL. The floor is not arbitrary: below a few hundred participants, maker-weighted surfaces have little to reward and the pair looks thin next to any organically active token. The ceiling is where per-wallet overhead starts dominating the budget without a corresponding signal gain.

What each additional wallet costs

Every wallet carries fixed setup costs regardless of how much it trades: SOL to exist and pay fees, and rent for the token account a first trade has to create. Those costs scale linearly with fleet size while the maker signal does not, which is what produces the diminishing return. A campaign at 10,000 wallets pays twenty times the setup overhead of one at 500.

The three per-wallet costs, in order of size for a typical campaign:

Token account rent. Charged once when a wallet first holds the token, because the account has to be created before it can hold anything. This is a deposit rather than a fee and can be reclaimed by closing accounts afterwards, but only if your tooling actually does that.
Base and priority fees per transaction. Every wallet's every trade pays these. Fee spend tracks transaction count, so fleet size matters here only through how many trades the fleet makes in total.
Funding transfers. Getting SOL into each wallet is itself a transaction with its own fee, so a fleet of 10,000 pays 10,000 funding fees before a single swap happens.

On top of these, apply the measured failure rate of your routing target, because failed transactions are charged in full. Our per-program measurements are on the measurement page, and the current sample shows DEX programs failing at several times the network rate of 27.9%.

The asymmetry to hold onto: maker signal saturates, overhead does not. Going from 100 to 500 wallets changes how a pair reads substantially. Going from 5,000 to 10,000 changes it much less while doubling every per-wallet line.

Large fleets compete with themselves

Solana locks the accounts a transaction writes to, so transactions touching the same account in the same slot cannot all execute and the losers are dropped. A large fleet trading one token is many transactions contending for the same curve or pool account, which means a fleet can raise its own failure rate simply by being large and fast. Spreading trades across slots is the fix.

This is the least intuitive cost of a big fleet and the one most often missed. Outside competition is not the only source of failures; your own wallets queue for the same accounts. Compressing 10,000 trades into fifteen minutes guarantees heavy self-contention, and the resulting failures are charged to you.

Duration is therefore not merely a stylistic choice about chart shape. It is the control that determines how much your fleet fights itself. The same 10,000 trades across six hours contend far less than across fifteen minutes, land at a higher rate, and cost less in wasted fees for identical volume.

Mechanism detail in priority fees, which covers why contention is per account rather than network-wide.

Choosing a number

Start from the signal you need rather than the budget. If you need breadth for a participation-weighted surface, go wide and accept the overhead. If you need to clear a volume threshold, go narrow and spend on trade size instead. If you need both, the middle of the range with a longer duration is more efficient than the top of the range compressed into a short window.

A reasonable decision procedure: pick the duration that matches the window you care about, then pick the largest fleet whose per-wallet overhead your budget absorbs at that duration, then set trade size to reach your target volume. Doing it in that order stops fleet size from being chosen last and by accident.

What to avoid is the configuration that maximises wallet count and minimises duration simultaneously. It produces the highest overhead, the highest self-contention, the highest failure rate and the shortest-lived signal, all at once. It is also, unfortunately, what "maximum wallets, fastest window" defaults tend to produce.

The console shows target volume, wallet count and estimated network cost together so the trade-off is visible before funding rather than after.

Fleet size interacts with routing, because the same wallet count costs more against a contested curve than a settled pool. Both cases are measured on the Solana volume bot overview and on the Pump.fun volume bot page.

Venue also sets the useful ceiling. On a bonding curve the volume a fleet can produce is capped by the curve remaining, so past a point extra wallets add rent rather than reach. In a deep Raydium or PumpSwap pool the constraint is slippage instead, and on concentrated venues such as Orca Whirlpools or Meteora DLMM it is where liquidity actually sits relative to price.

Questions

What is a good number of wallets for a volume campaign?

There is no single answer, because wallet count buys breadth rather than volume and the right amount depends on which signal you need. As a starting frame: a few hundred is the floor where maker-weighted surfaces have something to reward, and the top of the range mainly adds overhead rather than signal.

Do more wallets mean more volume?

No. Volume is wallet count times trades each times trade size, so any volume figure is reachable from any fleet size. More wallets means more unique makers, which is a different signal that some rankings weight separately.

Why does a bigger fleet fail more transactions?

Because Solana locks the accounts each transaction writes to, and a large fleet trading one token means many transactions competing for the same curve or pool account. Transactions that cannot get their lock are dropped and still charged. Spreading trades over a longer duration reduces this.

Is token account rent recoverable?

It is a deposit, so closing the account reclaims it. Whether you actually get it back depends on whether your tooling closes accounts after a campaign. Budget it as a cost unless recovery is explicit.

What does Volion support?

500 to 10,000 wallets per campaign, with a minimum trade size of 0.1 SOL. The console recalculates target volume and estimated network cost as you change fleet size, so the overhead is visible before you commit funds.

Makers vs volume Priority fees and contention Cost breakdown Clustering risk