When a token price crashes, the first 48 hours decide whether it becomes a temporary drawdown or a lasting loss of confidence. The right response is to find out why it happened before you act, communicate early and factually, make sure liquidity is still functioning, and avoid dramatic gestures you cannot sustain. Most of the lasting damage we see after a sharp drop comes not from the drop itself but from how the team reacts to it. Below are the eight most common mistakes, each with the fix, followed by a response plan you can prepare before you need it.
First: What Kind of Crash Is It?
Not every sharp drop has the same cause, and the right response depends on which one you are facing.
| Cause | Typical signs | Primary response |
|---|---|---|
| Market-wide sell-off | Majors and your sector down together | Communicate context; keep liquidity steady |
| Large holder or unlock selling | Known wallets moving to exchanges; unlock date | Explain the movement; check depth |
| Liquidity failure | Spread blows out, thin book, sharp wicks | Restore quoting; talk to your market maker |
| Security incident | Unexpected contract activity, drained pools | Contain first: pause where possible, then disclose |
| Negative news or FUD | Social spike around a specific claim | Answer the claim with facts and evidence |
| Leverage cascade | Perp liquidations, funding swings | Explain mechanics; review spot depth |
Spending the first hour on diagnosis is not wasted time. It is what prevents the mistakes below.
Mistake 1: Going Silent
The instinct to wait until you have the full picture is understandable. But silence is read as either ignorance or guilt. Within an hour, someone in your community will offer an explanation, and it will usually be worse than the truth.
The fix: Post a short holding statement quickly. Acknowledge the move, state what you know, state what you are checking, and say when the next update will come. Then deliver that update on time. You do not need all the answers to show you are present.
Mistake 2: Blaming the Market Without Checking
"The whole market is down" is sometimes true and often only partly true. If your token fell much further than its sector, or if the drop started before the broader move, the community will see that on the chart and stop trusting the statement.
The fix: Compare your move against majors and a handful of peer tokens over the same window before you say anything about causes. If the market explains part of it, say that, and say what else you are looking at.
Mistake 3: Panic Buybacks
Announcing a buyback in the middle of a crash feels decisive. In practice it often spends treasury into a falling market, signals desperation, and sets an expectation the team will have to repeat at every future drop.
The fix: Buybacks should follow a pre-agreed policy with clear triggers, budgets and execution rules, decided when nobody is panicking. If you do not have one, do not improvise it during a crisis. Our token buyback programmes guide covers how to design one properly.
Mistake 4: Ignoring the Order Book
A crash with a functioning order book is a price move. A crash with a broken order book, where spreads blow out and depth disappears, is a liquidity failure, and it makes every subsequent sell more damaging.
The fix: Within the first hour, check spreads and depth on every venue. If your market maker is not quoting or depth has collapsed, raise it immediately. The point of professional market making is that two-sided liquidity continues through volatility; it does not mean propping up price. Our guide to market making strategies in volatile markets explains what you should expect to see.
Mistake 5: Moving Treasury or Team Tokens Without Explanation
On-chain watchers track team, treasury and investor wallets. During a crash, any movement from those wallets will be screenshotted and framed as insiders selling, even when it is an internal transfer or a return of loaned tokens.
The fix: Freeze non-essential treasury and team wallet movements during the crisis window. If a movement is necessary, explain it before or as it happens, with the transaction and the reason. This is especially relevant if you are mid-way through a liquidity provider change; our guide on how to switch market makers covers how to handle loan recalls without alarming the market.
Mistake 6: Overpromising
Under pressure, teams announce roadmap items early, promise partnerships that are not signed, or commit to price-related outcomes. Every one of those becomes a liability when it slips. Statements that imply price support or returns can also create legal risk.
The fix: Only communicate what is already true or already scheduled. Never promise anything about price. If you want to remind the community of progress, point to shipped work and measurable usage, not plans.
Mistake 7: Arguing With Everyone
When FUD spreads, teams sometimes reply to every critic, delete critical comments or ban users en masse. All three amplify the problem: arguments spread the claim, deletions look like hiding something, and bans create more angry accounts.
The fix: Answer the specific factual claims once, clearly, with evidence such as on-chain data, audit reports or vesting contracts. Pin that answer. Moderate genuine spam and scams, but leave honest criticism up. One calm, factual thread does more than a hundred replies.
Mistake 8: No Post-Mortem
Once price stabilises, the temptation is to move on. But a crash usually reveals something structural: a thin book on one venue, an unlock nobody modelled, an unclear holder concentration, or a communication gap.
The fix: Within two weeks, write an internal post-mortem: what happened, what the team did, what worked, what did not, and what changes. Consider publishing a summary. Communities forgive drawdowns far more readily than they forgive the same mistake twice. Our article on why tokens fail after launch covers the structural issues that most often surface this way.
The 48-Hour Response Plan
Prepare this before launch and assign an owner to each line.
Hour 0 to 1
- Confirm the move across venues and compare against majors and peers
- Check spreads and depth on every venue; contact your market maker
- Rule out a security incident: unusual contract calls, pool drains, admin key activity
- Post a short holding statement with a time for the next update
Hour 1 to 6
- Identify likely cause: market, unlock, specific wallets, leverage, news
- Freeze non-essential treasury and team wallet movements
- Publish a factual update: what happened, what is known, what is being checked
- Brief moderators with the approved facts and a moderation policy
Hour 6 to 48
- Answer specific claims with evidence; pin the answer
- Monitor liquidity hourly; escalate any venue where depth has not recovered
- Hold scheduled communications; avoid new promises
- Schedule the post-mortem
Prepare Before You Need It
The teams that handle crashes well are rarely the ones with the best instincts under pressure. They are the ones that wrote down, before launch, who speaks, who checks liquidity, which wallets are frozen, and what the buyback policy is. Put this plan in your launch runbook alongside listing and TGE tasks.
Fibonacci Capital provides market making that keeps two-sided liquidity in place through volatile periods, with clear reporting so teams can see what is happening in their order books when it matters most. If you want to review how your token's liquidity would hold up in a sharp sell-off, get in touch.