In brief
A Kaspa wallet is software for keys, addresses, signing, and transaction workflow. Network evidence is checked separately from what a wallet screen shows.
What this page explains#
Solo and pool mining are explained as different operational routes from block templates to proof-of-work attempts and payout evidence. This page sits in Wallets, Nodes, And Mining. 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 operational, so every explanation is tied to an observable workflow. A wallet can build and sign intent, a node can sync and serve state, a miner can work on templates, and none of those observations by themselves replace accepted-network evidence.
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 WIKI-MINING, RK-BLOCK-TEMPLATE, RK-MEMPOOL, RK-POW-KHEAVYHASH. 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 Solo And Pool Mining Flow, the model is built around these anchors: solo mining depends directly on local node state; pool mining adds pool policy and payout accounting; rejected shares and rejected blocks have different meanings; template construction remains node-side evidence; payout evidence is not the same as consensus validation. 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. solo mining depends directly on local node state. 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. pool mining adds pool policy and payout accounting. 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.
3. rejected shares and rejected blocks have different meanings. Operational pages explain the workflow by separating local intent, local process state, network submission, and accepted evidence. The guide names the moving part first, then gives the verification surface that can prove or disprove the claim.
4. template construction remains node-side evidence. Mempool and relay behavior describe what a node is willing to hold, replace, forward, or package; they are not final acceptance. Block templates are candidate work for miners, and they can change as node state or policy changes. The guide names each stage separately: built, signed, submitted, admitted, relayed, templated, mined, and accepted.
5. payout evidence is not the same as consensus validation. Validation pages separate layers that are often confused. Shape checks, activation context, UTXO context, mass/resource checks, script execution, covenant context, and error ownership each reject different mistakes. A useful guide traces the rejected transaction to the layer that owns the failure.
This mechanism section separates local action, node state, network submission, and accepted evidence. Commands and catalogs are useful only when current source or release evidence keeps them fresh.
How to check it#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check solo mining depends directly on local node state. | Use WIKI-MINING, RK-BLOCK-TEMPLATE, RK-MEMPOOL; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 2 | Check pool mining adds pool policy and payout accounting. | Use WIKI-MINING, RK-BLOCK-TEMPLATE, RK-MEMPOOL; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 3 | Check rejected shares and rejected blocks have different meanings. | Use WIKI-MINING, RK-BLOCK-TEMPLATE, RK-MEMPOOL; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 4 | Check template construction remains node-side evidence. | Use WIKI-MINING, RK-BLOCK-TEMPLATE, RK-MEMPOOL; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 5 | Check payout evidence is not the same as consensus validation. | Use WIKI-MINING, RK-BLOCK-TEMPLATE, RK-MEMPOOL; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
When using this page operationally, record the network, software version, node sync state, wallet or miner state, and the observation being made. A local command result is useful evidence, but accepted network consequences require accepted transaction, UTXO, block, or node-source details.
Related Pages#
- mining
- wallets-nodes-mining
- mining-hardware-and-high-staleness-catalogs