> For the complete documentation index, see [llms.txt](https://leodex.inleo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://leodex.inleo.io/general/fees.md). # Fees ### Affiliate Fees Our affiliate fee for Thorchain, Maya Protocol, ChainFlip, Rango and Relay is 0.45%. One of the lowest in the industry. ### What Happens to Fee Revenue? 100% of Affiliate Fee Revenue is captured by the sLEO staking contract on Arbitrum as USDC (Arbitrum) and is claimable by every [LEO staker](/general/leo-staking.md) on a stake-weighted basis. ### Bridging Fees When LEO is moved across blockchains, a small bridging fee is incurred. This fee is dynamic (usually 1% - 5%) based on market pricing. 100% of bridging fee revenue is burned which makes LEO deflationary each time someone bridges it to another chain. ### Referral Rewards When a user utilizes our referral program to create a unique ID and share that code with swappers, they get a share of our 0.45% affiliate fee. * 0.28% to LeoDex * 0.12% to the user * 0.05% discount to the swapper --- # 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://leodex.inleo.io/general/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.