> 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/udder-chaos-validator/validator-funding.md). # Validator Funding #### Where do validator profits go? * 50% is reinvested in the validator * 25% is invested in token value * 25% for team and expenses The 50% reinvested into the validator is to compound and continually grow the amount that we are earning. We are accumulating as much SOL to self-stake to stablize the growth of our project and ensure long-term success. We aren't thinking about a month or two from now, we're thinking 10-20 years from now.\ \ The other 25% invested in token value and 25% invested in team/expenses are broken down further in the [Royalties](/project/royalties.md) section. #### How does validator stake increase? Our validator stake is consistently growing from royalties and compounding earnings. 50% of all royalties are contributed to the validator, and we are reinvesting 50% of all validator earnings. This is to consistently grows the payouts and creates more revenue for the project. As long as SOL exists, our validator will be growing and earning more and more. If you're expecting the value of SOL to increase, we're the perfect project for you. --- # 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/udder-chaos-validator/validator-funding.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.