# $dogwifhat (Mid Cap Meme) ### Reason for initiating a FUD campaign against them: Issa, founder of the original dogwifhat meme, launched this token on ETH out of frustration with $WIF (SOL) getting to billions in market cap without giving him a share of the pie. \ The $WIF community was angered by the negative attention and liquidity fragmentation caused by this new token.\ \ On **February 4, 2024**, just one day after the $dogwifhat launch, a whale initiated a FUD campaign against it. ### Main challenges: * **Bullish Market and Memes**: The market was highly bullish with meme tokens experiencing significant gains. * **Liquidity Boost from $WIF**: $WIF had generated substantial liquidity & sparked a "cute dog" trend. * **Deployer**: Token deployed by Issa, the original creator of the meme. * **Narrative**: The story of $dogwifhat potentially surpassing $WIF. * **High Visibility**: $dogwifhat trended as #1 on Dexscreener and Dextools, with over $70 million in trading volume on its first day. * **Rapid Market Cap Growth**: Achieved a $20 million market cap within 20 minutes of launch. * **Exchange Listings**: Quickly listed on several centralized exchanges, including MEXC. * **Strong Support from Chinese KOLs**: Gained significant backing from Chinese key opinion leaders and supporters. ### Actions Taken by Fluffies: * **Initial Research**: With no pre-existing FUD on $dogwifhat, the research team thoroughly investigated to identify vulnerabilities and developed several FUD threads. * **Community Infiltration**: Over 50 Telegram accounts (including both Fluffies and bots) were easily integrated into the $dogwifhat community, as Telegram was not well-moderated. * **FUD Deployment**: The campaign began on February 4th, working closely with the $WIF community. * **Twitter**: Utilized more than 10 accounts to create negative threads and comments on promotional posts. AI agents flooded Twitter with likes, retweets, and influencer tags. Constant reporting of $dogwifhat and Issa’s Twitter accounts aimed at getting them suspended. * **Telegram**: Fluffies aggresively spread FUD whenever moderators were inactive and used trolling and softer FUD tactics when moderators were present, creating a hostile environment. AI agents recruited existing FUDders and DM-ed new members with warnings against buying. * **WeChat and Weibo**: Expanded the campaign to Chinese social media by translating and posting FUD content in Mandarin, leveraging the large Asian following. * **$WIF Community**: Rallying the $WIF community to participate in the FUD campaign, utilizing their unity and aggressive stance. * **KOL Engagement**: Using our smart wallet tracker, we identified several top-tier KOLs' wallets holding $WIF and approached them with $dogwifhat FUD. Many KOLs including Ansem then joined the FUD effort, leading to public roasting of Issa on Twitter Spaces. * **Strategic Manipulation**: Engaged Issa in conversation to set a trap, prompting him to admit to selling and dumping his own bags onto his community. * **Community Trust Erosion**: Implemented bot attacks to significantly lower the community trust score on Dexscreener and Dextools. * **MEV Exploitation**: Advised MEV players to exploit the high trading volume by using sandwich bots to capitalize on $dogwifhat’s liquidity.
### **Actions Taken by the $dogwifhat Team**: * **Ignored Official FUD Announcement**: The team disregarded Fluffies' official FUD notifications. * **Rejected Termination Fee**: Chose not to pay the termination fee that could have secured permanent immunity from future FUD attacks. * **Account Bans**: Banned several Telegram FUD accounts to mitigate the impact. * **Conflict with $WIF Community**: Engaged in a "war of the hats" with $WIF (Solana) community. * **Team Disengagement**: Issa became increasingly absent and disheartened due to the relentless FUD campaign. ### Outcome: * **Price Impact**: $dogwifhat fell to $0.16 just one day after the FUD campaign began. Within 2 weeks, the price dropped to $0.013 (a 92% decrease) and continued to decline to $0.007 (a 96% decrease) over 6 months. * **Loss of Support**: The project lost smart money, whales, and KOL backing entirely. * **Financial Losses**: The founder, Issa, failed to recognize the impact of Fluffy's campaign, resulting in substantial financial losses. * **Account Suspension**: Both $dogwifhat and Issa’s Twitter accounts were reported and suspended. * **Team Withdrawal**: The team abandoned the project, ceasing Twitter updates and Telegram interactions after 4 months. * **Reputation Damage**: The project became a pariah, with no one willing to CTO a heavily FUDded project.
### **Areas for Improvement**: * **Striking the right audiences:** Moved too slowly in targeting the Chinese communities.\ \ **Correction:** Never be too afraid to step out of comfort zone, into foreign languages, cultures & platforms to spread FUD, especially with the help of our AI Agents.
* **Campaign Duration**: The campaign ended too soon, allowing the price to rebound from its lows. \ \ **Correction**: If future budgets allow, extending the campaign would ensure the complete destruction of the targeted project, preventing any potential recovery or exit pumps. ### Post Campaign Sentiment: Fluffy Fudders recognized that 99% of beta, duplicate, or derivative projects fail to add genuine value to the space. Although Issa was the rightful creator of the meme, he could have pursued a collaboration or acquisition of $WIF rather than seeking a share of the success from an established community project. Launching a new token on a different chain inevitably invited backlash. While we sympathized with his situation, this campaign aligned with our principles to aggressively target and eliminate $dogwifhat from the market. We did not hold back and felt a sense of accomplishment witnessing the project's rapid decline. We hope our FUD efforts have served to warn and protect many unsuspecting traders. ### Click [HERE](< https://forms.gle/ZfoNcZKPR97ZZwjj6>) and fill up the form to create a FUD campaign! --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://fluffy-fudders.gitbook.io/fluffy-fudders/case-studies/usddogwifhat-mid-cap-meme.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.