> For the complete documentation index, see [llms.txt](https://alviroky.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alviroky.gitbook.io/docs/problem-with-actual-launchpads/short-term-impact-and-limited-token-dispersion.md).

# Short term impact & limited token dispersion

### Short term impact

The advisory and promotional impact of the project disappear when the launch is done, hurting the engagement and the popularity. As important as the pre-launch phase is the post launch phase, where the project has to keep growing in users and engagement to fulfill the roadmap.

### Limited token dispersion

For us this is the biggest problem. Some launchpads don't attract much investors, so they give a high allocation to them. This latter is traduced to very few people interested in the project and the price dumps. Other launchpads only offer lottery allocation just to benefit their own token, but on the sales again few users participate meaning low token dispersion and making the project vurnerable.

GuildPad will make sure that all the projects launched by the platform are supported after the sale, and with our allocation system we offer double token dispersion than the market average.


---

# 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:

```
GET https://alviroky.gitbook.io/docs/problem-with-actual-launchpads/short-term-impact-and-limited-token-dispersion.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.