> 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/mining-system/14_calculation_of_the_initial_stone_supply.md).

# 14 STONX Initial Supply

CryptoStone does not issue 12 separate tokens for each Stone Type. It uses one STONX Token.

The initial total supply is set as follows.

* STONX Initial Total Supply = 1,200,000,000 STONX
* Additional Mint = None

The reason for setting STONX at 1,200,000,000 is not simply to expand the number of tokens. CryptoStone aims for a structure in which more than 100,000 users can participate in mining pools at various scales. For this, a unit structure is needed that allows small participants, medium-scale participants, and high-Mining Power participants to participate naturally.

With a structure of 1,200,000,000 STONX, even assuming more than 100,000 participants, a natural participation UX in units of several thousand STONX can be designed. This lowers the entry barrier for small participants, provides a practical mining participation unit for mid-scale participants, and enables long-term mining strategies for high-Mining Power participants.

Therefore, the issuance of 1.2 billion tokens should be interpreted not as an indiscriminate increase in supply, but as a unit design to accommodate a broader user base and the Proof of Mining structure.

Expected Active Mining Ratio = approximately 30% \~ 40%

$$
1,200,000,000 \ \text{STONX} \times 40% = 480,000,000 \ \text{Active Mining STONX}
$$

Based on 100,000 participants, the average active stake is as follows.

$$
480,000,000 \ \text{STONX} \div 100,000 \ \text{users} = 4,800 \ \text{STONX per user}
$$

In other words, the 1,200,000,000 STONX structure is designed to accommodate a large participant base while allowing small participants to access the mining ecosystem.


---

# 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/mining-system/14_calculation_of_the_initial_stone_supply.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.