> 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.md).

# Turbo and Stable

Built on top of our classic QUEEN-BISHOP-ROOK structure, the Turbo & Stable series is customized for points earning and rewards. Get the most out of your points-earning assets with Turbo & Stable, even if you are just here for fixed-interest earning.

Specifically:

* [**QUEEN**](/faq/turbo-and-stable/queen.md): The QUEEN token swaps 1:1 with the underlying assets from day one till the fund reaches maturity. The ratio will always stay at 1:1.
* [**Turbo**](/faq/turbo-and-stable/turbo.md): An enhanced version of ROOK, customized for maximum points earning. Leverage the leverage for points earnings at a cost.
* [**Stable**](/faq/turbo-and-stable/stable.md): Enhanced BISHOP. Fixed and competitive interest earning with no lock-up period.

***

Tranchess Turbo and Stable structure for points-earning are now on Scroll and BNB Chain.

### Live Funds (click on the asset names for a full user guide of the fund):

<table><thead><tr><th width="170">Underlying Asset</th><th>Contract Deployment</th><th>Starting Date</th><th>Maturity Date</th></tr></thead><tbody><tr><td><a href="https://tranchess.notion.site/Tranchess-uniBTC-brBTC-Fund-IV-User-Guide-29ace8b3d9e380728527f6c2c015390e">brBTC (Fund 4)</a></td><td>Oct. 24, 2025</td><td>Oct. 28, 2025</td><td>January 27, 2026</td></tr><tr><td><a href="https://tranchess.notion.site/Tranchess-uniBTC-brBTC-Fund-IV-User-Guide-29ace8b3d9e380728527f6c2c015390e">uniBTC (Fund 4)</a></td><td>Oct. 24, 2025</td><td>Oct. 28, 2025</td><td>January 27, 2026</td></tr></tbody></table>

{% hint style="info" %}
Use the Contract Deployment dates to calculate fair values. More details can be found [here](/faq/turbo-and-stable/upon-maturity.md).
{% endhint %}

### Matured Funds:

| Underlying Assets    | Maturity Date      |
| -------------------- | ------------------ |
| asBNB (Fund 2)       | December 15, 2025  |
| brBTC (Fund 3)       | September 25, 2025 |
| uniBTC (Fund 3)      | September 25, 2025 |
| brBTC (Fund 2)       | June 26, 2025      |
| uniBTC (Fund 2)      | June 26, 2025      |
| asBNB                | June 6, 2025       |
| brBTC                | March 31, 2025     |
| uniBTC               | March 31, 2025     |
| slisBNB (Fund 2)     | March 27,2025      |
| SolvBTC.BBN (Fund 2) | March 5, 2025      |
| STONE (Fund 2)       | February 13,2025   |
| weETH                | December 15, 2024  |
| SolvBTC.BBN          | December 7, 2024   |
| STONE                | October 8, 2024    |
| slisBNB              | September 30,2024  |
| SolvBTC              | September 10, 2024 |

***

## Fees and costs

Creation/Redemption: 0

Split/Merge: 0

Trading fee: 0.05%

Protocol fee: [Depends on each Fund.  ](/faq/turbo-and-stable/turbo.md#points-rebate)


---

# 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.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.