> For the complete documentation index, see [llms.txt](https://doc.cryptostone.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.cryptostone.org/crypto-stone/crypto-stone-wp-cn/xie-yi-jia-gou/39-an-quan-ying-dui-yu-qu-zhong-xin-hua-zhi-jian-de-ping-heng.md).

# 39. 安全与去中心化

CryptoStone 将 No Admin Mint 和 No Central Server 作为核心原则。不过，在初期开发与部署阶段，为了安全审计、测试和漏洞应对，可能需要有限的管理结构。

| 阶段         | 管理结构                                                 |
| ---------- | ---------------------------------------------------- |
| 测试网与审计阶段   | 可存在有限管理权限                                            |
| 正式部署前      | 参数验证与安全检查                                            |
| 正式上线后      | 移除核心发行、供应和概率更改权限                                     |
| finalize 后 | No Admin Mint、No Supply Change、No Probability Change |

如果存在紧急暂停功能，该功能只能作为防止安全事故的有限功能使用，而不得用于操纵发行结果或更改供应量。同时，紧急功能应通过时间锁或多签等公开可验证方式进行限制，不能成为运营方任意更改稀有度或发行量的手段。

CryptoStone 的主要合约由代币合约、Gem NFT 合约、Mining Pool Template、Pool Factory 和随机生成结构组成。这些合约在部署前后都最好经过安全审计，审计结果和主要漏洞应对记录也应公开。

应公开的核心验证要素如下。

| 验证项目                         | 说明              |
| ---------------------------- | --------------- |
| Contract Source Verification | 已部署合约源码公开与验证    |
| Audit Report                 | 主要合约与随机结构的审计报告  |
| Admin Function List          | 管理员函数是否存在及其移除计划 |
| Finalize Event               | 核心参数固定时间与事件记录   |
| LP Lock / Burn Proof         | 初始流动性相关 LP 处理记录 |
| Probability Table Hash       | 确认概率表与部署前公开值一致  |
| Metadata Freeze              | 发行后核心属性是否不可更改   |

该结构旨在在实务安全应对与去中心化资产性之间取得平衡。


---

# 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://doc.cryptostone.org/crypto-stone/crypto-stone-wp-cn/xie-yi-jia-gou/39-an-quan-ying-dui-yu-qu-zhong-xin-hua-zhi-jian-de-ping-heng.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.