> 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/17_target_pool_power_and_long_term_mining_period.md). # 17 Target Pool Power CryptoStone’s Target Pool Power is calculated based not on the total STONX supply, but on the effective staking amount expected to actually participate in mining. * Target Pool Power = 40,000,000 Power per Pool * 12 Pools Total Target Power = 480,000,000 Power This reflects the assumption that approximately 40% of the total STONX supply of 1,200,000,000 may participate in the mining ecosystem over the long term. If the total Mining Power of a specific pool (j) is (P\_j), and its Target Pool Power is (P\_j^\*), the total pool power is defined as follows. $$ P\_j = \Sigma P\_{i,j} $$ $$ P\_j^\* = 40,000,000 $$ Assuming that participants increase by 10,000 each year, approximately 100,000 users participate after 10 years, and the average active stake is around 4,800 STONX, it may take approximately 8 to 9 years for about 90% of the total Gem NFT supply to be mined. Due to the halving structure, the mining speed after the 90% stage becomes even slower. Therefore, it may take more than 12 years for 100% of the total Gem NFT supply to be fully mined. This period estimate is not intended to predict any specific return rate or price. It is a model to explain that CryptoStone aims to be a decentralized mining ecosystem in which digital gemstones are gradually mined over a long period of time, rather than a short-term NFT minting event. --- # 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/17_target_pool_power_and_long_term_mining_period.md?ask=&goal= ``` `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.