> For the complete documentation index, see [llms.txt](https://docs.vibeswap.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vibeswap.net/economics/fee-distribution.md). # Fee Distribution Vibeswap fees are collected in zkLTC. The long-term direction is to use fees to support the arcade economy instead of treating them only as revenue. ## Planned Distribution Areas * Reward pools for future seasons. * Treasury reserves. * Swap liquidity support. * Product and infrastructure costs. * Ecosystem campaigns and partnerships. ## Reward Pool Direction Each competitive season should start with a predefined zkLTC reward pool. During the season, a portion of game fees can gradually support future rewards. This approach keeps season rewards predictable while allowing game activity to help sustain the next reward cycles. ## Current Status The exact fee split is not final. It should be finalized before the first competitive season with zkLTC rewards. --- # 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.vibeswap.net/economics/fee-distribution.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.