> For the complete documentation index, see [llms.txt](https://rubixdao.gitbook.io/rubixdao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rubixdao.gitbook.io/rubixdao/revenue-streams.md). # Revenue Streams **Stability Fees:** The Stability fee is paid by every Vault owner when debt is paid down and/or completely paid off. It is an annual percentage yield that is calculated on top of the existing Vault debt. Stability fees must be paid in TAD only. This is currently set at 2% (subject to Rubix Governance). **Deposit Fees:** At this time there are no deposit fees other than what the typical user gas costs (subject to Rubix Governance). **Rubix Protocol Auctions:** See ‘Liquidations’ section. **How Protocol revenue is distributed:** Revenue is distributed to Rubix stakers at 2% annual return with the rest of the generated revenue going back to the treasury fund. **How users benefit from Protocol revenue:** At this time, the primary benefit to RBX holders will be selling generated revenue and 'buying and burning' RBX. This will primarily be facilitated through Rubix Governance votes. However, an automated smart contract may be developed at a later stage by the DAO community. **How Protocol revenue is tracked:** We assume that a dashboard functionality will be developed by the DAO community at a later stage. --- # 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://rubixdao.gitbook.io/rubixdao/revenue-streams.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.