> 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-treasury.md).
# The Treasury
The Treasury serves as the backbone of our financial ecosystem, fortified by an array of computational models and strategies aimed at enhancing cash flow, liquidity, and overall asset management. This is particularly vital for ensuring long-term stability and profitability.
**Algorithms for Price Stability**
Key to our Treasury management are advanced algorithms that work cohesively to maintain the value and stability of our native token, LUCI. These algorithms automatically adjust supply parameters and collateral requirements based on current market conditions.
The Supply Adjustment Algorithm can be formulated as:
Where 𝛥S is the rate of supply adjustment.
\
**Protocol-Owned Treasury Model**
Central to the Treasury's operation is the Protocol-Owned Treasury Model, which comprises various sources of funding, including but not limited to liquidations, minting, and partnerships.
The funding sources can be mathematically represented as:
**Price Stabilization Mechanisms**
To ensure that the LUCI token maintains its value, we implement price stabilization mechanisms, especially during pivotal events like minting and burning. The Stabilization Ratio (SR) can be defined as:
An SR value close to 1 indicates that the token is well-collateralized and stable.
**Liquidations and Price Oracle**
A grace period of 72 hours is set for liquidations when accounts reach a critical threshold, often related to the Minimum Collateralization Ratio (MCR). An algorithm monitors these parameters, triggering automated notifications to users.
The Price Oracle continually adjusts the value *P* of assets and tokens based on market data.
**Policy for Burning and Minting**
The treasury periodically mints new tokens as a method of funding. Minting can also occur when a borrower defaults. Let *M* be the number of tokens minted, then:
Conversely, burning tokens occurs when a debtor clears their post-default debt. If *B* is the number of tokens to be burned, it could be calculated as:
**Liquidity as a Service and AMMs**
To optimize returns, a portion *X* treasury funds are allocated to liquidity providers and automated market makers (AMMs). This is often a fixed proportion α of the treasury's total available funds *T*.
**Flash Loans and Arbitrage Bot**
The treasury employs an arbitrage bot that uses flash loans to seize arbitrage opportunities across decentralized exchanges. The profitability Π of this strategy can be estimated as:
**Example**
Assume that the treasury has total available funds of 10,000 LUCI and wants to allocate 20% to liquidity providers and AMMs. In this case:
This treasury model, coupled with an array of algorithms and external partnerships, aims to dynamically respond to market conditions and user behavior, safeguarding the ecosystem's stability and financial health.
---
# 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-treasury.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.