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

# Dual Token Structure

To ensure sustainable growth and equitable value distribution within the global education ecosystem, XIIID adopts a **dual token structure**. This structure comprises the **XIIID Utility Token**, which serves as the primary utility and governance token for the platform, and **RWA (Real World Asset) Project Tokens**, which are directly linked to specific educational intellectual property (IP) domains.

**Core Roles of the XIIID Utility Token**

* **Platform Access and Utility**: Acts as the primary medium of exchange for all platform services, including access to educational content, AI tutors, and marketplace transactions.
* **Governance Participation**: Token holders can stake their tokens to gain voting rights and participate in key decision-making processes within the XIIID ecosystem.
* **Staking and RWA Token Swap Eligibility**: Staking XIIID tokens provides staking rewards and eligibility to swap for IP-linked RWA project tokens.
* **Ecosystem Reward Mechanism**: Distributed as rewards for ecosystem contributions, such as learning participation, content creation, and data provision.

**Core Roles of RWA Project Tokens**

* **Linkage to Real-World IP Domains**: Each RWA token is directly tied to specific educational IP domains (e.g., educational content, publications, B2B solutions, global licensing).
* **Revenue-Based Rewards**: A portion of the actual business revenue generated from the corresponding IP domain is automatically distributed to RWA token holders.
* **Domain-Specific Governance**: Grants holders decision-making authority (via DAO) over the development direction, new service launches, and technology development priorities for the specific IP domain.
* **Exclusive Benefits**: Provides priority access to premium content, exclusive events, and beta testing opportunities within the respective domain.

**Unidirectional Token Swap Mechanism**\
To ensure ecosystem stability and the independence of each project token, token exchanges are designed with a unidirectional swap structure:

* **XIIID → RWA Token Unidirectional Swap**: XIIID token holders who meet specific staking conditions can swap their tokens for RWA project tokens of interest. The swap ratio is determined based on project stage, market conditions, and staking duration.
* **No Reverse Swap**: Direct swaps from RWA tokens back to XIIID tokens are not permitted. This ensures that each project’s value and performance are evaluated independently, minimizing the impact of any single project’s failure on the broader ecosystem.
* **Market-Based Trading**: RWA token holders seeking XIIID tokens can exchange them through separate decentralized exchanges.

This dual token structure provides an economic model that balances the overall growth of the XIIID platform with the specialized development of various educational IP domains.


---

# 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://xiiid.gitbook.io/xiiid/tokennomics/dual-token-structure.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.