10 — Token-Price Crash

Trigger: The native token (or a token central to your product) is down 30%+ in 24 hours, or down 50%+ in 7 days, with community panic — independent of any underlying operational issue.

First 30 minutes

Token-price crashes test the discipline of doing nothing well. The instinct to do something — issue a statement, announce a buyback, defend the price publicly — is almost always wrong. The right posture in most token crashes is calm, fact-anchored continuity. The wrong posture is panicked validation of the panic.

That said, some price crashes are downstream of operational events that do require communication. The first job of this playbook is to distinguish.

1. Confirm the move and its scope. Is the token down because the broader market is down? Because a category is down? Or because of something specific to your project?
2. Identify the catalyst — or confirm there is none. Major unlock? Whale liquidation? Hack rumor? FUD post? Macroeconomic event? Genuine project-specific bad news? Each implies a different response.
3. Open the hotline. “Token crash: -[X]% in [Y] hours. Catalyst: [if known]. Operational issues: [yes/no — see other templates].”
4. If there’s an underlying operational issue (hack, depeg, regulator letter, etc.), use that template instead. Token crash from a hack is a hack-handling problem.
5. If it’s a market-driven crash with no project-specific cause, the playbook is mostly: stay calm, stay visible, and don’t make it worse.
6. Brief community team and support. Volume will spike on Discord, Telegram, X. Single talking point: “We’re watching the market like everyone else. Our [X-month / X-quarter] roadmap is [unchanged]. No updates from the project on this.”
7. Decide who is and isn’t visible. Founder visibility is calibrating: too much looks defensive; too little looks absent. Often: a brief pre-existing-roadmap update from the founder, on schedule, that doesn’t reference the price.
8. Brief market-makers and treasury counterparties if you have them. Operational coordination, not communications.

Holding statement templates

When no statement is the right answer

Most market-driven token crashes warrant no statement at all. Token-price commentary from a project’s official account is almost always a mistake. The audience that would be reassured by it doesn’t need it; the audience attacking the project will use any statement against the project.

Instead: continue normal product/marketing cadence. Ship the planned blog post. Hold the planned Twitter Space (don’t change the topic to “the price”). Publish the planned dev update.

When brief acknowledgement is required

For genuinely project-specific catalysts (e.g., a major partnership loss, a leadership change, a tokenomics issue):

[TIMESTAMP — UTC]
      
      [PROJECT] is aware of [SPECIFIC CATALYST — e.g., "the unwinding of the [PARTNER]
      relationship", "the announcement of [LEADERSHIP CHANGE]"].
      
      [OPERATIONAL CONTINUITY STATEMENT — e.g., "Product development continues per the published
      roadmap. The [SPECIFIC FUNCTION] previously handled by [PARTNER / PERSON] has been
      transitioned to [NEW STRUCTURE]"].
      
      We do not comment on price action. The project's focus remains [STATED MISSION / ROADMAP].
      
      — [Project]
      

When tokenomics or fundamental questions are being raised

Different category — the underlying claim has substance and won’t go away on its own. This usually requires a longer-form response (blog post, AMA, podcast appearance) within 5 days, not a quick statement:

[TIMESTAMP — UTC]
      
      A discussion is underway in [VENUE / COMMUNITY] regarding [SPECIFIC FUNDAMENTAL TOPIC —
      e.g., "the [TOKEN]'s emission schedule", "the project's treasury allocation", "the
      governance structure"].
      
      To address the substantive points: we will publish a detailed response at [SPECIFIC URL]
      on [SPECIFIC DATE WITHIN 5 DAYS].
      
      The published response will cover: [3-5 SPECIFIC TOPICS]. We invite community questions
      ahead of publication via [CHANNEL].
      
      — [Project]
      

What all templates deliberately avoid: - Direct commentary on the price action (“we believe the market is wrong” / “we see this as a buying opportunity”). Project officials commenting on price is almost always a regulatory and reputational error. - Buyback announcements made in panic. If a buyback is the right move, do it after the dust settles, not in the middle of a crash. - Comparisons to past prices (“we’re back to where we were in March”). Anchoring the audience to specific levels is a trap. - Threats against “manipulators” or “shorts.” Tone-deaf and counter-productive. - Promises of future price action. Don’t.

Stakeholder cascade

Do

• Continue normal product/marketing cadence. Visible business-as-usual is the highest-value response.
• Address substance if substance exists. A real fundamental concern about tokenomics doesn’t disappear; deal with it in long-form within a week.
• Engage major holders 1:1, not in public. Quiet reassurance to people who matter beats public reassurance to everyone.
• Decline to comment on price to press, in DMs, in AMAs, on Twitter Spaces. “We don’t comment on price action” is a complete sentence and the most consistent response possible.
• Track the catalyst. If the crash leads to retail panic that creates an operational issue (e.g., withdrawal pressure, support volume spike), the relevant operational template kicks in.

Don’t

• Don’t comment on price. Ever. Especially not as a project official, doubly especially not on X.
• Don’t announce a buyback in the middle of the crash. Any buyback should be planned in calm, executed with discipline, and announced after the fact (or as a pre-existing program).
• Don’t blame manipulators / shorts / “FUD spreaders.” Defensive, performative, counter-productive.
• Don’t promise future price action. Almost certainly a regulatory and reputational issue.
• Don’t disappear. The other failure mode — going completely silent — also reads badly. Continue regular cadence, just don’t talk about price.

Variants

Token unlock-driven crash. Major unlocks have predictable price impact. The communications around an unlock should pre-date the unlock, not respond to it. If you’re handling this in real time, the playbook is largely: don’t comment.

Macro-driven crash (broader market correction). Easy variant — clearly not project-specific, easier to maintain silence. Continue normal cadence.

Crash following a hack / depeg / outage / pause. Use the relevant primary template. Token crash is downstream of the operational event; addressing the operational event addresses the price (eventually).

Crash following a bad press cycle. Address the press substance through the appropriate channel (07 — Social Firestorm or direct press response), not the price.

Crash with retail panic that creates support volume. Brief support team to acknowledge and route to general resources, not engage on price specifically. “For market questions, please refer to community-led discussions in [CHANNEL].”

Crash that triggers liquidations of staked / lent positions. Different category — the operational impact on stakers and lenders may require platform-specific communication. See 02 — Depeg for cascading liquidation handling.

24-hour follow-up

• Audit what was said internally and externally during the window. Inconsistency is the long-tail risk here.
• If a substantive concern was raised during the panic, ship the long-form response within 5 days. Don’t let it linger.
• Brief the team on observed patterns; track any sentiment shifts that persist after price recovery.
• For projects with a treasury, consider whether the price action surfaces governance-level questions that should be tabled for the community via formal proposal.
• If the crash exposed gaps in market-maker arrangements or treasury management, address them in calm.

Cross-references: 01 — Hack, 02 — Depeg, 05 — Key-Person Event, 06 — Partner Blow-Up, 07 — Social Firestorm, 08 — Withdrawal Pause. Most token crashes are downstream of, not the primary cause of, an event covered elsewhere.