# Yield Farms
SpiritSwap itself is simply a blockchain protocol which by design, does not offer any resources for utilization. As such, in order to provide users easy access to $SPIRIT and for the protocol to perform its core function as a DEX, users would need to be incentivized to play the role of liquidity providers and stake their digital asset pairs (e.g. FTM/SPIRIT) into the decentralized market making pools to provide the necessary liquidity for transactions. \
\
As compensation for opportunity costs, these liquidity providers which help to promote adoption of SpiritSwap by staking or including assets to selected liquidity pools (i.e. gauges) in exchange for SPIRIT-LP tokens would be rewarded with $SPIRIT (i.e. "farming" on SpiritSwap), according to each user's relative contribution after various adjustment and correction parameters.
In Figure 1 example of a liquidity provider depositing supported SPIRIT-LP tokens to the gauge contract.
In the aforementioned example, the gauge contract emits 10 $SPIRIT/block and the new farmer owns 100 out of 400 SPIRIT-LP tokens in the farming contract. Therefore, the liquidity provider will be earning 2.5 $SPIRIT tokens per block.
In the manner of true decentralization, the SpiritSwap farms operate on a "[gauge](/spiritswap-v3/v2-core-features/yield-farms/gauges.md) model". This offers inSPIRIT holders the opportunity to decide where weekly farming emissions are delegated from the beginning to end of each epoch.
---
# 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://docs.silverswap.io/spiritswap-v3/v2-core-features/yield-farms.md?ask=
```
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.