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

# Token Ecosystem

AliceToken's ecosystem is built on three foundational pillars: Creator Tokens, Governance Tokens, and Utility Tokens (AliceTokens), each designed to facilitate a vibrant, equitable, and interactive webtoon community.

### Creator Tokens

* **Purpose:** Allow webtoon creators to issue their own tokens, representing a stake in their creative work.
* **Benefits:** Direct monetization of content, enhanced fan engagement, and unique opportunities for content customization and exclusive access.

### Governance Tokens

* **Purpose:** Empower the AliceToken community to participate in platform governance, influencing content curation, platform upgrades, and policy changes.
* **Benefits:** A democratized platform that evolves in response to community feedback, ensuring alignment with user and creator needs.

### Utility Tokens (AliceTokens)

* **Purpose:** Act as the primary currency within the AliceToken ecosystem, enabling transactions, content access, and participation in exclusive events.
* **Benefits:** Streamlined transactions, increased platform liquidity, and incentivized participation in the ecosystem.


---

# 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://alicetoken.gitbook.io/alicetoken-whitepaper/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.