> For the complete documentation index, see [llms.txt](https://docs.skydrome.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.skydrome.finance/features/tokenomics-and-emissions/protocol-revenue.md). # Protocol Revenue An important aspect of any initiative is ensuring its financial sustainability. Skydrome has invested considerable thought into guaranteeing that both the team and the community have a steady revenue stream. **Swap Fees** Trading fees generated from liquidity pools that don't have associated gauges will be directed to the tank. Once a gauge is established for a specific pool, this process is deactivated. The accumulated fees will be utilized at the team's discretion for varied purposes, such as $SKY buybacks and burns, incentivizing core pools, covering development expenses, and more. **Protocol Owned Liquidity** Through the inaugural liquidity-providing $SKY pool, Skydrome doesn't accrue any revenue. There will be no emissions from this pool, and upon fulfilling its intended purpose, the tokens will be terminated. **Team Emissions** 4% of all emissions are channeled to the treasury. These $SKY tokens will serve multiple purposes as deemed appropriate by the team. This includes activities like incentivizing primary pools, financing developments, and bolstering team member voting influence, among others. **Team Voting** Every team member possesses their distinct $veSKY, empowering them to cast votes based on their preferences. This mechanism allows them to potentially carve out their personalized revenue source. --- # 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.skydrome.finance/features/tokenomics-and-emissions/protocol-revenue.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.