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

# Token Ecosystem

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

**User Base and Global Reach -** Flickrz targets to establish a global user base, with monthly users from 170 countries and content available in nine different languages. Our close relationship with the world's top 5 webtoon platform assures that we deliver high-quality webtoons to millions of readers throughout the world. Our ambition is to establish ourselves as a major participant in the web3-driven digital content market.

**Token Ecosystem -** We have painstakingly created a sophisticated and precise token ecosystem that pays users for the time they spend on our platform. This ecosystem gamifies content consumption by providing features like level upgrades and more to boost user revenue. Our token will soon be listed on global exchanges, allowing users to trade and leverage their rewards.

**EP Points (Earnings) -** EP points are stored in the internal wallet. These EPs can be used to swap EP to FLKZ Token. EP can be swapped into FLKZ governance Token on the Flickrz website.&#x20;


---

# 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://flickrz.gitbook.io/whitepaper-flickrz/token-ecosystem.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.