> 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/00-zhai-yao.md).

# 摘要

比特币虽然并未直接以现实世界中的黄金作为抵押，但它通过有限供应量、公开的挖矿规则、去中心化网络以及任何人都可以验证的交易结构，形成了“数字黄金”这一新的资产概念。比特币的本质意义在于，它证明了即使没有特定发行方或中央机构的信任背书，也可以仅通过代码与网络来实现数字资产的稀缺性与所有权。

开发者试图将这一哲学扩展到“宝石”这一资产概念。现实世界中的宝石具有有限的开采量，并且每一颗宝石都会根据重量、颜色、净度、切工等属性而具有不同的稀缺性与价值。即使是同一种宝石，只要个体属性不同，其价值也会发生变化。从这一点来看，宝石本质上具有非同质化特征，并且非常适合在数字环境中被表达为独立且唯一的资产。

CryptoStone 是一种去中心化数字宝石协议，旨在将宝石的可挖掘性、稀缺性、等级性和收藏性表达为链上数据，并使宝石 NFT 能够在没有中央服务器或运营方任意干预的情况下，于数字环境中被挖掘生成。每一颗宝石都以唯一的 Gem 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/00-zhai-yao.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.