> 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/bai-pi-shu/zhong-yao-feng-xian-ti-shi-yu-mian-ze-sheng-ming.md).

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

一、本白皮书仅为 VITA 去中心化协议的机制说明与技术文档，用于阐述协议的设计哲学、身份体系、网络结构与治理方向，不构成任何投资建议、财务建议、法律建议、税务建议或要约邀请，也不构成任何形式的收益承诺。

二、数字资产、智能合约交互与链上参与均具有高风险，可能因价格波动、合约漏洞、流动性不足、监管变化或其他不可预见因素导致本金部分或全部损失。所有参与者应根据自身风险承受能力谨慎决策，并自行承担全部后果。

三、VITA 协议为开源智能合约体系，部署于币安链（BNB Chain），所有规则链上透明可查、不可篡改。项目无单一中心化运营主体，不设募集资金账户，所有交互均为用户与智能合约之间的自主链上行为。合约内部未保留任何管理员后门或人工干预权限，确保链上规则执行的绝对确定性。

四、白皮书所述审计、储备注入、合作关系、权限移交与地址披露，均以最终部署代码、链上记录和正式公开文件为准。任何尚未完成部署、审计或验证的功能，仅以规划、预留或研究方向的形式表述。

五、全球各司法辖区对数字资产的监管规定存在差异。所有参与者必须严格遵守所在国家及地区的相关法律法规，若本白皮书内容与当地法规冲突，应立即停止参与。本白皮书未经过任何国家监管机构的审核或批准。

六、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/bai-pi-shu/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.
