# Farming

'Farming' refers to the act of being rewarded for staking or providing liquidity in a token different from the asset(s) being staked or LPed. In Lixir's case, this token is the protocol's governance token [$LIX](https://lixir-finance.gitbook.io/lixir-doc/lixir-dao/lix-and-velix), and it's distributed to all liquidity providers. Note that this distribution is different from the $LIX distributions funded with the revenue from the [Performance Fee](https://lixir-finance.gitbook.io/lixir-doc/lixir-vaults/performance-fee). 

Lixir's farming model is in large part similar to Curve's farming model, and hence relies on a system of 'liquidity gauges' that tracks each liquidity provider's share in each of the Lixir Vaults. Each gauge is given a 'type weight' that will either increase or decrease that gauge's share in the total farming emission w\.r.t. the other gauges. By staking your LV tokens in the corresponding gauge, you're rewarded proportional to the amount of liquidity you're providing.

This is done in such a way that lower risk pairs that bring in significantly less revenue per dollar liquidity receive a lower $LIX farming emission than riskier pairs that bring in significantly more revenue per dollar liquidity. The type weights can at any point be changed through a [LIP](https://lixir-finance.gitbook.io/lixir-doc/lixir-dao/lixir-improvement-proposals) if the [DAO](https://lixir-finance.gitbook.io/lixir-doc/lixir-dao/introduction) wishes to do so.

{% content-ref url="farming/boost" %}
[boost](https://lixir-finance.gitbook.io/lixir-doc/farming/boost)
{% endcontent-ref %}


---

# Agent Instructions: 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:

```
GET https://lixir-finance.gitbook.io/lixir-doc/farming.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.