In brief
Proof of work gives blocks an objective work signal; kHeavyHash and header checks belong to source-backed mining and validation pages.
What this page explains#
Proof of work gives blocks an objective work signal; kHeavyHash and header checks belong to source-backed mining and validation pages. This page sits in Core Protocol Source Path. It gives the topic a plain-language handle first, then shows the working idea, the mechanism, the source trail, and any limits that still matter. This category is a code-reading path. It treats source files as evidence with boundaries: a constant proves one kind of thing, a pipeline proves another, and a test proves only the scenario it covers.
The writing follows a simple Kaspa documentation pattern: answer the practical question first, then link outward for details. The closest public sources for this page are RK-POW-KHEAVYHASH, RK-HEADER-PIPELINE, WIKI-MINING. Local notes can help choose what to explain, but public-facing references resolve to upstream websites, repositories, papers, release pages, or docs.
How to think about it#
The practical model starts by naming the layer that owns the topic: wallet use, node operation, consensus, transaction validation, Toccata script behavior, tooling, or research. From there, the page shows which public source can support the explanation and where the explanation becomes incomplete.
For Proof Of Work And kHeavyHash, the model is built around these anchors: nonce/header search is miner work; hashing and target checks are implementation details; proof of work does not validate transaction contents alone; blue score/work fields are separate consensus context; hardware catalog claims are high-staleness operational material. This model is useful, but it does not encode every constant, branch, error type, or edge case. Those details belong in the source path and the source notes.
How it works#
1. nonce/header search is miner work. Mining and proof-of-work explanations belong to the node/miner path, not the ZK path. The node prepares candidate block templates from consensus and mempool state; mining hardware or pool software searches for acceptable work. Hardware catalogs and profitability references are volatile, while the durable protocol boundary is proof of work verification and template validity.
2. hashing and target checks are implementation details. Core protocol source pages explain which subsystem owns the behavior. The reader should come away knowing whether the evidence belongs in params, constants, proof of work, header processing, body processing, virtual processing, DAA, pruning, reachability, storage, or tests.
3. proof of work does not validate transaction contents alone. Mining and proof-of-work explanations belong to the node/miner path, not the ZK path. The node prepares candidate block templates from consensus and mempool state; mining hardware or pool software searches for acceptable work. Hardware catalogs and profitability references are volatile, while the durable protocol boundary is proof of work verification and template validity.
4. blue score/work fields are separate consensus context. Blue/red vocabulary belongs to consensus classification, not user reputation or transaction success. Blue score and blue work are progress signals inside the consensus view. They are useful for understanding chain progress and ordering context, but wallet, indexer, and app pages still need accepted-transaction or UTXO evidence before claiming a spend has taken effect.
5. hardware catalog claims are high-staleness operational material. Core protocol source pages explain which subsystem owns the behavior. The reader should come away knowing whether the evidence belongs in params, constants, proof of work, header processing, body processing, virtual processing, DAA, pruning, reachability, storage, or tests.
This mechanism section is a source checking guide. Each paragraph names the subsystem that owns the claim and keeps constants, params, pipelines, tests, releases, and KIPs in their own evidence lanes.
How to check it#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check nonce/header search is miner work. | Read RK-POW-KHEAVYHASH, RK-HEADER-PIPELINE, WIKI-MINING; identify the exact Rusty Kaspa module, test, KIP, or release that owns this behavior. |
| 2 | Check hashing and target checks are implementation details. | Read RK-POW-KHEAVYHASH, RK-HEADER-PIPELINE, WIKI-MINING; identify the exact Rusty Kaspa module, test, KIP, or release that owns this behavior. |
| 3 | Check proof of work does not validate transaction contents alone. | Read RK-POW-KHEAVYHASH, RK-HEADER-PIPELINE, WIKI-MINING; identify the exact Rusty Kaspa module, test, KIP, or release that owns this behavior. |
| 4 | Check blue score/work fields are separate consensus context. | Read RK-POW-KHEAVYHASH, RK-HEADER-PIPELINE, WIKI-MINING; identify the exact Rusty Kaspa module, test, KIP, or release that owns this behavior. |
| 5 | Check hardware catalog claims are high-staleness operational material. | Read RK-POW-KHEAVYHASH, RK-HEADER-PIPELINE, WIKI-MINING; identify the exact Rusty Kaspa module, test, KIP, or release that owns this behavior. |
When using this page for source review, start with the claim class, then read the owner module, tests, KIP or release context, and any dependent interface. Record what the source proves and what it does not prove before strengthening wiki wording.
Related Pages#
- header-body-virtual-pipeline
- core-protocol-source-path
- daa-difficulty-and-activation