> For the complete documentation index, see [llms.txt](https://docs.carbondefi.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.carbondefi.xyz/carbon-defi/introducing-carbon-defi/fees-and-payments.md). # Fees & Payments All fees collected by Carbon DeFi are protocol-owned, and their allocation is decided solely through DAO governance. ### Trader fees These fees are paid by the users that trade with existing strategies and orders on Carbon DeFi. The trading fee is defined as a percentage from the trade amount. The current trading fee percentage can be verified via smart contract, as described on the [tradingFeePPM](/contracts-and-functions/carboncontroller-functions/read-functions/tradingfeeppm.md) page. ### Dex aggregator swap fees On the app interface, for some chains, we introduce a dex aggregator solution (inhouse or managed by 3rd party) which will include a specific 0.25% trading fee as part of the transaction. --- # 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.carbondefi.xyz/carbon-defi/introducing-carbon-defi/fees-and-payments.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.