# Origins: Fluffy Fudders

Round & cute. Fluffy & watchful. \
But beware... we are relentless & lethal.\
We are everywhere, we are a legion. <br>

Fluffy Fudders are born to FUD. \
Fear. Uncertainty. Doubt. \
These elements are the vital energy we harness to thrive.<br>

Fudding is in our blood. \
It is our livelihood & our commitment. \
Apart from having fun, we see it as our duties & responsibility to educate the crypto space on certain truths that are being swept under the carpet by scheming/dishonest teams & influencers. <br>

Since the inception of Bitcoin, we have honed the art of fudding, successfully dismantling hundreds of projects and ensuring they meet their rightful end.                 \
&#x20;                                                                                                 &#x20;

<figure><img src="/files/hY5NsntG6Hm1Q6X9pug7" alt="" width="375"><figcaption><p>We are watching... always watching!</p></figcaption></figure>

> *Rising from the depths & shadows of the crypto space, Fluffy Fudders emerged as a DARK knight to **cleanse** Web3 of its corruption, to put projects/teams to a **test** and to **reverse** the dilution crisis unfolding before our eyes.*              \
> &#x20;                                                                                                                            \- **Vitalik Buterin** (from Earth 69)


---

# 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/origins-fluffy-fudders.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.