> For the complete documentation index, see [llms.txt](https://fija.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fija.gitbook.io/docs/overview/fija-token/gas-fees.md). # Gas fees To ensure transparency regarding the costs associated with the fija ecosystem, it is important to distinguish between **user-initiated transactions** and the automated **management** of the underlying strategies. #### **User-Level Transactions** Standard blockchain interactions, such as **depositing** assets into a vault or **withdrawing** funds, incur network transaction costs known as "**gas fees**". These fees are paid directly from the user's connected wallet at the time of execution. #### **Strategy Management and Maintenance** A benefit of the vault infrastructure is the automation of yield-generating activities. To maintain the performance of a strategy, the following actions are handled by fija: * **Harvesting:** The process of collecting earned rewards from underlying DeFi protocols. * **Rebalancing:** Adjusting asset allocations within a strategy to maintain the target risk-reward profile or to optimize for changing market yields. * **Emergency Mode:** In case of emergency (e.g., unexpected activities like a depeg) or if a strategy is discontinued, the strategy is set to “emergency mode”. During it, all funds are retrieved from the DeFi protocols and remain stored in the strategy contract in the deposit currency. The holder of the fija token can then retrieve their funds directly through the vault. The gas fees associated with these background operations are **covered by fija**, ensuring that the day-to-day management of the strategy does not require manual intervention or additional costs from the individual investor. --- # 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://fija.gitbook.io/docs/overview/fija-token/gas-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.