> 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/wa-kuang-xi-tong/17targetpoolpower-yu-chang-qi-wa-kuang-zhou-qi.md).

# 17. Target Pool Power

CryptoStone 的 Target Pool Power 并不是以 STONX 总供应量为基准计算，而是以预计实际参与挖矿的有效质押量为基准计算。

$$
\text{Target Pool Power} = 40,000,000 \text{ Power per Pool}
$$

$$
\text{12 Pools Total Target Power} = 480,000,000 \text{ Power}
$$

这反映了一个假设：总供应量 1,200,000,000 STONX 中约 40% 可能长期参与挖矿生态。

若特定矿池 (j) 的总挖矿算力为 (P\_j)，Target Pool Power 为 (P\_j^\*)，则总矿池算力定义如下。

$$
P\_j = \sum P\_{i,j}
$$

$$
P\_j^\* = 40,000,000
$$

假设参与者每年增加 10,000 人，10 年后约有 100,000 人参与，平均 active stake 约为 4,800 STONX，则全部 Gem NFT 供应量中约 90% 被挖掘完成可能需要约 8 至 9 年。

由于减半结构的存在，90% 之后的挖矿速度将进一步放缓。因此，全部 Gem NFT 的 100% 完全被挖掘可能需要超过 12 年。

该时间推算并不是为了预测特定收益率或价格，而是为了说明 CryptoStone 并不是短期 NFT mint 事件，而是一个数字宝石在长期内逐步被挖掘出来的去中心化挖矿生态。


---

# 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/wa-kuang-xi-tong/17targetpoolpower-yu-chang-qi-wa-kuang-zhou-qi.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.