Common questions about Solana volume bots
Fifteen questions that get skipped in most guides, usually because they are the practical ones. Short answers, no sales language, and an honest no wherever the honest answer is no.
These are deliberately not summaries of the explainers. Each one is a question the desk keeps meeting on its own, about running the thing rather than understanding it, and the answers stay short enough to read in a queue. Where a question needs the longer treatment, the relevant explainer is linked at the bottom of this page rather than inside every answer.
Do I need to be able to code to use one of these?
No. Hosted tools put the whole thing behind a form, and the settings are words rather than code: which token, which venue, how many wallets, how big each trade is. What you do need is the ability to read a transaction on a block explorer, because that is how you check whether the tool did what it reported. That skill takes an afternoon and is worth more than any amount of configuration knowledge.
How much SOL do I need before I can start?
There is no universal minimum, and any figure quoted as one is a business decision rather than a technical limit. Work it out instead: multiply your planned number of swaps by the venue fee rate plus your priority fee, then add roughly 0.002 SOL of rent for every wallet that will hold the token, then add a margin for failed attempts. That total, not a round number somebody suggested, is your floor.
What happens if I close my laptop while a run is going?
It depends entirely on where the software is running. A hosted service executes on its own servers and keeps going regardless of your browser. Something running locally stops when the machine sleeps, usually leaving wallets part-funded and a schedule half finished. Establish which kind you have before the first run, because recovering a half-completed run is far more annoying than planning for it was.
Can a volume bot take my tokens?
Anything holding a private key can move whatever that key controls, which is why the structure matters more than the promise. Worker wallets should be disposable and hold only what a run needs. Your main wallet should never be involved and should not share a seed phrase with anything that is. If a tool asks for a seed phrase or a private key export at any point, that is not a security question, it is theft.
Why do two sites show different volume for the same token?
Because neither of them is reading an official number. Each service reconstructs volume from block data and decides for itself which pools count, which router programs it recognises, how to price SOL at the moment of each swap, and whether both legs of a trade are included. Different modelling choices produce different totals from identical chain data. When two figures disagree sharply, the interesting question is which venues each one includes.
Does more volume push the price up?
Not by itself. A buy and a matching sell return the pool close to where it started, minus the fees paid on both. Price moves when someone buys without selling back, which is a different activity with a different budget and a much larger one. Charts where volume and price rose together usually had genuine one-directional buying underneath, and the volume was a symptom rather than the cause.
Can I test any of this without spending real SOL?
Partly. Solana runs public test clusters where SOL has no value and transactions behave broadly like the real thing, which is enough to learn the interface and watch a transaction land. What test clusters cannot reproduce is a real pool with real depth, real competition for block space, and other traders moving the price between your quote and your execution. Treat them as a rehearsal room, not a dress rehearsal.
Do I need my own RPC endpoint, or is the free one fine?
Public endpoints are shared and rate limited, so they drop requests when busy. For reading balances and looking things up occasionally they are fine. For submitting hundreds of transactions on a schedule they are the most common cause of a run that looks broken but is not. A paid endpoint is the usual answer, and hosted tools include one, which is part of what their fee covers.
Can I run this on a token somebody else created?
Technically nothing stops you, because pools are permissionless and anyone may trade any token. Whether it is a sensible or defensible thing to do is a different question, and it changes the character of the activity considerably. Manufacturing activity around something you have no relationship with is harder to describe innocently than doing it around your own project, and that difference is worth thinking through before rather than afterwards.
Do I need a fresh set of wallets every time?
You do not have to, but reusing the same addresses across campaigns links every run together permanently and publicly. It also means old token accounts and leftover dust accumulate in wallets you have stopped tracking. Generating fresh workers per run costs the rent deposits again and keeps the accounting clean. Whichever you choose, keep a record of which addresses belonged to which run while it is still easy.
What happens to the SOL left in the worker wallets afterwards?
It sits there until something sweeps it back. Two amounts are involved: the unspent float, which returns immediately, and the rent deposits inside token accounts, which only come back when those accounts are emptied and closed. Some tools do both automatically and some quietly do neither. Check the balances yourself after a run rather than assuming, because across a few hundred wallets the total is not trivial.
Will a listing site tell me if it discounted my activity?
No, and it has good reasons not to. Publishing the filters would explain exactly how to evade them, so the criteria stay undisclosed and change without notice. This means a campaign can execute perfectly at the chain level and still produce nothing where you wanted it to appear. Nobody selling a tool can know in advance how a third party will treat the activity, and claims to the contrary are guesses.
Is a free volume bot ever the real thing?
The trades themselves cost money, so somebody is paying for fees, RPC capacity and servers. If it is not you, the arrangement deserves an explanation. Sometimes it is a trial, or a demonstration on a test cluster, which is honest. Sometimes the product is the key material you were asked to provide. Before running anything advertised as free, find the sentence that explains where the money comes from.
Does this help a token get listed on a centralised exchange?
There is no evidence that it does, and no mechanism by which it obviously would. Exchange listing teams have their own criteria, generally involving legal review, real holder distribution, genuine third-party interest and commercial terms. They have access to the same chain data as everyone else, and analytics that flag clustered self-trading are ordinary tooling. Assume a listing decision is unaffected at best.
Where do I look first when a run behaves strangely?
The run log, then a block explorer, in that order and nowhere else. Take a signature the tool reported and look it up yourself: either it exists on chain with the result claimed, or it does not, and that settles most disputes in under a minute. If the tool reports no signatures at all, the problem is almost always the connection to the network rather than the trading logic.
Answered by The Plain Solana Desk. If your question is not here, it probably belongs in the long form: the six explainers cover the mechanics properly, and single terms are defined in the word list. Anything still unanswered can be sent to the desk from the contact page, and good questions tend to become entries here.