In brief
Indexers make accepted data usable, but they must recover, replay, and handle stale heads.
What this page explains#
Indexers make accepted data usable, but they must recover, replay, and handle stale heads. 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 TOOL-SIMPLY-KASPA-INDEXER, RK-INDEXES, RK-VIRTUAL-PIPELINE, 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 Indexers And Accepted Evidence, the model is built around these anchors: accepted transactions are the input, not local intent; UTXO changes and covenant heads need replay discipline; restart recovery is part of correctness; endpoint disagreement must be investigated; indexer schemas are app evidence, not consensus rules. 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. accepted transactions are the input, not local intent. 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. UTXO changes and covenant heads need replay discipline. 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 recovery is part of correctness. 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. endpoint disagreement must be investigated. 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. indexer schemas are app evidence, not consensus rules. Index and query-surface claims are about what data a node, RPC service, or indexer can expose, not a shortcut around consensus. The guide should say which index must exist, which interface reads it, how restart or replay affects it, and which source path proves the field or evidence is preserved.
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 accepted transactions are the input, not local intent. | Use TOOL-SIMPLY-KASPA-INDEXER, RK-INDEXES, RK-VIRTUAL-PIPELINE; confirm the interface preserves the protocol field or evidence surface being claimed. |
| 2 | Check UTXO changes and covenant heads need replay discipline. | Use TOOL-SIMPLY-KASPA-INDEXER, RK-INDEXES, RK-VIRTUAL-PIPELINE; confirm the interface preserves the protocol field or evidence surface being claimed. |
| 3 | Check restart recovery is part of correctness. | Use TOOL-SIMPLY-KASPA-INDEXER, RK-INDEXES, RK-VIRTUAL-PIPELINE; confirm the interface preserves the protocol field or evidence surface being claimed. |
| 4 | Check endpoint disagreement must be investigated. | Use TOOL-SIMPLY-KASPA-INDEXER, RK-INDEXES, RK-VIRTUAL-PIPELINE; confirm the interface preserves the protocol field or evidence surface being claimed. |
| 5 | Check indexer schemas are app evidence, not consensus rules. | Use TOOL-SIMPLY-KASPA-INDEXER, RK-INDEXES, RK-VIRTUAL-PIPELINE; 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#
- sdks-and-wallet-builders
- developer-integration
- docker-and-self-hosted-nodes