Telling a tool from a scheme
A checklist you can run in a few minutes against something specific that has been put in front of you. Twelve questions with a tally, six signals that decide the matter on their own, and an honest section on the things people treat as red flags that are not.
The one-sentence version
A tool sells you a defined job for a stated price and lets you verify the result; a scheme sells you a place in a queue and cannot tell you where in the queue you are.
How to use this page
Have something specific in front of you. This checklist is close to useless as general reading and quite useful when applied to one concrete offer, message, product page or invitation. Open the thing, work down the twelve questions, and mark each one as a clear yes, a clear no, or an answer you could not get.
The scoring is deliberately blunt. It does not produce a probability, because a probability would suggest more precision than any checklist deserves. It produces one of three outcomes: this behaves like a product, this behaves like an arrangement, or the answers are not available and that is the finding.
One instruction before the questions. Do not run this while a deadline is running. Every question below is easier to answer honestly with an hour of distance, and any offer that stops making sense when you take that hour was depending on you not taking it.
The twelve questions
Mark a point for every question you can answer clearly in the direction described. Questions you cannot answer score nothing, and a blank is not neutral.
- 1. Is there a named deliverable? Score a point if you can write down, in one sentence, what will be done in exchange for the money, without using the words opportunity, chance or entry.
- 2. Is there a price attached to the deliverable? A point for a stated price or a stated formula. Not for a percentage of an outcome that has not happened yet.
- 3. Is the customer somebody other than you? A point if the paying customer is a token team buying a service. If you would be paying to participate, no point, and you have already learned the most important thing on this page.
- 4. Does it still do something if nobody else joins? A point if the answer is yes and you can say what. Tooling works alone. An arrangement cannot answer this at all.
- 5. Can you name what you would check afterwards? A point if you could say which address you would open and what number you would count.
- 6. Is custody stated? A point if you know who holds the private keys of any wallet involved, and what happens to residual balances at the end.
- 7. Are the limits stated? A point if the seller has told you, unprompted, something their product does not do. Real products have edges and honest sellers describe them.
- 8. Is the timing public? A point if nothing about the plan depends on a moment being kept secret from people outside the group.
- 9. Is there any path where you profit without a later buyer? A point if yes. If every version of success requires somebody to buy after you at a higher price, no point.
- 10. Does the material avoid promising a return? A point if there is no claim about how much you will make. A tool sells a job. Only an arrangement needs to sell a number.
- 11. Does a structural question get a structural answer? Ask one. A point if you got a mechanism back rather than reassurance, enthusiasm or a change of subject.
- 12. Can you take a day? A point if you can wait twenty-four hours and the offer is still there on the same terms.
Reading the tally
Add the points. The bands below are wide on purpose, because a narrow band would imply the instrument is more sensitive than it is.
| Score | What it indicates | Reasonable next step |
|---|---|---|
| 10 to 12 | Behaves like a product with a customer and a deliverable | Evaluate it as a normal purchase, on price and fit |
| 6 to 9 | Product-shaped but with real gaps, most often around custody and limits | Ask the missing questions directly before anything else |
| 3 to 5 | The answers are mostly unavailable rather than bad | Treat unavailability as the finding and stop |
| 0 to 2 | Behaves like an arrangement with participants | Do not participate; nothing further needs establishing |
One caution about the top band. A high score means the thing is structured like a product, not that the product is good, priced fairly or run by competent people. Those are ordinary commercial judgements and this checklist does not make them for you.
Six signals that decide on their own
Some findings end the exercise. If any of these is present, the tally does not matter and there is nothing further to weigh up.
- You are asked to buy at a coordinated moment. This is the mechanism itself, stated out loud. Whatever else is true, the thing being described requires participants rather than customers.
- You are asked for a seed phrase or private key. No product needs this, ever. There is no configuration, verification or eligibility check that requires it. The request is the theft.
- A profit figure is promised. Nobody can promise a market outcome. A promised number means either the promiser does not understand what they are selling or the number is bait, and both conclusions lead to the same door.
- Access is tiered by how early you pay. A tool does not work better for people who paid sooner. A sequence of buyers does, which is precisely why the tiering exists.
- You are told not to discuss it outside the group. Secrecy is presented as protection and is functioning as isolation. Nothing about a legitimate purchase gets worse when a friend hears about it.
- The urgency has no external cause. Real deadlines come from outside: a launch time, a contract, a scheduled event. Manufactured urgency exists to compress the time you have to think, which is the only defence the offer has to get past.
Regulators publish plain-language warnings that describe these same shapes across many decades and many markets, and the investor alerts on the SEC website are worth reading precisely because they were written before this vocabulary existed. The wrapper changes constantly. The shape does not.
What pressure looks like in writing
Pressure is easier to spot in a message than in a conversation, because a message can be re-read. Three patterns are worth naming.
The first is the shrinking window. An offer that was open becomes an offer that closes soon, then an offer that closes tonight, without any external event changing. The shrinking is doing work, and the work is preventing the hour of distance recommended above.
The second is the moving goalpost. You ask a structural question, receive an answer to a different question, and the conversation moves on. Read the exchange again afterwards and check whether your actual question was ever addressed. Frequently it was not, and the exchange still felt cooperative.
The third is social proof by volume. Screenshots, member counts, reaction emoji, a stream of people saying it worked. None of this is evidence about mechanism, all of it is trivially produced, and its function is to make asking a question feel socially expensive. Noticing that feeling is the useful part.
Verifying a claim yourself
Most claims in this field are claims about a public ledger, which means most of them are checkable by anyone willing to spend ten minutes. You do not need special tools.
Start with the token address, not the name. Names are not unique and are not verified by anything. With an address you can open it on a public block explorer and look at the transaction history directly. What you are looking for is not sophisticated: whether trading exists outside the periods somebody is telling you about, whether holdings are spread across many addresses or concentrated in a few, and whether activity continues after any campaign was supposed to end.
Then compare the claim to the record. If you were told activity was organic, a record showing bursts from a cluster of freshly funded wallets says otherwise. If you were told a service delivered a quantity of trading, the swaps are countable and the count either matches or it does not.
What you cannot establish this way is intent. The ledger shows what happened, never why, and never who knew. That limitation is worth stating clearly rather than working around, because a confident story about intent that cannot be checked is exactly the kind of thing this whole page exists to slow down.
Things that look like signals and are not
A checklist that only adds suspicion makes people worse at deciding, not better. These are patterns that regularly get read as warnings and carry very little information.
- A new domain. Every real product had a first week. Age correlates weakly with honesty and strongly with survival, which is a different thing.
- Anonymous operators. Common across this entire market for reasons that include ordinary personal safety. Anonymity raises the cost of recourse, which is a real consideration, but it is not itself evidence of a scheme.
- Marketing language. Enthusiastic copy is a fact about the copywriter. Judge the structural answers underneath it, which are the part that is expensive to fake.
- A price that seems high. Expensive and dishonest are unrelated axes. So are cheap and honest.
- Automation itself. A great deal of ordinary market infrastructure is automated. The presence of a program says nothing about who benefits from it.
- Small user numbers. Niche tools have few users. Popularity is a signal about marketing budgets, and the fourth category is often the most popular thing in the room.
What a real vendor tells you before you pay
The best calibration for this checklist is reading something that passes it easily. A vendor selling into the tooling categories has a set of things they can state without hesitation, because those statements are what the customer is actually buying.
They can tell you what the software does in a sentence with no adjectives. They can put a number next to it. They can tell you which costs are theirs and which belong to the venue, since the venue portion moves with market conditions and no vendor controls it. They can tell you who generates the wallets and who can move funds out of them. They can tell you what happens when transactions fail, because a share of them always will. And they can tell you what the product does not do, which is usually the most informative sentence on any product page.
A vendor offering multi-venue volume automation has to be specific about which venues, because each one prices trades differently and the difference lands on the customer bill rather than the vendor. That specificity is not a courtesy; it is a structural property of selling a service to a customer, and its absence is exactly what the checklist is detecting.
None of this makes any particular vendor good. It makes the category legible, and legibility is what you are testing for. An arrangement resists every one of those statements, not because its operators are careless, but because writing them down would show the participant where they are standing.
Keeping a record while you decide
Whatever you conclude, keep the material. This costs nothing at the moment you do it and is impossible to reconstruct later, and the people who most regret not doing it are the ones who assumed they would remember.
Save the messages rather than summarising them, because a summary written a week later carries your interpretation rather than the original wording, and the original wording is what matters if you ever need to explain the sequence to somebody official. Screenshots with visible timestamps and usernames are more useful than copied text. Note the addresses involved, since names and handles change and addresses do not.
Write down what you were told would happen, in the exact words used, alongside the date you were told it. If the thing turns out to be a product, this record is simply a purchase file. If it turns out to be an arrangement, it is the difference between a report somebody can act on and a recollection nobody can verify.
Keeping records is also quietly useful for its own sake. The act of writing down what was promised tends to expose promises that were never actually made, which is a common and entirely ordinary feature of persuasive conversation. Several readers who run this exercise discover that the specific claim they were acting on was assembled by them, from implications, rather than stated by anybody.
If you are still unsure
Do nothing. That is a complete answer and it costs you an opportunity that, in the overwhelming majority of cases, was not one.
If you want to keep working on it, the most productive move is to write the offer down in your own words as though explaining it to somebody who has never heard of any of this. Ambiguity that survives conversation usually does not survive being written out, because writing forces you to name the customer and the deliverable, and if you cannot name them you have your answer.
Two further pages here go deeper than a checklist can. Why late buyers lose works through the arithmetic that decides who ends up holding a position in a thin market, and how coordinated buying works describes the mechanism at the depth needed to recognise it from the inside. If you have already sent money, what to do afterwards covers the first steps and the reporting routes without pretending the outcome is usually good.
Questions readers send about this page
How long should this take?
A few minutes for the twelve questions, and often less, because most offers fail one of the decisive signals before the checklist gets going. If an offer requires you to move faster than that, the speed requirement is itself one of the answers.
What if it scores in the middle?
A middling score is a reason to stop rather than a reason to proceed carefully. The checklist is designed so that a clear product produces a clear result. Persistent ambiguity across several structural questions usually means the answers are being avoided rather than that the subject is complicated.
Can a real vendor fail some of these questions?
Yes, and that is worth saying plainly. A small, honest operation may be disorganised, may not publish everything, and may answer a custody question badly. The checklist distinguishes structure, not competence. A vendor who is merely disorganised will still be able to describe a deliverable and a customer.
Does a well-known name make an offer safe?
Familiarity is not verification. Names are cheap to borrow, screenshots are trivial to fabricate, and being in a channel with many members says nothing about who is standing where. The structural questions do not care how recognisable the person asking is.
Someone I trust invited me. Does that change anything?
It changes how the invitation feels, not how the mechanism works. Most people who pass these invitations along believe what they are saying and are themselves somewhere in the sequence. Being invited by a friend is one of the most common ways people end up in the fourth category, and it is not a sign of poor judgement on anyone part.
What if I have already sent money?
Stop sending more, keep the records you have, and read the page on what to do afterwards. That page covers the official reporting routes in general terms and is honest about how often funds are recovered, which is less often than people are led to expect.
Written by The Pump Bot Primer Desk. This page is a reasoning aid, not a verdict on anything specific and not legal or financial advice. It names no group, project or person. If a question here has no clean answer for the thing in front of you, that ambiguity is information rather than a failure of the checklist. Terms are defined in the term list.