What is a pump bot?

The short answer

A pump bot is not one thing. The phrase is used for at least four unrelated categories: launch tooling that a token team runs at the moment a token goes live, market-activity tooling that produces recorded trading on a token, ordinary execution bots that trade on rules for whoever owns them, and coordinated buying schemes, which contain no software at all and are simply an arrangement between people in a chat group.

Three of those are products with vendors, prices and public transaction trails. One of them is an arrangement in which the order people arrive decides who is paid and who pays. They share a name because the vocabulary of this market grew in group chats rather than in documentation, and because vagueness is more useful to one of the four than to the other three.

Everything below is an attempt to give each meaning its own definition, so that the next time somebody says the words you can ask a question specific enough to get a real answer.

Where the phrase came from

Two older phrases collided. "Pump and dump" is an old term from equities markets, describing a promotion campaign that inflates interest in a thinly traded asset so that whoever organised it can sell into the interest. "Bot" arrived from software, where it has always meant a program that performs an action repeatedly without a person clicking each time.

When automated trading became easy on public blockchains, both words were already in the room. Anyone selling automation had an incentive to reach for the more exciting one, and anyone running an arrangement had an incentive to reach for the more technical one. The result is a phrase that can mean a piece of paid infrastructure or a scheme, depending entirely on who is saying it.

It is worth noticing that neither half of the phrase was ever precise. "Pump" has never had a technical definition. "Bot" describes the delivery method, not the purpose. A phrase built from two loose words is going to be loose, and the looseness is not an accident that anyone is in a hurry to fix.

What the word bot is doing

In every one of the four meanings where software is actually involved, the software does a small number of ordinary things. It holds a private key, or several. It builds transactions. It signs them. It sends them to a node, waits to see whether they were included in a block, and decides what to do when they were not. That is the whole shape of it.

None of that is exotic. Transactions on Solana are ordinary data structures that any program can build, and the mechanics are described in the public Solana developer documentation. The difficulty in writing one of these programs is not conceptual, it is operational: a network producing blocks continuously will drop, delay or reject a meaningful share of what you send it, and the retry logic is where most of the engineering effort actually goes.

This matters for definition purposes because it strips away the mystery. When a person says the word bot, they are describing how instructions get sent, not what the instructions are for. Two programs with identical internals can be doing entirely different things, and the word bot will not distinguish them. That is why the second half of the phrase carries all the weight.

What the word pump is doing

"Pump" is used in two senses that people slide between without noticing, and separating them is probably the single most useful thing on this page.

The first sense is descriptive: a chart went up sharply. Used this way, "it pumped" is just a report about price, carrying no claim about who did what. Charts move for many reasons, including reasons nobody arranged.

The second sense is intentional: somebody set out to make a chart go up, in order to sell into the resulting interest. Used this way, the word describes a plan and, crucially, a plan that requires other people to buy after the plan starts working.

The slide between senses is where most of the harm lives. A message saying "this one is going to pump" borrows the innocence of the first sense while relying on the mechanics of the second. If you make a habit of asking which sense is meant, a lot of confident sentences stop making sense, which is exactly what you want to happen before you send money anywhere.

The four families the phrase points at

Each of these deserves its own definition, because they differ in who operates them, who pays, what the money buys and whether the outcome can be checked afterwards.

Launch tooling

Software used at the moment a token becomes tradable. The job is narrow and finishes quickly: get a set of transactions into the earliest blocks, in a specific order, without them being separated by other traffic. A token team buys this because launch moments are chaotic and the first blocks are contested. Whether that is a reasonable thing to buy is a separate argument, but the category is at least legible: a described job, a price, and a result you can look at afterwards in the block record.

Market-activity tooling

Software that sends a schedule of small buys and sells on one token, from wallets it controls, so that the token shows recent trading. The purpose is to affect what activity-sorted screens display, not to take a position. This is the category most often confused with the scheme, because both produce a chart that starts moving. The difference is structural: here a token team pays a vendor for a described service, and the trades are all visible afterwards.

Execution bots

General trading automation. Rules go in, orders come out, and the person who owns it is the person who profits or loses from it. Snipers, arbitrage programs, grid traders and portfolio rebalancers all live here. Nobody joins someone else execution bot; it is a private instrument, and if a stranger offers to run one for you the interesting question is why.

Coordinated buying schemes

An arrangement, not a program. A number of people agree to buy the same thinly traded asset at roughly the same time. The concentration of buying moves the price on a market that did not have much depth to begin with, and the movement is what gets sold to whoever arrives next. There is no vendor, no scope and no deliverable. Whatever software appears in the story is usually incidental, and often just a message-sending script.

The four side by side

Reading them in a row makes the differences hard to unsee. The last column is the one to keep in mind, because it is the property that cannot be faked with confident language.

Notice that the first three rows all have a named payer buying a named service. The fourth row has participants paying with their own market orders and receiving, in exchange, a place in a queue whose length and shape they cannot see. That structural difference survives every rebrand of the vocabulary.

Working out which one is in front of you

This is a short sequence rather than a checklist, because the order matters: each question narrows the field before the next one is asked.

1. Is there software at all, or only an arrangement? Ask what the program does when nobody else participates. Launch tooling and activity tooling still do their job. An execution bot still runs its rules. A coordinated buying scheme has no answer to this question, because participation is the mechanism.
2. Who is the customer? If the answer is "a token team", you are in the tooling half of the field. If the answer is "you, by joining", you are not looking at a product at all.
3. What exactly is being delivered? A vendor can describe the deliverable in one sentence and put a price next to it. An arrangement describes an outcome instead of a deliverable, and the outcome always depends on other people.
4. Can the result be counted afterwards? Trades are public. Ask what you would look up on a Solana block explorer after the fact to check that the thing happened. A vendor should be able to tell you exactly what to look for. If the honest answer is "nothing", the claim was never a claim about the chain.
5. What happens if fewer people show up than expected? For tooling, the answer is that the job is smaller and costs less. For an arrangement, the answer is that somebody is left holding a position nobody wants, and the interesting question is who has been standing where all along.

Five questions, none of them technical, and between them they separate a product from an arrangement more reliably than any amount of studying the marketing.

What none of them can do

Whatever the meaning, some claims are outside the reach of all four. These are worth learning as a group, because they are the claims most likely to be attached to the phrase when somebody wants something from you.

• None of them creates depth. Depth in a market comes from someone committing capital to both sides of it. Trading through a pool does not deepen the pool. A token can show a great deal of activity and still move violently on a modest order, because activity and depth are unrelated properties.
• None of them produces sustained price movement without sustained net buying. Balanced trading returns a market to roughly where it started, minus costs. Anything that goes up and stays up did so because more value came in than went out, from people who were not being reimbursed.
• None of them guarantees attention. Aggregators, trending lists and screening tools apply their own filters, and several of them actively try to discount activity that looks self-generated. Producing activity and being shown are different outcomes.
• None of them is an investment product. Money spent on transaction fees is spent, not invested. There is no position, no yield and no mechanism by which the outlay returns itself. Anything described as both a bot and a return is describing two things at once, and one of them is not true.

What the tooling meaning costs, illustrated

Because the tooling meanings involve real spending, it is worth seeing the arithmetic once. The numbers below are chosen to be round rather than typical, and describe no real campaign.

Suppose a program sends 1,000 swaps over a session. Each swap pays a network fee, and each swap also pays a venue fee to whatever pool or curve it trades against, plus whatever price movement the trade itself causes. Say the venue and slippage costs together average 1.4 percent of a trade, and the trades are 0.05 SOL each. That is 50 SOL of turnover, and 0.7 SOL consumed by venue costs and price impact before network fees are counted at all.

Now change one input. If the pool is thinner and the average cost per trade is 2.6 percent instead, the same 50 SOL of turnover consumes 1.3 SOL. Nothing about the software changed. The venue did. This is the single most important thing to understand about the tooling half of the field: the cost of producing activity is set by the market being traded, not by the vendor, and any quoted price that ignores the venue is quoting only part of the bill.

The full cost of a campaign like this, and the way vendors package it, is the subject a Solana volume bot is built to handle, which is also why the tooling side of this field has published pricing at all. An arrangement in a chat group has no equivalent arithmetic, because there is no service being priced.

Two further notes on the arithmetic. First, failed attempts still cost network fees, so a session with a high failure rate is paying for outcomes it did not get. Second, none of this spending is recoverable. It is a promotion budget with an uncertain result, which is a legitimate category of business expense, but it is not the same category as an investment and should never be presented as one.

Why the confusion is expensive

People do not usually lose money because they misunderstood a technical detail. They lose it because a word was doing two jobs, and the sentence they heard was true in one sense while they were acting on the other.

Consider a person who has read a vendor page describing activity tooling, understood it correctly, and concluded that this whole category is a normal service that token teams buy. That conclusion is fine. Now the same person is invited into a group where the same words are used, and applies the same conclusion. The words match. The structure does not. In the vendor case there was a customer and a deliverable; in the group case the person has become the input rather than the customer.

Running the categories in the other direction produces its own kind of error. Somebody who has only met the scheme meaning tends to assume the whole subject is fraudulent, which is not accurate either, and which makes it harder for them to evaluate an ordinary tool on its actual merits. Precision is not pedantry here; it is the difference between two very different decisions.

The distinction that catches most readers out is the one between tool classes rather than between tools and schemes, because those are genuinely similar objects doing genuinely different jobs. A launch-moment grouping tool and a continuous activity tool are both bought by token teams and both described as bots, and the comparison of volume bot vs bundler is the one people most often need spelled out before the rest of the vocabulary settles into place.

The rest of this site takes each meaning further. The page on four things that share one name goes deeper into how the categories differ in ownership and money flow, the tool-or-scheme checklist turns the five questions above into something you can run in a few minutes, and the pages under how people get hurt deal with the fourth meaning specifically, including what the arithmetic does to the people who arrive last.

Questions readers send about this page