> 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/01-yin-yan.md).

# 1. 引言

在现实世界中，宝石长期以来一直作为价值储存工具、装饰资产、收藏资产以及象征性资产发挥作用。宝石的价值并不单纯来自其物理存在本身。宝石的价值由开采难度、储量限制、加工精细度、等级差异、收藏需求以及文化象征性共同形成。

尤其是钻石、红宝石、蓝宝石、祖母绿等宝石，即使属于同一种宝石，也会根据每一颗宝石的个体属性而具有完全不同的价值。重量更大、颜色更优、净度更高、切工更精细的宝石，往往具有更高的稀缺性。这种结构表明，宝石并不是可替代的普通商品，而是其价值会根据个体属性发生变化的非同质化资产。

区块链技术为在数字环境中表达这种非同质化属性提供了基础。然而，现有 NFT 市场大多围绕图像、游戏道具、会员权益、外部内容的所有权或访问权发展。在这种情况下，NFT 的价值可能会依赖于外部图像、中央服务器、特定平台或运营主体。

CryptoStone 提出了一种不同的方向。CryptoStone 并不是用于证明外部图像或中央服务器内容的 NFT，而是一种数字宝石资产。在这一结构中，NFT 本身持有宝石的属性数据，并且这些属性本身表达稀缺性与收藏价值。

如果说比特币创造了数字黄金的叙事，莱特币曾被称为数字白银，那么 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/01-yin-yan.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.
