> For the complete documentation index, see [llms.txt](https://help.wavesfunnynode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.wavesfunnynode.com/documentation/zh/prefs/xian-zhi-yu-gui-ze.md).

# 限制与规则

## 限制、规则与成熟期

为了确保节点健康且可持续，WFN V2 遵循一套严格的规则和运营限制。理解这些内容将帮助你管理对奖励分配的预期

### 1. 1000 区块成熟规则

**这是什么？** 一笔租约只有在活跃满以下时长后才被视为“成熟”并有资格获得奖励： **1000 个区块** （约 17 小时）

**为什么？** 此规则可防止“奖励跳跃”（即用户在区块被挖出前才租入，并在之后立即取消租入）。它确保只有为节点安全作出贡献的长期质押者才能获得奖励

**连续租约：** 如果你在同一个区块中取消旧租约并开启新租约，系统足够智能，会将其识别为“连续租约”。你不会失去成熟度，并且会继续根据旧租约和新租约中的较小金额来获得奖励。

### 2. 支付间隔与限制

设置偏好时，你必须保持在以下范围内：

* **最小间隔：** 
  * *例如：设置为 100 个区块，意味着你大约每 1.7 小时获得一次奖励*
* **最大间隔：** 
  * *例如：设置为 10,000 个区块，意味着你大约每 7 天获得一次奖励。*
* **默认：** 未设置间隔的用户按周支付

### 3. 节点费用（佣金）

节点费用在……之前扣除 *在……之前* 奖励按比例分配。

* **WAVES：** 10%
* **LP 代币：** 10%
* **UNIT 代币：** 10%

{% hint style="info" %}
这些是标准费用。它们可能会根据特定节点配置或促销活动而有所不同
{% endhint %}

### 4. 最低支付额

为节省网络费用，系统设有最低支付额：

* **WAVES：** 900000 wavelet（0.009 WAVES）
* **代币兑换：** 如果你的奖励太小而无法执行兑换，它将被保留，直到你的余额增长，或以原始代币支付

### 5. 安全与双因素认证

WFN V2 中的每笔支付交易都由 **多重签名（2FA）** 流程保障。每笔支付都必须由两个不同的管理员密钥签署确认，确保你的奖励始终安全并正确处理


---

# 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://help.wavesfunnynode.com/documentation/zh/prefs/xian-zhi-yu-gui-ze.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.