Wallet count and swap size, decided together

The short answer

Wallet count is how many separate addresses send the trades in a run. Swap size is how much each individual trade moves. Wallet count buys you spread across addresses and costs you a fixed overhead per address, paid before any trading happens. Swap size buys turnover per trade and costs you price impact, which grows with size relative to the depth of the venue you picked.

Set them together, not one at a time. A wallet count that looks cheap next to a large budget can consume most of a small one, and a swap size that is invisible in a deep pool is disruptive in a thin one.

Where the two fields sit

On most panels these two appear immediately after the venue selector, sometimes labelled wallets and amount, sometimes threads and trade size, occasionally makers and volume per trade. The wording varies; the arithmetic does not. A third field usually sits with them, controlling the interval between trades, and a fourth may offer a range rather than a fixed size.

If your panel offers a range, use it. A run where every trade is exactly 0.05 SOL at exactly thirty second intervals is a machine writing its signature into the transaction list, visible to anybody who scrolls it. A range of sizes and a jittered interval cost nothing extra and produce a schedule that at least does not announce itself.

What wallet count actually changes

Four things change when you move this number, and only one of them is the thing people are usually thinking about.

The number of distinct addresses in the transaction list

This is the visible effect. Turnover produced by six addresses and the same turnover produced by six hundred look different to anyone counting traders rather than trades. Explorers show a unique trader count next to volume, and so do most aggregators.

The fixed overhead paid before trading

Each worker wallet needs SOL for transaction fees and, for the token being traded, an associated token account. Creating that account requires a rent deposit. Neither cost depends on how much the wallet then trades, which means the overhead is a flat charge per wallet and dominates when the per-wallet trading budget is small.

The time to get started

Wallets have to be funded before they can trade. Funding forty wallets is forty transfers, each with its own fee and its own chance of needing a retry. A large wallet count means the first minutes of a run are spent on distribution rather than on trading.

The cleanup at the end

Every wallet that was funded holds a remainder when the run stops. Sweeping those remainders back is another transaction per wallet, and closing the token accounts to recover the rent deposits is another one. A high wallet count is a high cleanup cost, and tools differ in whether they do this for you at all.

The overhead per wallet, itemised

Worth seeing as a list, because it is the part of the cost that the estimate on the confirmation screen frequently understates.

The rent line is the one that surprises people. It is a deposit rather than a fee: Solana requires accounts to hold a minimum balance to stay alive, and that balance comes back when the account is closed. The mechanism is described in the Solana accounts documentation, and the exact minimum depends on account size, so treat any figure quoted here or in a panel as an approximation to verify rather than a constant.

The practical consequence: if your panel does not close token accounts at the end of a run, the rent is not recoverable in practice, and a hundred-wallet run has parked a meaningful amount of SOL in accounts you will probably never revisit. Ask about this before choosing a large number, because it is the difference between an overhead and a loss.

Few large wallets against many small ones

There is no correct answer here, only a trade you should make deliberately. The table sets out what each direction actually buys.

A useful rule of thumb, applied before the form rather than during it: decide the largest fraction of your budget you are willing to spend on overhead, and let that fix the wallet count. If you are unwilling to spend more than one twentieth of a run on fixed costs, and each wallet costs roughly 0.003 SOL to set up and clean up, then a 1 SOL budget supports something like sixteen wallets and not sixty.

What swap size changes

Swap size is simpler to reason about and easier to get wrong, because the consequence is not visible on the form. Three things move with it.

Turnover per transaction. The straightforward one. Doubling the size doubles the notional each trade contributes, and halves the number of trades needed for a given total.

Price impact per trade. Each swap moves the venue's price along its curve, and the movement scales with the trade's size relative to reserves. Small trades against deep pools have negligible impact; large trades against thin ones have a great deal.

Fee efficiency. Each transaction pays fixed costs regardless of size. Very small swaps are therefore inefficient: the fixed fee becomes a large percentage of a tiny trade. There is a floor below which shrinking the size makes the run worse rather than cheaper.

Those last two pull in opposite directions, which is the entire design problem in one sentence. Too large and slippage eats the budget; too small and fixed fees do. The comfortable range sits between them and depends on the venue you chose in the previous field guide.

Sizing against depth rather than budget

The instinct is to divide the budget by the number of trades you want. The better method is to start from the venue and work backwards.

1. Find the reserves

   Look up how much is in the pool or curve you selected, in the same unit as your swap size. An explorer or the panel's own venue display will show it. This number is the constraint everything else respects.

2. Pick an impact ceiling

   Decide the maximum price impact you are willing to pay per trade. Something modest is sensible for a first run, because impact is paid on every single swap and compounds across a schedule.

3. Derive the size

   For a constant product pool, impact is roughly the trade size divided by the reserve of the token you are paying with. A ceiling of half a per cent against a 400 SOL reserve therefore implies a swap size around 2 SOL, and a 40 SOL reserve implies around 0.2 SOL.

4. Check the floor

   Compare the derived size against the fixed cost per transaction. If fees are a large fraction of the trade, the size is too small to be efficient and the venue is too thin for the run you were planning.

5. Convert to a schedule

   Divide the turnover you wanted by the size you derived. That is the number of trades, and it has to fit inside the duration you are about to set. If it does not, one of the three has to move.

Doing it in this order means the venue constrains the size, the size constrains the trade count, and the trade count constrains the duration. Doing it in the opposite order means picking a duration first and then discovering that it demands a swap size the pool cannot absorb.

The funding calculation in full

Here is the arithmetic a confirmation screen is doing on your behalf, worked by hand so you can check it. Every figure is illustrative except the base signature fee.

Take twenty wallets, each making ten swaps of 0.05 SOL, on a venue charging one per cent. That is 200 swaps and 10 SOL of notional. Each wallet needs enough SOL to cover its trades and its own overhead, and the funding wallet needs enough to cover all of that plus distribution.

Read that table twice, because it contains the thing everybody misses. The trading float is not spent, it circulates: a buy converts SOL into tokens and a later sell converts them back, minus costs. What is actually consumed is the bottom group, roughly 0.22 SOL, of which the rent line comes back if the accounts are closed. The 10 SOL is working capital, not expenditure.

That distinction changes how you read a budget cap. A cap that counts notional will stop this run almost immediately, because 10 SOL of notional accumulates quickly. A cap that counts consumption will let it run to the end. Establishing which one your panel means is worth more than any other single question about the form.

Leftovers, dust and sweeping

When a run ends, twenty wallets hold small remainders of SOL and possibly of the token. Collecting them is a separate operation and one that panels handle with wildly varying diligence.

• Sweep SOL back to the funding wallet. One transfer per wallet, minus a fee. Amounts below the fee are not worth moving and are effectively gone.
• Sell or move the token remainder first. A wallet still holding tokens cannot have its token account closed, so the token has to go somewhere before the rent comes back.
• Close the token accounts. This is what returns the rent deposit. If the panel has no button for it, the deposits stay where they are.
• Record which wallets existed. If the keys were generated in your browser and you clear the profile, the leftovers become unreachable regardless of size.
• Check the funding wallet balance against your arithmetic. The gap between what you funded and what came back is the true cost of the run, and it is the only figure worth comparing between runs.

The checks before you save

Short list, run in this order, taking the venue depth from the previous field guide as given.

• Overhead is an acceptable fraction of the budget. Multiply wallet count by your per-wallet estimate and compare it against the total before anything else.
• Swap size sits inside your impact ceiling for this venue. Derived from reserves, not from the budget.
• Swap size is comfortably above the fixed cost per trade. Otherwise the run is paying mostly fees.
• Trade count fits the duration you are about to set. Trades divided by window gives the pace the panel will have to keep.
• The cleanup path exists. You know how remainders come back and whether accounts get closed.

If a panel exposes a maximum wallet count far above what your budget supports, treat the maximum as a marketing number rather than as a recommendation. The limit that matters is the one your own arithmetic produces, and any tool worth using will show you an estimate you can check against it. This is also the clearest way to compare tools: an automated Solana volume bot that shows its derived totals before you commit is answerable in a way that one which only shows a start button is not.

Where this leads

You now have a wallet count that respects your overhead tolerance and a swap size that respects the depth of your venue. Between them they imply a number of trades, and that number needs somewhere to happen: a window, and a spending limit that ends the run whether or not the window is finished.

That is the last field guide in this sequence, and it is the one that decides when everything stops. Read it before you start, because a run without an unambiguous stopping condition is the one failure mode on this site that has no cheap recovery.