> 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/sheng-tai-xi-tong-yu-wei-lai/45-xiang-mu-di-yi-yi.md).

# 45. 项目意义

CryptoStone 的意义可以概括为三点。

第一，CryptoStone 提出 NFT 可以脱离外部内容所有权，成为属性型资产本身。现有 NFT 很多依赖图像或平台，而 CryptoStone 试图通过将宝石属性直接保存为链上数据，强化 NFT 本身的资产性。

第二，CryptoStone 将宝石的稀缺性与等级结构转移到数字环境中。现实中的宝石会根据重量、颜色、净度和切工产生不同价值。CryptoStone 通过概率表、挖矿难度、减半和供应量限制来实现这一点。

第三，CryptoStone 将去中心化挖矿的概念扩展到比特币之后的新资产领域。如果说比特币将黄金的稀缺性数字化，莱特币形成了数字白银的叙事，那么 CryptoStone 则将宝石的稀缺性与收藏性数字化。

此外，CryptoStone 提出了一种生态结构：已被挖掘的 Gem NFT 并不只是持有资产，还可以扩展至精炼、交易、排名、收藏活动等。这表明 NFT 的价值不应局限于图像或稀有度，而可以扩展至使用历史、精炼世代、供应压缩历史和生态实用性等方面。

CryptoStone 并不声称替代现实宝石。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/sheng-tai-xi-tong-yu-wei-lai/45-xiang-mu-di-yi-yi.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.