In brief
Developer integration starts by deciding what kind of claim is being made: interface, convenience, observation, or protocol behavior.
What this page explains#
Developer integration starts by deciding what kind of claim is being made: interface, convenience, observation, or protocol behavior. 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 WIKI-DEVELOPERS-KB, DOC-KASPA-BUILD, RK-REPO. 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 Developer Knowledge Base, the model is built around these anchors: official developer pages orient the reader; APIs expose node or service surfaces; SDKs improve ergonomics but need field preservation; indexers observe accepted data; implementation source closes protocol claims. 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. official developer pages orient the reader. 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. APIs expose node or service surfaces. 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. SDKs improve ergonomics but need field preservation. 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. indexers observe accepted data. 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. implementation source closes protocol claims. 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 official developer pages orient the reader. | Use WIKI-DEVELOPERS-KB, DOC-KASPA-BUILD, RK-REPO; confirm the interface preserves the protocol field or evidence surface being claimed. |
| 2 | Check APIs expose node or service surfaces. | Use WIKI-DEVELOPERS-KB, DOC-KASPA-BUILD, RK-REPO; confirm the interface preserves the protocol field or evidence surface being claimed. |
| 3 | Check SDKs improve ergonomics but need field preservation. | Use WIKI-DEVELOPERS-KB, DOC-KASPA-BUILD, RK-REPO; confirm the interface preserves the protocol field or evidence surface being claimed. |
| 4 | Check indexers observe accepted data. | Use WIKI-DEVELOPERS-KB, DOC-KASPA-BUILD, RK-REPO; confirm the interface preserves the protocol field or evidence surface being claimed. |
| 5 | Check implementation source closes protocol claims. | Use WIKI-DEVELOPERS-KB, DOC-KASPA-BUILD, RK-REPO; confirm the interface preserves the protocol field or evidence surface being claimed. |
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#
- developer-integration
- developer-environment-networks-rpc-and-wallets