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#
This page bridges operations and protocol source: a node may admit a transaction, but miners still need a valid block template and consensus still decides acceptance. 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 RK-MEMPOOL, RK-MEMPOOL-STANDARD, RK-MEMPOOL-RBF, RK-BLOCK-TEMPLATE, RK-TEMPLATE-SELECTORS. 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 Mempool And Block Templates, the model is built around these anchors: mempool admission is local policy; block templates select candidate transactions under limits; dependencies, fees, mass, and readiness affect selection; miners can reject or fail work for reasons outside a wallet's local intent; accepted evidence comes later through virtual processing. 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. mempool admission is local policy. 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.
2. block templates select candidate transactions under limits. 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. dependencies, fees, mass, and readiness affect selection. Readiness pages are evidence gates. A testnet result is useful only with network name, date, release or branch, node/wallet/tool versions, and accepted evidence. Release notes and source paths support stronger claims; old testnet observations remain historical unless refreshed.
4. miners can reject or fail work for reasons outside a wallet's local intent. 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. accepted evidence comes later through virtual processing. 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.
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 mempool admission is local policy. | Use RK-MEMPOOL, RK-MEMPOOL-STANDARD, RK-MEMPOOL-RBF; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 2 | Check block templates select candidate transactions under limits. | Use RK-MEMPOOL, RK-MEMPOOL-STANDARD, RK-MEMPOOL-RBF; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 3 | Check dependencies, fees, mass, and readiness affect selection. | Use RK-MEMPOOL, RK-MEMPOOL-STANDARD, RK-MEMPOOL-RBF; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 4 | Check miners can reject or fail work for reasons outside a wallet's local intent. | Use RK-MEMPOOL, RK-MEMPOOL-STANDARD, RK-MEMPOOL-RBF; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 5 | Check accepted evidence comes later through virtual processing. | Use RK-MEMPOOL, RK-MEMPOOL-STANDARD, RK-MEMPOOL-RBF; 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-troubleshooting
- wallets-nodes-mining
- operational-troubleshooting