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#
Mining hardware, hashrate tables, pools, and profitability references are volatile catalog material, not durable protocol education. 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-HASHRATE-TABLES, WIKI-PROFITABILITY, WIKI-MINING, 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 Mining Hardware And High-Staleness Catalogs, the model is built around these anchors: hardware lists can age quickly; profitability changes with market and network conditions; catalogs avoid endorsement language; protocol pages should not depend on mining ROI claims; last-checked dates and non-endorsement warnings are required. 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. hardware lists can age quickly. 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.
2. profitability changes with market and network conditions. 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.
3. catalogs avoid endorsement language. 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. protocol pages should not depend on mining ROI claims. 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.
5. last-checked dates and non-endorsement warnings are required. 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.
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 hardware lists can age quickly. | Use WIKI-HASHRATE-TABLES, WIKI-PROFITABILITY, WIKI-MINING; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 2 | Check profitability changes with market and network conditions. | Use WIKI-HASHRATE-TABLES, WIKI-PROFITABILITY, WIKI-MINING; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 3 | Check catalogs avoid endorsement language. | Use WIKI-HASHRATE-TABLES, WIKI-PROFITABILITY, WIKI-MINING; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 4 | Check protocol pages should not depend on mining ROI claims. | Use WIKI-HASHRATE-TABLES, WIKI-PROFITABILITY, WIKI-MINING; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 5 | Check last-checked dates and non-endorsement warnings are required. | Use WIKI-HASHRATE-TABLES, WIKI-PROFITABILITY, WIKI-MINING; 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#
- solo-and-pool-mining-flow
- wallets-nodes-mining
- mining-troubleshooting