> 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/introduction/02_simplest_way_to_understand_cryptostone.md).

# 02 CryptoStone Overview

CryptoStone is an on-chain protocol for mining digital gemstones. A user deposits STONX into the gemstone mining pool of their choice, and once enough Proof of Mining, or PoM, has accumulated over time, the user can claim a Gem NFT. The mined NFT is not a simple image, but a unique digital gemstone containing recorded attributes such as Stone Type, weight, color, clarity, cut, rarity score, and mining time.

Users can choose from 12 stone pools, including diamond, ruby, sapphire, and emerald. Each STONX has a different supply, mining interval, and halving structure. As mining progresses, the remaining supply decreases and the scarcity multiplier increases.

The core experience of CryptoStone is simple:

* STONX is deposited into a digital mine.
* Over time, Mining Power accumulates as Proof of Mining, PoM.
* When the required PoM threshold is reached, a Gem NFT can be claimed.
* Which gemstone appears is determined by publicly disclosed probabilities and verifiable randomness.

In other words, CryptoStone aims to be a “mined digital gemstone,” not a “purchased NFT.” Users do not simply buy an image. They mine their own digital gemstone within publicly disclosed rules and fixed probability structures.

After mining, Gem NFTs can be connected to various ecosystem utility modules, such as holding, exploration, trading, and refinement. However, these expansion functions do not replace the core mining structure. They are optional ecosystem modules designed to expand the utility and collectibility of mined digital gemstones.


---

# 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/introduction/02_simplest_way_to_understand_cryptostone.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.