> 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/our-solutions.md).

# Our Solutions

## Fan community development support

We will support the content providers in issuing community participation proof NFTs and managing their communities.

<figure><img src="/files/oZqmjkyNEJ7CawwYrq7V" alt=""><figcaption></figcaption></figure>

## Ticket NFT sales support

We will design ticket NFTs that will be used at various physical events including our partner facilities, starting with our RED° TOKYO TOWER.

<figure><img src="/files/9pj3RmjNGTGh0VXkX2MQ" alt=""><figcaption></figcaption></figure>

## E-Commerce Support

We will support the content providers in admission tasks such as NFT ownership verification, required when the content providers sell exclusive products to NFT holders.

## Token incentives for fans

We will support the content providers in designing incentive structures so that users will be rewarded for introducing content to others, bringing in new users for the content, and such.

## Token incentives that do not rely on content providers’ proprietary tokens

The existing fan tokens have been issued for each respective content, which has led to liquidity issues and speculative demand, resulting in tokens’ unstable prices. Therefore, we plan to use a common fan token among the content providers to provide liquidity and stabilize prices. We are also convinced that by making the common fan token among the content providers, the fans will gain opportunities to access new content they are not familiar with. Therefore, the content providers can acquire new visitors from different fan communities, revitalizing the content services in the facility. We believe that for the content providers, this will be not a zero-sum effect, but a positive-sum effect.


---

# 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/our-solutions.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.