> For the complete documentation index, see [llms.txt](https://learn.buildship.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.buildship.xyz/technical-docs/communities-we-dont-approve.md).

# Communities We Don't Approve

*While our app is open for every community, you can raise more than 500 ETH only if you have an Early Access Pass NFT.*

We **don't** launch communities that:

* have no doxxed team
* have a roadmap without guarantees and specific promises
* founders don't buy any NFT themselves
* that's their first project in web3

### DOXXED

Being doxxed doesn't always help, but NOT being doxxed is a 🟥 🟥 🟥.

There are great pseudonymous creators, which is not the same as anonymous.

### ROADMAP

Our mantra is: underpromise, overdeliver.

Roadmap is when you have plans for the next five years without any clear understanding how much it takes to execute

This includes even charity projects that raise money "to help penguins or Ukraine" etc!

### OWNING NFT

Usually people who want instant sell out are the ones who don't understand why users buy NFT.

If you don't own any, how can you create something that others would?

We don't sell FOMO. We sell digital **goods.**

### FIRST PROJECT

Launching a first project in web3 is best indicator yet of launching a rug pull. Crypto is an amazing tool to raise a lot of money because of

People see "success stories" and want to take part, so they apply their web2 mindset and "launch an ad campaign to generate traffic to our NFT minting website".

*No. ETH is for community, hackers and art.*

Since last August, I have closely interacted with at least 50 launched collections. There is a luck factor, of course. But mostly success is predetermined by being a type of person who gives first before asking, and who sets goals and executes them consistently.

### One last thing

Will you recommend your friend to mint it? Did you find five close friends who will?

### Recap

In the end, it all comes down to:

I am not gonna sell FOMO. I am not gonna sell FOMO. I am not gonna sell FOMO. I am not gonna sell FOMO. I am not gonna sell FOMO. I am not gonna sell FOMO.

{% embed url="<https://video.twimg.com/tweet_video/FQsNvrWakAIzS0l.mp4>" %}

Read more:

{% embed url="<https://buildship.xyz/community>" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://learn.buildship.xyz/technical-docs/communities-we-dont-approve.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
