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

# Token Economic Model

Token Allocation

The total supply of tokens is 100 billion, named MEDX. Initially, the tokens are planned to be issued on the BNB Chain network, with future expansion to ETH Layer2 networks such as Arbitrum and Base. The token allocation is as follows:

* 5% allocated to the team
* 10% allocated to VCs and investment institutions
* 3% allocated to market operations
* 5% allocated to OAT early users
* 2% allocated to market-making liquidity
* 75% released through the attention economy, with the release rate proportional to platform traffic contribution (the higher the traffic, the faster the release).&#x20;

The specific details are approximately calculated as follows: Total views / Daily release base = Total release volume.

Users earn points by watching videos, which can be directly exchanged for tokens, thereby obtaining the release volume.&#x20;

The release volume a user can obtain = (Number of videos watched / Total views) × Total release volume for the day

Users need to use tokens or U to purchase short videos.

<br>


---

# 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://mediax.gitbook.io/mediax/token-economic-model.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.
