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#
Wallet roundtrip evidence checks whether intent survives build, signing, decoding, submission, and accepted-state observation. 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-WALLET, RK-WRPC, RK-RPC-TX, RK-VIRTUAL-PIPELINE. 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 Wallet Roundtrip Evidence, the model is built around these anchors: local transaction construction is only intent; signed bytes show authorization under a signing context; decoded signed transactions should preserve expected fields; broadcast success is not accepted evidence; accepted transaction and UTXO evidence close the loop. 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. local transaction construction is only intent. 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. signed bytes show authorization under a signing context. 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. decoded signed transactions should preserve expected fields. 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. broadcast success is not accepted 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. accepted transaction and UTXO evidence close the loop. 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 local transaction construction is only intent. | Use RK-WALLET, RK-WRPC, RK-RPC-TX; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 2 | Check signed bytes show authorization under a signing context. | Use RK-WALLET, RK-WRPC, RK-RPC-TX; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 3 | Check decoded signed transactions should preserve expected fields. | Use RK-WALLET, RK-WRPC, RK-RPC-TX; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 4 | Check broadcast success is not accepted evidence. | Use RK-WALLET, RK-WRPC, RK-RPC-TX; check version, network, node sync, index, wallet or miner state, and accepted evidence separately. |
| 5 | Check accepted transaction and UTXO evidence close the loop. | Use RK-WALLET, RK-WRPC, RK-RPC-TX; 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#
- setting-up-a-cli-wallet
- wallets-nodes-mining
- message-signing-and-kip-0005