Developer Integration

What this page explains#

Map docs, APIs, SDKs, indexers, tests, and tooling into a source-checked integration guide. 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, DOC-KASPA-API, RK-RPC-PROTO, 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 Developer Integration, the model is built around these anchors: Developer integration starts by deciding what kind of claim is being made: interface, convenience, observation, or protocol behavior.; Developer environment setup begins with network selection, node access, RPC shape, wallet authority, and reproducible local tooling.; RPC and wRPC are interfaces into node behavior and must preserve field meaning across clients.; REST API pages are convenience and observation pages, not consensus authority.; SDK pages teach build/decode/sign/submit/observe loops while keeping wallet authority and network evidence separate.. 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. Developer integration starts by deciding what kind of claim is being made: interface, convenience, observation, or protocol behavior.. 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. Developer environment setup begins with network selection, node access, RPC shape, wallet authority, and reproducible local tooling.. 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. RPC and wRPC are interfaces into node behavior and must preserve field meaning across clients.. 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. REST API pages are convenience and observation pages, not consensus authority.. 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. SDK pages teach build/decode/sign/submit/observe loops while keeping wallet authority and network evidence 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.

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#

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.

Expanded Category Guide#

This category carries integration surfaces. It should distinguish protocol objects, RPC/wRPC/API representations, SDK behavior, indexer replay, and application-readiness claims.

Use this category as a curated path. Start with the category README to understand the boundary, then read the mechanism pages, then follow source-path or open-gap pages for claims that need stronger evidence. If a page contains needs checking rows, keep those claims visibly unresolved until a reader reads the cited public source directly.

The category should not be treated as final authority by folder name alone. The authority comes from page Source Notes, Source Lists, public URLs, and the status labels attached to each claim.

Related Pages#

• developer-integration
• developer-knowledge-base

Topic pages#

• Developer Knowledge Base: Developer integration starts by deciding what kind of claim is being made: interface, convenience, observation, or protocol behavior.
• Developer Environment, Networks, RPC, And Wallets: Developer environment setup begins with network selection, node access, RPC shape, wallet authority, and reproducible local tooling.
• RPC And wRPC: RPC and wRPC are interfaces into node behavior and must preserve field meaning across clients.
• REST API: REST API pages are convenience and observation pages, not consensus authority.
• SDKs And Wallet Builders: SDK pages teach build/decode/sign/submit/observe loops while keeping wallet authority and network evidence separate.
• Indexers And Accepted Evidence: Indexers make accepted data usable, but they must recover, replay, and handle stale heads.
• Docker And Self-Hosted Nodes: Self-hosted node pages explain environment and operation without turning deployment snippets into protocol authority.
• Testing And Tooling: Testing pages connect source claims to reproducible evidence and named limits.
• Integration Readiness Checklist: Readiness is a checklist of evidence: fields preserved, network selected, source current, tests run, accepted evidence captured, and recovery paths tested.

Topic notes#

This category is accepted when the subpages explain the actual topics, not merely the source links. Each subpage carries public source IDs, claim labels, Open Questions, and a path from first contact into source review.