> For the complete documentation index, see [llms.txt](https://lumi-finance.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://lumi-finance.gitbook.io/docs/legacy/overview-of-v2.md).
# Overview of V2
Lumi Finance emerges as a pivotal financial derivative within the Lumi ecosystem, aimed at aggregating sustainable wealth accumulation.
LUA stands as the core strategic token, minting LUAUSD through its floor price collateral mechanism, LUAUSD is the stable coin acting as the ecosystem's currency.
* LUA features a dual pricing mechanism, with a issuing price(we called it market price in V1) and a floor price, where the latter only ascends based on algorithms and calculus.
* The LUA dual market system, alongside price mitigation and TWAMM balance mechanisms, harmonizes stability with volatility, offering the market a broader spectrum of strategic options.
* Staking LUA mints LUAUSD, concurrently yielding profits in LUAB and LUAG.
* LUAUSD liquidity mining.
* Protocol buy-back and burn LUA mechanic, similar to EIP-1559.
* AMO Protocol for algorithmically keeping LUAUSD return to the peg.
* Stablecoin(LUAUSD) has continuous high-quality use cases in the Lumi ecosystem, such as [Lumiterra](https://twitter.com/LumiterraGame).
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://lumi-finance.gitbook.io/docs/legacy/overview-of-v2.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
