> 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/ecosystem-and-future/46_conclusion.md).

# 46 Conclusion

CryptoStone is a protocol that implements the concept of digital gemstones on smart contracts.

It defines STONX as a mining resource and Gem NFT as the mined result, connecting the two through Proof of Mining, or PoM. Users deposit STONX into mining pools, accumulate Mining Power and PoM over time, and claim Gem NFTs once the required threshold is reached.

## Core Structure

| Item                 | Structure                                              |
| -------------------- | ------------------------------------------------------ |
| Mining Resource      | STONX                                                  |
| Initial Supply       | 1,200,000,000 STONX                                    |
| Mining Result        | CryptoStone Gem NFT                                    |
| Stone Types          | 12 birthstone-based pools                              |
| Attribute Generation | Weight, Color, Clarity, Cut, Rarity                    |
| Metadata             | HTTPS metadata API + watcher finalization + IPFS media |
| Rarity Standard      | Rarity Score + Probability Rarity Index                |

## Protocol Execution Structure

| Stage             | Description                                                                                       |
| ----------------- | ------------------------------------------------------------------------------------------------- |
| Participation     | Enter a mining pool from 1,000 STONX                                                              |
| Mining Power      | Calculated from staked amount, lock-up period, and pool parameters                                |
| PoM               | Mining work value accumulated over time                                                           |
| Claim             | Gem NFT claim after reaching the required PoM threshold                                           |
| Claim Burn        | 2 STONX x Scarcity Multiplier                                                                     |
| Maturity Burn     | Depreciation burn based on lock-up period                                                         |
| Randomness        | User entropy, recent multi-block entropy, `prevrandao`, claim state, and contract-specific values |
| Finalization      | Core attributes fixed at claim; media updated later by watcher                                    |
| Open Verification | Source code, audit reports, LP handling records, and probability tables                           |

CryptoStone's purpose is not to connect NFTs to real gemstone ownership. It is to reinterpret the structure of gemstones as a digital-native asset model: mining difficulty, scarcity, individual attributes, and collectible value.

This whitepaper does not claim that CryptoStone is a great discovery or a fundamentally new invention. It is a change of perspective and a new attempt. If gemstone attributes, scarcity, and collectibility are accepted by the market as a meaningful value system, CryptoStone may develop into a new category of digital gemstones.

CryptoStone should continue to evolve with transparent contracts, verifiable randomness, public supply data, secure metadata structure, and user-facing tools that make the system easier to understand and verify.


---

# 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/ecosystem-and-future/46_conclusion.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.
