> 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/jie-shao/04-xie-yi-xin-ren-yuan-ze.md).

# 4. 协议信任原则

CryptoStone 追求一种不依赖特定创始人或运营方信任的结构。本协议的信任基础并不是创始人的身份，而是公开代码、固定发行量、不可变更的概率表、No Admin Mint 结构、可验证随机性，以及任何人都可以确认的链上数据。

运营方不得向特定用户任意分配稀有 NFT，不得更改各宝石供应量，也不得操纵挖矿概率。CryptoStone 的目的，是建立一种由协议规则而非人的权威形成数字宝石稀缺性的结构。

| 信任原则                   | 说明                                             |
| ---------------------- | ---------------------------------------------- |
| Fixed Supply           | STONX 总发行量与各宝石 NFT 最大发行量预先固定                   |
| Open Market Allocation | STONX 通过 DEX、Direct Sale、战略配分和上市流动性储备形成公开市场型分配 |
| No Admin Mint          | 运营方不得任意发行 Gem NFT                              |
| Immutable Probability  | 宝石属性概率表公开，并在 finalization 后不可更改                |
| Verifiable Randomness  | 宝石属性必须由可验证随机结构决定                               |
| On-chain Attributes    | Gem NFT 核心属性应记录为链上或公开可验证数据                     |
| Transparent Pools      | 各宝石矿池的已挖数量、剩余量、难度应公开可确认                        |
| Open Verification      | 任何人都应能够验证合约与挖矿规则                               |

这一结构表明，CryptoStone 是通过公开规则与可验证代码运行的去中心化数字宝石协议，而不是依赖特定运营方裁量的系统。


---

# 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/jie-shao/04-xie-yi-xin-ren-yuan-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.