> 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/migration-from-v1-to-v2.md).

# Migration from V1 to V2

Before the official launch of V2, all functions of V1 will remain unchanged. 

After the official launch of V2, some functions of V1 will be restricted, including the following:

1. Unable to mint/burn LUA in V1 LUA AMM
   * You can mint in V2 LUA minting protocol or swap in Uniswap
2. Unable to obtain new LUAB rewards in V1
   * You can get it by minting LUA, staking LUA or providing LUAUSD liquidity
3. Unable to add LUAUSD liquidity in V1

Other functions of V1 will operate normally, such as unstake LUA, and claim existing rewards.


---

# 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/migration-from-v1-to-v2.md?ask=<question>&goal=<user_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.