> 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.md). # fija Token For every deposit, the vault **mints** its own **fija Token** and issues them to the address from which the deposit was made or an address defined in the deposit function. Each vault has its own tokens. The token **increases in value over time** as the strategy contract harvests fees and issues the yields back into the strategy. The value of the strategy token held by the vault will therefore increase, and in return, the value of the token will increase. Hence, a customer **redeeming a token** after a certain time will receive **more deposit tokens** than initially deposited. A token can be sent back to the vault anytime. When sent back the vault burns the token and transfers all underlying assets to the wallet address the token was sent from or the address defined in the withdraw function. A fija token can be directly associated with the underlying strategy token and, consequently, the assets held by the strategy contract. --- # 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.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.