> 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/wa-kuang-xi-tong/18-shu-zhi-yu-can-shu-de-jie-shi.md).

# 18. 参数解释

本白皮书所提出的各宝石供应量、基础挖矿周期、挖矿算力公式、PoM 阈值、减半倍率、Weight·Color·Clarity·Cut 概率表以及 Rarity Score 公式，并不是对现实宝石生态的完美复制或绝对标准。

这些数值是为了以下目的而设计的初始基准参数。

| 目的      | 说明                  |
| ------- | ------------------- |
| 表达数字稀缺性 | 在链上环境中表达宝石稀缺性       |
| 实现挖矿难度  | 通过智能合约实现挖矿难度和供应限制   |
| 区分相对稀缺性 | 设计可比较的各宝石稀缺性差异      |
| 区分收藏价值  | 通过稀有度和等级结构提升收藏市场理解度 |
| 长期供应控制  | 通过减半和难度上升管理供应速度     |
| 参与扩展性   | 同时容纳小额参与者和大规模参与者    |

因此，本白皮书中的数值并不能被视为完全反映现实宝石市场中的所有价格形成因素、鉴定标准、流通结构、供需关系、文化价值、实物保管成本以及鉴定机构评估模型。

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/wa-kuang-xi-tong/18-shu-zhi-yu-can-shu-de-jie-shi.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.