> For the complete documentation index, see [llms.txt](https://lucia-protocol.gitbook.io/lucia-protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lucia-protocol.gitbook.io/lucia-protocol/the-luci-token.md). # The LUCI Token LUCI is a stablecoin anchored to a treasury reserve, designed to simplify the user experience in the digital asset space. It allows individuals to mint LUCI tokens by pledging established stable assets—such as USDT, USDC, and DAI—into a dedicated treasury. This process not only enables the issuance of LUCI tokens but also offers liquidity for users. Importantly, at any point, users can opt to redeem their original assets by repaying the LUCI tokens they have minted. Built on the Ethereum blockchain, LUCI offers robust security and can be stored across an array of digital asset wallets. It is also supported by various platforms that accommodate Ethereum-based tokens. Once minted or acquired, LUCI behaves akin to other cryptocurrencies, meaning it can be transferred, spent on goods and services, or used within the Lucia Protocol's ecosystem for revenue generation through stLCI, the staked iteration of LUCI. To ensure utmost transparency, every LUCI transaction is recorded and publicly verifiable via the Ethereum blockchain. Each LUCI token in circulation is fully backed by a basket of collateral assets held in the treasury. This mechanism ensures that the overall value of the collateral always exceeds the total circulating LUCI supply. Currently, LUCI is supported by a diverse portfolio of under-collateralized digital assets, including but not limited to USDT, USDC, and DAI. We are also actively exploring avenues to incorporate additional stable assets into the treasury, thereby broadening the backing of LUCI and enhancing its resilience and stability. --- # 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://lucia-protocol.gitbook.io/lucia-protocol/the-luci-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.