> For the complete documentation index, see [llms.txt](https://vitaprotocol.gitbook.io/vita/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vitaprotocol.gitbook.io/vita/vita-protocol/jing-ji-mo-xing/zhong-yao-feng-xian-ti-shi-yu-mian-ze-sheng-ming.md).

# 重要风险提示与免责声明

一、本文档为 VITA 去中心化协议经济模型的完整技术说明，独立完备地披露协议的代币参数、发行机制、网络权重、分红规则、等级权益与收益结算逻辑。本文档不构成任何投资建议、财务建议、法律建议或要约邀请，也不构成任何形式的收益承诺。

二、文中全部公式、参数与测算数值均为机制描述与理论推演。实际执行结果取决于链上真实状态——包括参与进度、市场价格、路由成交、储备余额、合约状态与风险参数——一切以链上数据为准。

三、文中出现的示例计算仅用于帮助理解公式含义，示例中的数字为假设值，与任何实际参与者、实际收益均无关联。

四、300% 单仓边界、加速系数、等级门槛、理论池规模等数值均为系统参数或参数测算值，均无固定收益、保本或确定回报的含义。数字资产参与存在包括本金全损在内的高风险，请根据自身风险承受能力谨慎决策。

五、VITA 协议为开源智能合约体系，无中心化运营主体，不设募集资金账户，合约不保留管理员后门。所有参与均为用户与智能合约之间的自主链上行为，参与者需自行遵守所在司法辖区的法律法规。


---

# 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://vitaprotocol.gitbook.io/vita/vita-protocol/jing-ji-mo-xing/zhong-yao-feng-xian-ti-shi-yu-mian-ze-sheng-ming.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.