> For the complete documentation index, see [llms.txt](https://docs.tranchess.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tranchess.com/faq/turbo-and-stable/staked-eth-yield-enhancement.md).

# Staked ETH Yield Enhancement

> #### :information\_source: This is the first fund utilizing our Turbo & Stable structure. However, it's not a points-leverage trading fund, thus we put it separately for better differentiation from the current standard Turbo & Stable structure. 

As a liquid staking protocol on Ethereum, Tranchess is always looking for ways to utilize its structured design to benefit the ETH liquid staking community further. V3 is the first step of our LSDFi narrative. 

Tranchess V3 aims to optimize the yield of staked ETH tokens, starting with stETH/wstETH. In 2024, we will continue to bring in more interesting LSDFi product designs to cater to the needs of the liquid staking token holders. Join us as we embark on this new and exciting journey.  


---

# 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.tranchess.com/faq/turbo-and-stable/staked-eth-yield-enhancement.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.