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#
A node is the local participant that syncs, validates, communicates with peers, serves APIs, and provides the state surface wallets and miners depend on. 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-NODE, RK-KASPAD-ARGS, RK-KASPAD-DAEMON, RK-RPC-STATUS, 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 Nodes, the model is built around these anchors: P2P connects the node to the network graph; sync and IBD determine whether local state is useful; indexes change what queries are available; logs and metrics are operational evidence; node source paths close behavior claims better than catalog pages. 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. P2P connects the node to the network graph. A node is useful only after its network, peer, sync, and index assumptions are understood. Process uptime is not the same as useful state. P2P handshake, IBD progress, logs, ports, and optional indexes each answer a different operator question, so troubleshooting starts by locating the failed layer rather than retrying commands blindly.
2. sync and IBD determine whether local state is useful. A node is useful only after its network, peer, sync, and index assumptions are understood. Process uptime is not the same as useful state. P2P handshake, IBD progress, logs, ports, and optional indexes each answer a different operator question, so troubleshooting starts by locating the failed layer rather than retrying commands blindly.
3. indexes change what queries are available. 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. logs and metrics are operational evidence. 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.
5. node source paths close behavior claims better than catalog pages. A node is useful only after its network, peer, sync, and index assumptions are understood. Process uptime is not the same as useful state. P2P handshake, IBD progress, logs, ports, and optional indexes each answer a different operator question, so troubleshooting starts by locating the failed layer rather than retrying commands blindly.
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 P2P connects the node to the network graph. | Use WIKI-NODE, RK-KASPAD-ARGS, RK-KASPAD-DAEMON; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 2 | Check sync and IBD determine whether local state is useful. | Use WIKI-NODE, RK-KASPAD-ARGS, RK-KASPAD-DAEMON; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 3 | Check indexes change what queries are available. | Use WIKI-NODE, RK-KASPAD-ARGS, RK-KASPAD-DAEMON; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 4 | Check logs and metrics are operational evidence. | Use WIKI-NODE, RK-KASPAD-ARGS, RK-KASPAD-DAEMON; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 5 | Check node source paths close behavior claims better than catalog pages. | Use WIKI-NODE, RK-KASPAD-ARGS, RK-KASPAD-DAEMON; 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#
- wallet-troubleshooting
- wallets-nodes-mining
- setting-up-a-cli-node