In brief
Readiness is a checklist of evidence: fields preserved, network selected, source current, tests run, accepted evidence captured, and recovery paths tested.
What this page explains#
Readiness is a checklist of evidence: fields preserved, network selected, source current, tests run, accepted evidence captured, and recovery paths tested. This page sits in Developer Integration. 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 turns public interfaces into a reviewable integration path. API calls, SDK builders, wallets, indexers, and Docker nodes are useful surfaces, but each must preserve the protocol meaning carried by source and accepted 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 DOC-KASPA-BUILD, RK-RPC-TX, RK-WRPC, RK-INDEXES, RK-TESTS. 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 Integration Readiness Checklist, the model is built around these anchors: field preservation is checked from builder to RPC/indexer; wallet signing and network evidence are separate; restart/replay is tested for indexers; source refresh happens before publication; Open Questions remain visible until closed. 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. field preservation is checked from builder to RPC/indexer. 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. wallet signing and network evidence are separate. 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.
3. restart/replay is tested for indexers. 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.
4. source refresh happens before publication. 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.
5. Open Questions remain visible until closed. 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.
This mechanism section treats API, RPC, wRPC, SDK, wallet, Docker, and indexer surfaces as interfaces to be checked against protocol-defined fields and accepted-state evidence.
How to check it#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check field preservation is checked from builder to RPC/indexer. | Use DOC-KASPA-BUILD, RK-RPC-TX, RK-WRPC; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 2 | Check wallet signing and network evidence are separate. | Use DOC-KASPA-BUILD, RK-RPC-TX, RK-WRPC; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 3 | Check restart/replay is tested for indexers. | Use DOC-KASPA-BUILD, RK-RPC-TX, RK-WRPC; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 4 | Check source refresh happens before publication. | Use DOC-KASPA-BUILD, RK-RPC-TX, RK-WRPC; add date, network, release or commit, tool version, and accepted/rejected evidence. |
| 5 | Check Open Questions remain visible until closed. | Use DOC-KASPA-BUILD, RK-RPC-TX, RK-WRPC; add date, network, release or commit, tool version, and accepted/rejected evidence. |
When using this page for integration work, check that the interface preserves the field or evidence surface being claimed. Hosted APIs, node RPC, SDKs, wallets, and indexers are useful surfaces, but protocol meaning still needs source, release, KIP, or accepted-state evidence.
Related Pages#
- testing-and-tooling
- developer-integration