> For the complete documentation index, see [llms.txt](https://whitepaper.mocossi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.mocossi.com/moconomics/token-distribution/lp-farming.md).

# LP Farming

Liquidity refers to how easily $MCOS can be converted into ADA. A low liquidity level means that the market is volatile, making it easier for a few individuals to manipulate prices. Therefore, we see the need to maintain a high liquidity rate that can produce several advantages (\*):

* High liquidity and high trading activities are more likely to facilitate an equilibrium price that is acceptable to most people.
* High liquidity ensures $MCOS’s price is stable enough to withstand large orders.
* High liquidity allows for greater accuracy in technical analysis since price and chart formation is more refined and precise in a liquid market.

In order to achieve the aforementioned liquidity rate, we will reserve 5% for LP farming rewards to incentivize our liquidity providers.

Source:

*(\*):* [*https://b2broker.com/news/cryptocurrency-liquidity-and-finding-the-best-liquidity-provider/*](https://b2broker.com/news/cryptocurrency-liquidity-and-finding-the-best-liquidity-provider/)


---

# 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://whitepaper.mocossi.com/moconomics/token-distribution/lp-farming.md?ask=<question>&goal=<endgoal>
```

`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.