> For the complete documentation index, see [llms.txt](https://docs.tomoon.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tomoon.org/usdtomoon-tokenomics/token-utility.md).

# Token Utility

### F**ee Structure**

There is a [platform fee](/platform-fee.md) incurred on each project made through our launch platform. The fee is then utilized for:

1. **Revenue-sharing**: 60% of the fees collected is redistributed to $TOMOON token stakers.
2. **Development expenses:** 20% is allocated to cover ongoing development expenses
3. **Buyback and Burn**: 10% is used to buy back and burn tokens, creating deflationary pressure.

### **Emission Strategy**

$TOMOON emission is designed to decay over time, ensuring early adopters are rewarded while controlling inflation.

> **Performance-based Emissions**: emissions are tied to certain KPIs in terms of number of successfully crowdfunded projects to ensure that emissions lead to protocol growth.

$TOMOON holders can vote on these KPIs in a decentralized manner. This is also in line with the aim to reach a sustainable balance where revenue from fees is higher than $TOMOON emissions.


---

# 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://docs.tomoon.org/usdtomoon-tokenomics/token-utility.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.