> For the complete documentation index, see [llms.txt](https://docs.ston.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ston.fi/developer-section/dex/farm.md).

# Farm

STON.fi yield farming guide - stake LP tokens to earn additional rewards on top of trading fees

Yield farming functionality for STON.fi liquidity providers.

## Overview

STON.fi farming allows LP token holders to earn additional rewards by staking their tokens in farming pools. This provides an extra incentive for liquidity providers beyond trading fees.

## How It Works

1. **Provide Liquidity**: Add tokens to a DEX pool to receive LP tokens
2. **Stake LP Tokens**: Deposit LP tokens into a farming pool
3. **Earn Rewards**: Accumulate farming rewards over time
4. **Claim & Unstake**: Harvest rewards and withdraw LP tokens when desired

## Key Features

* Multiple farming pools with different reward rates
* Flexible staking and unstaking
* Real-time reward accumulation
* NFT-based position tracking

## SDK Integration

Farming functionality is available through the STON.fi SDK:

```typescript
import { FARM } from '@ston-fi/sdk';
```

See the operation guides below for contract setup, transaction preparation, and execution.

## Available Operations

* [Stake in Farm](/developer-section/dex/farm/stake.md)
* [Claim Rewards](/developer-section/dex/farm/claim.md)
* [Unstake from Farm](/developer-section/dex/farm/unstake.md)
* [Destroy Farm NFT](/developer-section/dex/farm/destroy.md)


---

# 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://docs.ston.fi/developer-section/dex/farm.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.
