# Why FUD??

Fluffy Fudders are born to FUD. We have had enough of the **dilution** rampant in the crypto space.\
\
Liquidity should be **concentrated** only to worthy projects serious enough to make a difference. \
If a project could not overcome Fluffies' fudding, they do NOT deserve to take a slice of the cake. 

We simply do not need pepeinu, babypepe, wrappedpepe, pepeshib, trumpepe, pepe2.0 & pepe0.5.

We also see it as our **duty to educate** the crypto community about the truths that are often concealed by deceitful teams and influencers, thereby safeguarding our community’s hard-earned money.

<figure><img src="/files/lShRk3l4iD2XSHNgrg9f" alt="" width="375"><figcaption><p>Don't cry, just FUD</p></figcaption></figure>

### So...what are FUD-worthy?

Some projects have clear red flags & malicious intentions to use retail investors as exit liquidity and we absolutely **HATE** to see them thriving in this space. \
\
Examples include larps, scam syndicates, projects with predatory tokenomics, lazy devs, internal hacks, airdrop baits, duplicates/forks/copycat and projects that raised millions but never ever launch.

### How should we respond then?

Investors usually sulk in defeat, accepting their losses in an unregulated space with little recourse.\
\
But Fluffies are built different. \
We FUD, we have FUN doing so while we burn projects to the ground. \
Cute, fluffy but lethal. \
\
We are ever ready to set some projects on FIRE, we mean it literally! 🔥

### 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/creating-a-fud-campaign/why-fud.md?ask=<question>
```

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.