08 — Withdrawals or Trading Paused

Trigger: A planned or unplanned operational decision to pause withdrawals, deposits, trading, or another core user function. Includes both temporary (hours-to-days) and indefinite pauses.

First 30 minutes

Withdrawal pauses are the highest-anxiety operational event in crypto. The category memory of every collapsed exchange — Mt. Gox, FTX, Celsius, BlockFi — is associated with withdrawal pauses that turned into wind-downs. Even when your pause is genuinely operational and short-term, the audience reads it through that history. The communications discipline reflects that.

Confirm the pause is necessary. What is the operational reason? Is it brief (planned upgrade, network congestion) or open-ended (custody issue, security incident, regulatory directive)? Each has a different communications profile.
Open the hotline. “Withdrawal/trading pause: scope, reason, expected duration if known.”
Time-stamp the pause initiation. This anchors the narrative.
Decide on user-facing message before you flip the switch. Pausing without simultaneous communication multiplies anxiety. The pause and the message ship together.
Convene the war room. Eng, treasury, comms, counsel, support, community.
Decide who the pause affects. All users? All assets? One chain? One asset class? Specificity is everything.
Set internal escalation criteria. If the pause runs longer than [X] hours, escalation level rises. Document the level changes.
Brief support team. Volume will spike from minute one.

Holding statement template — short, planned pause

For announced pauses (network upgrades, scheduled maintenance):

[TIMESTAMP — UTC]
      
      [ASSET / NETWORK / SERVICE] [WITHDRAWALS / DEPOSITS / TRADING] are temporarily paused for
      [SPECIFIC OPERATIONAL REASON — e.g., "the Ethereum [UPGRADE NAME] upgrade, scheduled for
      [DATE]"].
      
      Expected resumption: [SPECIFIC DATE / TIME, UTC].
      
      User funds remain secure. [OTHER ASSETS / SERVICES] continue to operate normally.
      
      Status updates: [URL]
      
      — [Company]

Holding statement template — short, unplanned pause

For brief operational pauses (RPC issues, third-party integration failures, hot-wallet rebalancing):

[TIMESTAMP — UTC]
      
      [ASSET / SERVICE] [WITHDRAWALS / DEPOSITS / TRADING] are temporarily paused as we resolve
      an operational issue with [BRIEF DESCRIPTION — e.g., "our [NETWORK] node infrastructure" /
      "hot-wallet rebalancing"].
      
      User funds are secure. We expect to resume [WITHIN SPECIFIC TIME WINDOW — e.g., "within
      the next 2-4 hours"]. We will publish an update at [SPECIFIC INTERVAL — every hour].
      
      Status: [URL]
      
      — [Company]

Holding statement template — open-ended pause

This is the highest-stakes communication in crypto. Slow down, get counsel involved, draft carefully.

[TIMESTAMP — UTC]
      
      [COMPANY] has paused [SPECIFIC SCOPE — e.g., "withdrawals on the [PRODUCT] platform"] as
      of [TIMESTAMP].
      
      The reason is [SPECIFIC AND TRUE — without revealing operational detail that creates
      additional risk]. User funds are [SPECIFIC FACTUAL CLAIM — e.g., "held 1:1 in segregated
      custody" / "secured in cold storage"]. [LINK TO PROOF-OF-RESERVE OR EQUIVALENT].
      
      We are working to [SPECIFIC ACTION — e.g., "complete the operational review and resume
      service"]. We will publish a fuller update at [SPECIFIC TIME, NO MORE THAN 12-24h OUT].
      
      [OPTIONAL, IF TRUE: "[OTHER PRODUCTS / SERVICES / ASSETS] continue to operate normally."]
      
      — [Name, Role]

What the open-ended template doesn’t say: - “Temporarily” or “shortly” or “as soon as possible.” Vague timing is the worst signal in this category. - “Out of an abundance of caution” — overused, evasive, doesn’t communicate substance. - “We are confident we will resume” — over-promise. - “Solvency is not at issue” — only say this if it’s both true and verifiable. The audience has heard this before, and it didn’t always turn out to be accurate.

Stakeholder cascade

#	Audience	Channel	Who	Goal
1	Internal — full leadership	Slack #incident	CEO/COO	Unified picture
2	Treasury / custody team	Direct	Treasury lead	Confirm fund security/recovery posture
3	Counsel	Phone	Comms lead with CEO	Vet language; flag disclosure obligations
4	Regulator (if licensed entity, especially for open-ended pauses)	Per protocol	Compliance + counsel	Required notification — many regimes have <24h windows
5	Major customers / institutional	1:1 calls before public statement	Account/BD leads	Preserve relationships
6	All users	In-app + email	Comms lead	Unified message
7	Public — statement	X + status page + blog	Comms lead	Set the narrative
8	Press	Coordinated, not reactive	Comms lead	Single quotable line
9	Community	Discord + Telegram + AMA	Community lead	Detail and reassurance

For open-ended pauses: a community AMA within 24-48 hours is almost always the right move. Silent pauses become solvency rumors fast.

Do

Pair the pause with the explanation. Same minute. Don’t pause first and explain later.
Be specific about scope. “USDC withdrawals on Polygon are paused; all other withdrawals operating normally” beats “some withdrawals affected.”
Anchor on solvency / reserves with evidence, not assertion. Link proof-of-reserve dashboards. If you don’t have them, this is the moment that exposes the gap.
Update on a strict cadence (every 2 hours for the first 12 hours of an unplanned pause).
Have the founder visible. Open-ended pauses where the founder is silent multiply panic. Visible doesn’t mean defensive — it means present.

Don’t

Don’t say “shortly”, “temporarily”, “soon” without a specific time. Vague time language is the highest-cost word choice in this category.
Don’t blame “market conditions” for an open-ended pause. It reads as evasion.
Don’t allow the support team to give different reasons than the public statement. Consistency is essential.
Don’t let the founder tweet a one-liner reassurance. “Solvency intact, we got this” without substance is the meme image of a failed exchange.
Don’t quietly resume without announcing the resumption. Same prominence as the pause announcement.

Variants

Asset-specific pause (not platform-wide). Frame tightly: “USDT withdrawals on TRC-20 are paused; all other USDT networks operate normally.” Lower anxiety inherently.

Regulator-directed pause. When a regulator has directed the pause, the statement frames it as compliance with regulatory directive. Counsel essential; depending on the regulator, you may be forbidden from disclosing the directive itself.

Pause due to integrator / counterparty. When the pause is because a partner failed (custody provider, blockchain RPC, oracle), name the dependency without making them the scapegoat. Cross-reference 06 — Partner Blow-Up.

Pause as part of a broader operational issue. Pauses often cascade — a hack triggers a pause, a depeg triggers a pause, an outage triggers a pause. Use the relevant primary template; this one applies to the user-facing communications layer of the pause itself.

Resumption. Equally important communication. Same prominence as the pause announcement. Confirm what was done, what’s now operational, and what (if anything) users should do.

24-hour follow-up

Public post-pause analysis within 5 days for unplanned pauses.
Operational retro: did the cause justify the pause? Did the duration justify the user impact? Could the pause have been narrower? What changes?
Customer compensation decision (per terms of service or as goodwill). Apply automatically; do not make customers ask.
Regulator follow-up filings as required.
Update internal pause-decision protocols based on what was learned. Pause decisions are governance decisions; document who has authority.

Cross-references: 01 — Hack, 02 — Depeg, 03 — Exchange Outage, 06 — Partner Blow-Up, 10 — Token Crash.