> For the complete documentation index, see [llms.txt](https://docs.growthdefi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.growthdefi.com/wheat/wheat-vaults-v2.md).

# 4.1 WHEAT Vaults (stkTokens V2)

*Wheat Contract Address (BSC): 0x3ab63309f85df5d4c3351ff8eacb87980e05da4e*

Wheat is the incentive token of the ecosystem, including Growth DeFi’s yield optimizer of the same name. Buyback and burn mechanics are implemented through performance fees on stkTokens in combination with fee collectors. This will eventually make WHEAT deflationary over time.<br>

stkTokens are tokenized yield farming positions in different protocols such as ApeSwap and PancakeSwap.

The standard performance fee for stkTokens is 5% of the token it is yield farming. In the case of ApeSwap and PancakeSwap strategies, these fees go to the respective fee collectors.

There are no deposit or withdrawal fees in stkTokens V2. They are used as ilks for MOR, and having deposit/withdrawal fees would only add friction.

stkTokens have been audited by ConsenSys Diligence, you can [*read the audit report  here*](https://consensys.net/diligence/audits/2021/06/growthdefi-wheat/)*.*<br>


---

# 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.growthdefi.com/wheat/wheat-vaults-v2.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.
