> For the complete documentation index, see [llms.txt](https://whitepaper.hypercoin.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.hypercoin.network/documentation/documentation-zh/yi-kai-shi/wa-kuang.md).

# 挖矿

区块链挖矿是验证交易、将交易记录在区块链上并创建新加密货币币的过程。它是像比特币这样的去中心化网络的支柱，确保在无需依赖中央权威的情况下实现安全、透明和信任。矿工通过使用计算能力解决复杂的数学难题参与其中。第一个解决难题的矿工将一组新的交易区块添加到区块链并以新铸造的币和交易费用作为奖励。该过程还防止了双重支付并保护网络免遭篡改。

工作量证明（Proof of Work，简称 PoW）是支撑许多区块链网络（包括 Hypercoin、比特币等）的共识机制。在 PoW 中，矿工竞争解决加密难题，这些难题的难度会自动调整以保持稳定的出块速率。PoW 确保区块链的完整性，因为修改已确认的区块需要对后续所有区块重新执行计算工作，使得攻击极其困难且代价高昂。该机制提供了强大的安全性，但也需要高能耗和专用的挖矿设备，这可能限制小型参与者的可及性。

为了解决 PoW 挖矿面临的挑战，矿工通常加入 [矿池](https://hypercoin.network/mining-pool)。矿池是一群矿工将其计算资源合并以提高成功挖出区块几率的组织。当矿池挖出一个区块时，奖励会按参与者贡献的算力比例分配。矿池使得小型矿工能够获得稳定的奖励，降低挖矿收益的波动，并提高整个挖矿运作的效率。

挖矿、工作量证明和矿池共同构成了一个稳健的生态系统，保护区块链网络安全、激励参与并确保奖励的公平分配。尽管 PoW 挖矿能耗高，但通过合并资源可以实现更广泛的参与并维持区块链系统的去中心化与无信任特性，使其成为现代加密货币网络的重要组成部分。


---

# 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://whitepaper.hypercoin.network/documentation/documentation-zh/yi-kai-shi/wa-kuang.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.
