> For the complete documentation index, see [llms.txt](https://docs.bsc.lista.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bsc.lista.org/zh-cn/zhi-li/lista/lista-holder-benefits.md).

# LISTA 持有者福利

在 [LIP-024](https://snapshot.org/#/s:listavote.eth/proposal/0x1a15347f6b452049212bdf51ff1a46c0a7edf7ca8efe1004b32c15c2965f0f3b) 获得批准后，Lista 为 LISTA 持有者推出了多项福利。

首先是清算保护，这是一种机制，为 LISTA 持有者提供额外的 24 小时，以防止其头寸被清算。有关更多信息，请参阅我们的 [清算页面](https://docs.bsc.lista.org/introduction/lista-lending/liquidation#delayed-liquidation)。

其次是 LISTA 持有者提升计划，这是一项发放计划，为在选定的金库和/或市场中存款和/或借款的 LISTA 持有者提供额外的发放。

此发放采用分级系统：

| 等级 | 7 天平均 LISTA 余额 | 存款和借款上限（分别计算） | 等级权重 |
| -- | -------------- | ------------- | ---- |
| 1  | ≥ 10,000       | $500          | 1.0  |
| 2  | ≥ 50,000       | $1,500        | 1.2  |
| 3  | ≥ 200,000      | $3,000        | 1.5  |
| 4  | ≥ 1,000,000    | $4,000        | 2.0  |
| 5  | ≥ 5,000,000    | $5,000        | 2.5  |
| 6  | ≥ 15,000,000   | $5,000        | 3.0  |

每周，Lista 将选择若干金库和市场，并为每个金库和市场分配一定数量的 LISTA 发放。每天，将为每个符合条件的金库/市场拍摄快照，以计算每个地址的确切 LISTA 发放量，这将由其在每个金库/市场的总符合条件的存款和/或借款中的份额决定。

每个地址在每个金库/市场的发放份额通过其存款/借款和等级权重相乘计算得出。

一个例子：

金库 A 和 B 分别分配了 40,000 和 60,000 的 LISTA 发放。如果一个地址的 7 天平均 LISTA 余额为 60,000，并分别向两个金库存入 $1,000。那么：

作为二级持有者，其金库存款上限为 $1,500，每个金库的权重为 1.2。

总符合条件的存款为 $2,000，超过了上限。当这种情况发生时，符合发放的金额将计算为：

1500/2000 \* 1000 = 750 对于两个金库

将此数字乘以其权重，其在两个金库中的份额将均为 750 \* 1.2 = $900。

如果金库 A 的总符合条件的存款为 $90,000，而 B 为 $180,000，那么该地址将获得的 LISTA 发放总额为：

900/90000 \* 40000 + 900/180000 \* 60000 = 700

<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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bsc.lista.org/zh-cn/zhi-li/lista/lista-holder-benefits.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.