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

# Token

$GOAT is bought back and burnt using a percent of revenue from the Dojo dex. Of the revenue received by the Goat Trading team, 50% goes to buying back and burning tokens. In regards to full trading fees of 1%: 33% goes to creators, 33% goes to the Goat team, and 33% goes to tokenholders.

Tokenholders benefit throughout the lifespan of the token. As opposed to similar protocols that only receive fees when a token is brand new, our system continues to receive fees from the trading of the token forever.

When new token types are being implemented and must be securely introduced into the system, $GOAT token is also likely to be used as a governance mechanism. This is only a plan at the moment and may or may not be implemented in the future.


---

# 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://goattrading.gitbook.io/dojo/token.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.