# In-App Use Cases ### **Fee Settlement** Players may use a wide array of ERC-20 tokens to [open positions](/whitepaper/core-mechanics.md), pay [exit fees](/whitepaper/fees.md#exit-fees), and [tip](/whitepaper/fees.md#balancer-fees) Balancers. And Directors may use whatever token they like to pay for [advertising](/whitepaper/fees.md#advertising-fees). However, all exit fees, advertising fees, and tips must ultimately be paid using $MIMIC. Accordingly, when a player does not pay fees with $MIMIC, their payment token will be immediately converted to a *MARKET BUY* order for $MIMIC tokens across supported exchanges and they will be responsible for slippage. Therefore every action in the protocol represents demand for $MIMIC. For the sake of clarity, only fees—not deposits locked in the smart contract—will be converted to $MIMIC. ### **Feature Gates** Players who use $MIMIC to open positions, or auto-swap to $MIMIC within our UI, will have access to advanced features that will not be available to players who use other tokens. For example, [automations](/whitepaper/advanced-features/automations.md) will all be restricted to players who mint Mimes using $MIMIC. Community rewards will also be restricted to players who use $MIMIC to open their positions. This will serve to increase demand for the token while also effectively removing $MIMIC tokens from circulation when they are locked in positions. --- # Agent Instructions: 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: ``` GET https://docs.mimicry.org/whitepaper/tokenomics/in-app-use-cases.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.