> For the complete documentation index, see [llms.txt](https://docs.kaichi.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kaichi.xyz/deepdive/our-why/what-went-wrong-in-the-first-place.md).
# What went wrong in the first place?
## The memecoin dilemma
Recently, some celebrities and content creators have decided to launch their own memecoins, distribute them for free, and push for adoption by their communities. However, what exactly motivates the creator to give away their social capital for free, apart from the prospect of quick profit?
Most of the time, whenever a celebrity launches a memecoin, it results in short-term value extraction at the expense of the community. In other words, it's a trend towards zero.
Additionally, what exactly motivates the crypto industry to invest in such tokens?
Memecoin investors bet on various factors: community growth and associated culture, scarcity, exclusivity, speculative hype, utility beyond memes for some, and brand association.
These elements can certainly drive up the token's value, but in the long term, memecoins remain valueless, and only a few select candidates manage to gather enough "cult" following to endure the proof of time.
Among other criticisms, we note that current solutions exhibit three core challenges.
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.kaichi.xyz/deepdive/our-why/what-went-wrong-in-the-first-place.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.