Handling a rug accusation

Why the first hour decides it

Accusations spread on a different clock from explanations. A screenshot and a claim take seconds to produce and seconds to share. Establishing what actually happened takes longer, and by the time it is ready the story has usually settled.

That asymmetry is the whole problem, and it means the response has to be structured around speed rather than completeness. A short, accurate acknowledgement posted within minutes is worth more than a thorough explanation posted the next morning, because the first one changes what people are waiting for.

The practical target is to say something true and verifiable before the narrative hardens, then follow it with detail. Getting this order wrong is the most common way a survivable situation becomes permanent.

What usually triggers one

Most accusations are set off by something specific and visible, and knowing the list means recognising the trigger quickly.

• A liquidity figure dropping, which is frequently a range or indexing artefact rather than a withdrawal.
• A large transfer from a known team wallet, which may be an exchange deposit, a treasury move or something entirely routine.
• A sharp price fall, attributed to the team by default in the absence of another explanation.
• Holders unable to sell, which is usually thin depth or slippage and is read as a freeze.
• Silence during any of the above, which converts a question into a conclusion.

The first and fourth are worth knowing in detail before they happen, because both have innocent explanations that are common and both look damning to somebody who does not know that. The on-chain reading guide covers how to establish which one you are actually dealing with.

The evidence that settles it

Assertions are discounted automatically. What ends an accusation is a thing a sceptical person can open and verify without trusting you.

Every row is public information that costs nothing to publish. The reason teams struggle in the moment is not that the evidence is unavailable; it is that nobody assembled it in advance and gathering it under pressure takes the hours the situation does not allow.

Why silence reads as confirmation

The instinct to wait until you understand the situation fully is reasonable and it is the wrong instinct here.

An accusation poses a question in public. Every hour it goes unanswered is evidence, to anyone watching, that there is no good answer. That inference is not fair and it is entirely predictable, which means it should be planned around rather than resented.

The way through is to separate acknowledgement from explanation. Acknowledging within minutes costs nothing and commits you to nothing: you have seen it, you are checking, you will post what you find. That single sentence changes the state from unanswered to pending, which is a completely different thing to a reader.

What it must not do is deny anything you have not yet verified. A confident denial followed by a correction is worse than the original accusation, because it converts a question about the pool into a question about your reliability.

There is a specific tone that works and one that reliably fails, and the difference is not about politeness. Responding with evidence and no argument works, because it invites the reader to check rather than to take a side. Responding with indignation fails, because it turns a factual question into a dispute between two parties and readers have no reason to pick yours. The most effective posts in these situations are almost boring: here is the pool address, here are the balances, here is the lock transaction, here is when it expires. Nothing to argue with.

If the accusation is partly right

This is the case that decides whether a team survives its own mistakes, and the correct approach is counterintuitive.

Concede the specific thing, quickly, in your own words. If liquidity was moved, say when and why. If a team wallet sold, say how much and what for. If authorities were left enabled, say so and say what you are doing about it now.

The reason this works is that the chain will establish it anyway. Being the source of the information is the only variable you control, and it is the difference between a team that reported a problem and a team that was caught. Those two situations produce very different outcomes from identical facts.

What fails reliably is broad denial. Saying nothing improper occurred, when something did, invites people to find the specific thing, and they will, and everything else you said becomes suspect at the same moment.

Preventing the next one

Most accusations feed on ambiguity rather than on wrongdoing, which means most of them are preventable by removing ambiguity in advance.

1. Disable mint and freeze authority unless you have a stated reason, and publish that state. The authorities explainer covers what each one actually permits.
2. Lock liquidity and publish the transaction, including when it expires, because the expiry will be found regardless. The locking guide covers what that does and does not prove.
3. Publish your own wallet addresses. Labelled team wallets turn a suspicious transfer into a known one.
4. Explain unusual activity before it is noticed. A large planned movement announced beforehand is administration; the same movement discovered is an incident.
5. Keep a document ready with the pool address, the lock transaction, the mint account and the team wallets. Assembling it takes twenty minutes on a calm day and is impossible on a bad one.

That last item is the highest-leverage thing on this page. The teams that handle accusations well are almost never the ones that respond most cleverly; they are the ones who could post six links in the first ten minutes because the links were already written down.