> For the complete documentation index, see [llms.txt](https://document.sunprotocol.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://document.sunprotocol.io/zhi-neng-he-yue/turbinefee-he-yue.md).

# Turbinefee合约

Turbine Fee 接收涡轮释放流程产生的 USDT 费用，并按照链上配置的比例把当前全部 USDT 余额分配给多个接收地址。该合约不记录个人待领取余额，也没有普通用户领取函数。

### 查询费用分配配置

推荐调用 `getFeeConfig()`，它一次返回两个等长数组：

* `recipients`：费用接收地址；
* `bips`：每个地址对应的分配比例。

比例分母由 `DENOMINATOR()` 返回，当前为 `10,000`。例如：

| `bips` |  比例 |
| -----: | --: |
| `5000` | 50% |
| `3000` | 30% |
| `2000` | 20% |

全部 `bips` 之和必须等于 `10,000`。也可以调用：

| 函数                     | 用途                   |
| ---------------------- | -------------------- |
| `feeConfigLength()`    | 接收地址数量               |
| `feeRecipients(index)` | 按从 0 开始的索引查询接收地址     |
| `feeBips(index)`       | 查询对应索引的分配比例          |
| `usdt()`               | 当前分配的 USDT 代币地址      |
| `dao()`                | DAO 地址               |
| `executors(account)`   | 地址是否为授权执行者           |
| `owner()`              | 当前管理地址；零地址通常表示所有权已放弃 |

### 执行分配

`executeUsdt()` 会读取合约的全部 USDT 余额，并按配置依次转给接收地址。该函数只允许 `executors(account)=true` 的地址调用，普通用户不能执行。


---

# 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://document.sunprotocol.io/zhi-neng-he-yue/turbinefee-he-yue.md?ask=<question>&goal=<user_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.