> For the complete documentation index, see [llms.txt](https://docs.idle.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idle.finance/products/yield-tranches.md).
# Yield Tranches
Products > Yield Tranches
> *In the financial world, a tranche represents a product split that carries specific features like risk, yields, duration. They are often arranged together to create pools of diversified products or a basket of investments with similar characteristics (risk-return related)*.
Based on this concept, Idle launched its own tranches primitive: [Yield Tranches](https://idle.finance/#/dashboard/tranches).
Each tranched asset has its own yield source, with two risk-adjusted investment profiles (Senior and Junior).
{% hint style="success" %}
Taking the stETH Yield Tranche based on the Instadapp stETH pool as an example, stETH deposited into the Senior and Junior classes of that Instadapp-based strategy are aggregated into a single pool and then deployed into the Instadapp Lite market.
{% endhint %}
Tranches allow users to enjoy DeFi yields with **built-in protection on deposits** for Senior depositors or **boosted yield** for Junior ones.
{% hint style="info" %}
Users can decide the strategy according to their risk profile: they can deposit funds into two different tranches (**Senior** or **Junior**) in exchange for a token indicating their claim.
{% endhint %}
---
# 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.idle.finance/products/yield-tranches.md?ask=&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.
