> 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/22-suo-xu-pom-yu-zhi.md).

# 22. 所需 PoM 阈值

挖出 1 个宝石所需的 PoM 阈值，由 Protocol Reference Power、各宝石基础挖矿周期、矿池难度和稀缺性倍率决定。

若宝石 (j) 的基础挖矿周期为 (T\_j)、Protocol Reference Power 为 (M\_{ref})、矿池难度为 (D\_j)、稀缺性倍率为 (S\_j)，则所需 PoM 阈值 (R\_j) 定义如下。

$$
R\_j = M\_{ref} \times T\_j \times D\_j \times S\_j
$$

CryptoStone 的基准值如下。

* Base Mining Unit = 1,000 STONX
* Protocol Reference Power = 100,000 Power
* Target Pool Power = 40,000,000 Power

Base Mining Unit 是最小参与单位，而 Protocol Reference Power 是用于修正挖矿速度的基准算力。通过分离二者，CryptoStone 能够同时维持可参与的基础单位与长期供应控制。

例如，Garnet Pool 的基础挖矿周期为 170,000 秒，Pool Difficulty 与 Scarcity Multiplier 均为 1x 时:

$$
R\_{Garnet} = 100,000 \times 170,000 \times 1 \times 1
$$

$$
R\_{Garnet} = 17,000,000,000 \text{ PoM}
$$

当用户 (i) 的 Mining Power 为 (P\_{i,j}) 时，该用户 claim 宝石 (j) 的 NFT 1 个所需预计时间可表示为:

$$
E\[T\_{i,j}] = R\_j \div P\_{i,j}
$$

例如，用户以 Flexible 条件在 Garnet Pool 质押 6,000 STONX 时:

$$
E\[T\_{i,Garnet}] = 17,000,000,000 \div 6,000
$$

$$
\= 2,833,333\text{秒}
$$

$$
\approx 32.8\text{天}
$$

也就是说，在初始条件下，质押 6,000 STONX 的用户大约一个月左右可以 claim 1 个 Garnet NFT。更少数量的用户会更慢累积 PoM，更多数量的用户会更快达到 claim 条件。


---

# 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/22-suo-xu-pom-yu-zhi.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.