> For the complete documentation index, see [llms.txt](https://docs.arafi.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arafi.app/tokenomics/protocol-fees.md). # Protocol Fees Protocol fees stand as one of the most critical components in accruing value for our vlARA lockers and ARA holders. They not only contribute to the overall financial health of the ecosystem but also form an integral part of our value proposition. Rather than merely serving as a revenue source, the majority of the fees generated are strategically reinvested into our protocol. This reinvestment strengthens the stability and resilience of our system, while simultaneously rewarding the various ecosystem participants. It's this efficient cycle of reinvestment and reward that propels our platform forward, reinforcing our commitment to create a symbiotic environment where both the protocol and its participants benefit and thrive. --- # 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.arafi.app/tokenomics/protocol-fees.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.