> For the complete documentation index, see [llms.txt](https://docs.udderchaos.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.udderchaos.io/project/royalties.md).
# Royalties
From the beginning of Udder Chaos, we have had a goal of not being reliant on royalties. That said, royalties are a very beneficial additional source of revenue. After putting royalties to vote, holders voted on a declining royalty structure and staking enforced royalties.
#### Where do royalties go?
* 50% - Validator Self-Stake
* 25% - Increasing Token Value
* 25% - Team (Subscriptions, Salaries, etc)
100% of royalties are being reinvested into the project. Even the 25% that goes to the team is investing in the project. The team portion covers discord nitro subscriptions, server boosts, discord bots, development costs, pay for dev contracts, moderators and a salary for the founders. This enables the team to work full time on the project. While the value brought in is currently quite low because of a volume, as the project builds momentum, the team portion of royalties will allow us to expand the team and continue scaling up.\
\
The 50% validator portion, increases our validator self-stake which creates a consistent revenue stream for the project. More details can be found in [Validator Funding](/project/udder-chaos-validator/validator-funding.md).\
\
The remaining 25% that goes towards increasing token value is invested into many different utilities. For full details check out [$MILK Tokenomics](/project/usdmilk-tokenomics.md) and all of the sub-categories.
---
# 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.udderchaos.io/project/royalties.md?ask=&goal=
```
`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.