Static crawler version. Interactive docs are available at https://docs.memewar.zone/platform/war-room.
War Room Chat
How live campaign chat works during Prepare Mode and active MemeWarzone campaigns.
The War Room is MemeWarzone's campaign-level chat experience.
It is live for Prepare Mode and is designed to sit close to the campaign experience so users can follow community activity, launch preparation, safety reminders, and campaign discussion without relying only on scattered external chats.
Simple version
The War Room is for live campaign conversation.
Use it to:
- follow campaign discussion
- ask basic questions
- coordinate community attention
- clarify official links
- react to launch preparation
- organize squad and recruiter activity
- follow the battlefield mood in real time
Do **not** treat War Room activity as financial advice, proof of safety, or an endorsement by MemeWarzone.
During Prepare Mode
During Prepare Mode, the War Room helps early users organize before full live deployment.
It can be used for:
- campaign briefings
- creator updates
- recruiter and squad coordination
- questions from new traders
- reminders about fees, claims, and reward rules
- official-link clarification
- safety education before users start chasing live activity
Prepare Mode is about getting the battlefield ready. The War Room gives that preparation a live communication layer.
Read: **[Prepare Mode](/prepare-mode)**.
During active campaigns
When campaigns are live, the War Room becomes the campaign's battlefield chat.
Users can follow:
- live campaign sentiment
- buy and sell reactions
- UpVote pushes
- graduation attempts
- League category pushes
- community coordination
- creator updates
- squad participation
The War Room should make the campaign feel alive, but users should still verify everything before acting.
What the War Room is not
The War Room is not:
- financial advice
- a safety label
- an endorsement of a campaign
- proof that a campaign will graduate
- proof that a creator is trustworthy
- a replacement for checking official campaign data
- a place to trust random claim links
A busy chat can still exist around a risky campaign.
What users should still check
Before acting on anything discussed in chat, users should review:
- official campaign links
- campaign details
- creator or deployer information
- bonding-curve state
- graduation progress
- token distribution where available
- liquidity state where available
- suspicious activity indicators
- the exact wallet prompt before signing
If something looks urgent, confusing, or too good to be true, slow down.
Signing and access
The intended user experience is simple.
Users should not need to sign every chat message. After wallet or session access is established, chat should feel like a normal live community experience.
Users should still read wallet prompts carefully. Do not sign unknown messages from fake pages, fake claim links, or lookalike domains.
Moderation
War Room moderation protects the community layer from obvious abuse.
Moderation can target:
- spam
- phishing links
- impersonation
- malicious contract links
- fake support accounts
- fake claim links
- coordinated scam messages
- harassment or destructive behavior
Moderation helps reduce obvious threats, but it cannot make every message safe. Users remain responsible for verifying what they click and sign.
Link safety
Always verify official links before clicking anything shared in chat.
Official site:
https://memewar.zone
Official docs:
https://docs.memewar.zone
MemeWarzone support will not randomly DM users with urgent claim links, recovery offers, wallet verification requests, or secret airdrop pages.
Reporting suspicious activity
If a user sees a fake link, impersonator, malicious contract, or suspicious campaign behavior in War Room:
- Do not click the link.
- Do not sign any related wallet prompt.
- Capture the campaign URL, message, wallet, or screenshot if safe.
- Report it through official channels.
- Warn others without spreading the dangerous link further.
Read: **[Avoid Scams](/security/avoid-scams)** and **[Incident Response](/security/incident-response)**.