# How we started

<https://rugpullprevention.medium.com/the-story-of-rugpull-prevention-21f690b7346c>

## <mark style="color:green;">Why create Rugpull Prevention?</mark>

The goal for Rugpull Prevention has always been to help the Avalanche community by providing quality tools to add transparency, confidence and clarity while maintaining an unbiased stance when evaluating projects.

![](/files/a1nFphtT1SH79LcEy4gH)

We started out alerting the community about possible RUGPULLS and have transformed into a multi-faceted and growing community of like-minded individuals. As the project has evolved, so have our goals. After completing our initial developments and data foundation tool "MetaDetect", we are able to offer a more unbiased approach to risk assessment. MetaDetect will be be used to help us determine and report the highest level of project transparency. It will also be used as the foundation of our tools.&#x20;

As we have grown, our project has become a trusted and valued community of Detectives, working together for a great cause. With much help from our "Undercover Detectives" we have been able to prove multiple cases of blockchain fraud and call out projects that are using deception, lies and other shady tactics to take your Avax.&#x20;

Celebrating our first anniversary we rolled out a new RugPull Investigations (R.P.I.) unit, added two new core team members and launched the Detective's Guild on mainnet!

![](/files/ByyxPtVaouKJXvH3fJMz)

##

###


---

# 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://enebula.gitbook.io/rugpull-prevention/introduction/how-we-started.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.
