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 troubleshooting separates node sync, template construction, miner connection, proof-of-work attempts, pool policy, and accepted block 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-P2P-FLOW. 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 Troubleshooting, the model is built around these anchors: a connected miner can still be working on stale or invalid assumptions; template errors point back to node and mempool state; rejected work can be local, pool, or network-side; accepted blocks need network evidence; hardware and firmware claims need fresh sources. 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. a connected miner can still be working on stale or invalid assumptions. 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. template errors point back to node and mempool state. 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.
3. rejected work can be local, pool, or network-side. 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. accepted blocks need network evidence. Virtual state is the bridge from ordered consensus consequences into the state surfaces that tools can inspect. Mempool visibility says a node is considering a transaction; accepted evidence says the transaction was incorporated through consensus processing. UTXO diffs, accepting data, and indexer replay are the review trail for applications that need durable state.
5. hardware and firmware claims need fresh sources. Source-review pages are practical maps. They start from one claim, identify the owning subsystem, inspect data structures and serialization, follow validation or execution, check tests and release context, and then write down what remains unresolved. The page is useful only if it says both what a source proves and what it does not prove.
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 a connected miner can still be working on stale or invalid assumptions. | Use WIKI-MINING, RK-BLOCK-TEMPLATE, RK-MEMPOOL; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 2 | Check template errors point back to node and mempool state. | 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 work can be local, pool, or network-side. | Use WIKI-MINING, RK-BLOCK-TEMPLATE, RK-MEMPOOL; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 4 | Check accepted blocks need network 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 hardware and firmware claims need fresh sources. | 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-hardware-and-high-staleness-catalogs
- wallets-nodes-mining
- mempool-and-block-templates