> For the complete documentation index, see [llms.txt](https://redtoken.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://redtoken.gitbook.io/whitepaper/about-products/issues.md).

# Issues

## Platform-dependent

The existing fan communities are using their fan club platforms, and since the communities rely on their platforms to interact with their fans, they cannot proactively communicate with the fans.

## Limited interaction among fans

In the existing fan clubs, information is only delivered from the content providers to individual fans, limiting information exchanges among the fans as well as content suggestions given from the fans.

## Fan’s contribution activities are not recognized

Fan’s word-of-mouth effort and contributions such as derivative work do not pay off.

## High cost and complex operation for communities to develop their own websites

In addition to the high cost required to develop the community website, content providers incur operational and human resource costs. We think that for small and medium-sized content providers, building their own websites is challenging.

## Liquidity and Price Instability

Existing fan tokens include crowdfunding-related tokens and governance tokens, but we consider their unstable prices and low liquidity challenging.


---

# 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://redtoken.gitbook.io/whitepaper/about-products/issues.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.