In brief
The readiness operations source path maps public claims about wallets, nodes, mining, broadcast, and accepted evidence to the upstream files that can support them.
What this page explains#
The readiness operations source path maps public claims about wallets, nodes, mining, broadcast, and accepted evidence to the upstream files that can support them. This page sits in Testnets And Production Readiness. 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 treats readiness as evidence discipline. Testnet success, explorer observations, wallet signing, release checks, and production review each answer different questions and must not be substituted for each other.
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-WALLET-TEST, RK-WRPC, RK-RPC-API, RK-RPC-TX. 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 Operations Source Path, the model is built around these anchors: wallet readiness routes to wallet, tests, RPC, and wRPC paths; node readiness routes to network, address, P2P, IBD, logs, and indexes; mining readiness routes to mempool and block-template source; broadcast and accepted evidence route to RPC, mempool, and virtual processing; tests and release notes are recorded before stronger readiness wording. 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. wallet readiness routes to wallet, tests, RPC, and wRPC paths. Developer integration pages explain an interface by naming the source object behind it. API, RPC, wRPC, SDK, wallet, and indexer surfaces are useful only when they preserve the fields and evidence that the protocol layer actually defines. Accepted-state evidence, replay behavior, schema choices, and endpoint disagreement must be checked separately.
2. node readiness routes to network, address, P2P, IBD, logs, and indexes. Network identity is the first readiness check. The page records the exact testnet or mainnet context, address prefix or suffix assumptions, node command or release, and the endpoint being observed so that evidence from one network is not reused as evidence for another.
3. mining readiness routes to mempool and block-template source. 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.
4. broadcast and accepted evidence route to RPC, mempool, and virtual processing. Accepted evidence needs a timestamped chain of custody: built transaction, signed transaction, broadcast or submission result, accepted transaction or UTXO-state evidence, and any explorer or indexer observation used to confirm it. Local logs alone stay scoped to local experience.
5. tests and release notes are recorded before stronger readiness wording. 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.
This mechanism section treats readiness as dated evidence: network, release, branch or commit, tool version, observation, and accepted/rejected result are all part of the claim.
How to check it#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check wallet readiness routes to wallet, tests, RPC, and wRPC paths. | Use RK-WALLET, RK-WALLET-TEST, RK-WRPC; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 2 | Check node readiness routes to network, address, P2P, IBD, logs, and indexes. | Use RK-WALLET, RK-WALLET-TEST, RK-WRPC; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 3 | Check mining readiness routes to mempool and block-template source. | Use RK-WALLET, RK-WALLET-TEST, RK-WRPC; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 4 | Check broadcast and accepted evidence route to RPC, mempool, and virtual processing. | Use RK-WALLET, RK-WALLET-TEST, RK-WRPC; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 5 | Check tests and release notes are recorded before stronger readiness wording. | Use RK-WALLET, RK-WALLET-TEST, RK-WRPC; add date, network, release or commit, tool version, and accepted/rejected evidence. |
When using this page for readiness, record the date, network, release or commit, tool versions, endpoint or explorer observation, and accepted or rejected result. Testnet success, local logs, and live API observations remain scoped evidence until release and source checks support broader wording.
Related Pages#
- readiness-troubleshooting
- testnets-production-readiness