> For the complete documentation index, see [llms.txt](https://docs.tetu.io/tetu-io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tetu.io/tetu-io/tetu-v1/yield-farm/strategies/simple-rewards-farming.md).

# Simple rewards farming

The most classic design of Yield Farming. If some strategy provides claimable rewards for a token, Tetu developers can create a strategy for automating this process.

When depositing in the vaults, the strategies will claim the rewards and sell them for the underlying tokens. This process will increase the underlying assets of each user participating in the vault over time, this is called [autocompound](/tetu-io/tetu-v1/yield-farm/vault-shares.md).

There are vaults that work according to PS ratio. The PS ratio determines the rate of rewards that will be distributed between the auto compound of the underlying vault and the then divided by the Profit Destination ratio to xTETU Profit Share, Protocol Owned Liquidity, and the Investment fund.

The [PS ratio](https://docs.tetu.io/tetu-io/profit-sharing-pool#ps-ratio) has been in existence since the inception of Tetu, the purpose of the PS ratio is to keep yield farming vaults attractive and it is adjusted through DAO voting. The dxTETU holders decide whether it is changed.


---

# 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://docs.tetu.io/tetu-io/tetu-v1/yield-farm/strategies/simple-rewards-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.