Crisis PR for Web3: what to say first when FUD, an exploit or a delisting hits

What crisis PR covers for a Web3 project

Quick test: Write the 3 facts you are sure of right now. A holding statement only uses what is certain.

Crisis PR gives a project team a disciplined way to communicate during an incident that may affect user confidence, partner relationships or public understanding. The work covers the message and its coordination; it does not replace technical incident response, legal advice or decisions made by an exchange or other platform.

We support teams responding to public claims, a suspected or confirmed exploit, a delisting notice, or uncertainty around a project update. The first task is to establish the communication problem: who is asking, what they need to know, and which facts the team can responsibly confirm. That creates a useful boundary between an update the team can publish now and questions that still require investigation.

A crisis response can include:

• A holding statement acknowledging the situation and explaining when the next update is expected.
• Talking points for leadership and community moderators.
• A short question-and-answer document for likely stakeholder concerns.
• Drafts for the project’s selected channels, with consistent wording and clear ownership.

For broader communications support, see PR and media. If the immediate need is a factual public announcement, press release distribution may be a separate or later step.

What should a team say first?

The first public message should acknowledge the issue, state only what the team has verified, and tell readers what is being checked next. A short, accurate holding statement is usually more useful than a detailed explanation assembled before the facts are stable.

Before drafting, gather the incident start time as the team understands it, the affected product or service, the current user impact, and the people authorized to confirm technical and operational details. Record which points are verified, which are under review, and which cannot yet be answered. Avoid language that implies a conclusion the investigation has not reached.

A practical holding statement usually answers three questions: what happened or was reported, what the team is doing now, and where readers should look for the next update. If users need to take a specific action, state it plainly and confirm that the instruction has been reviewed by the responsible technical or security lead. Do not fill silence with a promised resolution time unless the team can support it.

MarketingExtra begins with a claim-by-claim review: we compare each proposed sentence with the evidence and mark it as confirmed, provisional or not ready to publish. The team then approves the wording and designates one spokesperson or channel owner. For community guidance on handling FUD, read how to handle FUD in a crypto community.

Your 6-point crisis checklist

Check these 6 points in the first hour. They separate what is known from what is guessed, which is the difference between a calm statement and a post you have to retract the next day in public.

1. Write down the 3 facts you are sure of.
2. Name one person who approves statements.
3. Pick one channel as the source of truth.
4. Pause scheduled posts.
5. Draft a holding statement.
6. Set the time of the next update.

Terms in one line

Holding statement (in plain words: a short first message that says what is known and when more will follow).

Source of truth means the one place where official updates are posted first.

How the response differs for an exploit, FUD or a delisting

The response should match the type of incident: an exploit calls for careful status updates, public claims call for evidence-led clarification, and a delisting calls for precise wording about the notice and next steps. A single generic statement is unlikely to answer the distinct questions each situation raises.

For a suspected exploit, coordinate communication with the people investigating the affected system. Confirm whether users should pause an action, use an alternative, or wait for an update; publish an instruction only after the responsible team validates it. Explain what is known about impact without speculating about cause or plan. Keep a record of changes as the investigation develops.

For FUD—fear, uncertainty and doubt—sort the circulating claims into specific questions. Respond to claims that can be addressed with evidence, link to the relevant primary information, and correct material errors without amplifying every post. If a point remains unverified, say that it is being checked.

For a delisting, distinguish the platform’s stated action from the project’s own plans. Confirm the exact affected market or product from the notice, prepare a concise user-facing explanation, and avoid suggesting that a review or reinstatement is certain. If the project also needs to address longer-term search results or public information, consider online reputation management as a related workstream.

What the team should prepare for a crisis

Rule of thumb: One channel is the source of truth. Pin the statement there and link to it everywhere else.

A response is easier to verify when the team shares source material, decision ownership and a clear approval route at the start. You do not need a polished narrative before contacting us; a factual working file is a better starting point.

Gather the materials available to you, including incident notes, relevant public notices, technical updates approved for release, and links to existing statements. Add a named contact for each area that may need to confirm details, such as security, product, legal or partnerships. Flag sensitive information that must stay internal and identify who can authorize its publication.

A useful intake checklist is:

• What is the incident, and when did the team first become aware of it?
• Which facts have been verified, and by whom?
• Which users, partners or public channels may be affected?
• What action, if any, should readers take now?
• Who approves the statement, and who posts it?

We use this material to draft a concise message, identify unanswered questions and return the open points to the appropriate owners. The client retains control of final approval and publication. For planned media outreach once the facts are stable, sponsored articles in crypto media can be assessed separately from the immediate response.

Keeping crisis messages consistent across channels

A response stays coherent when every channel draws from one approved source of truth, even if each channel needs a different format. The core facts and next steps should match; length and level of detail can be adapted for the audience.

We agree who owns the central statement, who can approve changes and who is responsible for publishing each version. Then we prepare channel-ready copy for the places the project chooses to use, such as its website, community channel or social account. Moderators and support staff can receive concise answers to likely questions so that they do not have to improvise beyond the approved information.

During an active incident, a dated update log helps the team see what changed and when. Each entry can record the new fact, its source, the wording approved and the channel where it appeared. This makes it easier to correct an earlier statement openly if the evidence changes, rather than leaving conflicting versions unexplained.

The engagement can move from a first statement to follow-up updates, a media response or a post-incident explanation. The plan is agreed against the team’s immediate needs. If an announcement later warrants newsroom outreach, crypto media placements can be discussed after message, evidence and timing are approved.

What crisis PR can and cannot control

Crisis PR can improve the accuracy, clarity and coordination of the project’s own communications; it cannot decide how an exchange, media outlet or community responds. In particular, a platform controls its delisting review and any reinstatement decision, while technical findings and public reactions may change as new evidence appears.

For the project’s part, keep a single approved statement easy to find, date every update, and correct material changes in the same channels used for the original message. Avoid removing an earlier account without explanation when readers may still rely on it. If a public claim is disputed, show the evidence supporting the project’s position rather than relying on tone or repetition.

When reviewing a crisis communications proposal, confirm who drafts, who approves, what channels are in plan and how updates will be recorded. Ask how the team will handle a new fact that changes an earlier message, and how urgent approvals will reach the person authorized to decide. Those answers reveal whether the working arrangement fits the incident.

Send 3 things: what happened in 5 lines, the channels you use and who can approve statements. With those, we start the holding statement and confirm the cost in writing before anything is published.

How it works

1. Share the incident contextSend a concise summary, relevant public materials and the contact who can confirm facts. Mark any information that must remain internal.
2. Review claims and evidenceWe separate confirmed details from open questions and identify statements that need technical or leadership approval.
3. Draft the first responseWe prepare the holding statement and, where agreed, supporting talking points or channel-specific copy.
4. Approve and coordinateYour designated decision-maker approves the wording. We align the agreed versions and clarify who publishes each one.
5. Record and updateWe keep a dated record of approved communications and help prepare follow-up wording as verified information changes.