In brief
Self-hosted node pages explain environment and operation without turning deployment snippets into protocol authority.
What this page explains#
Self-hosted node pages explain environment and operation without turning deployment snippets into protocol authority. 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-RUSTY-KASPAD-DOCKER, RK-REPO, RK-P2P-FLOW, RK-INDEXES. 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 Docker And Self-Hosted Nodes, the model is built around these anchors: Docker images are environment artifacts; network flags and app data paths affect behavior; indexes change available queries; logs and ports are verification surfaces; release and image freshness are operational risks. 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. Docker images are environment artifacts. 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. network flags and app data paths affect 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.
3. indexes change available queries. 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. logs and ports are verification 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.
5. release and image freshness are operational risks. 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 Docker images are environment artifacts. | Use DOC-RUSTY-KASPAD-DOCKER, RK-REPO, RK-P2P-FLOW; confirm the interface preserves the protocol field or evidence surface being claimed. |
| 2 | Check network flags and app data paths affect behavior. | Use DOC-RUSTY-KASPAD-DOCKER, RK-REPO, RK-P2P-FLOW; confirm the interface preserves the protocol field or evidence surface being claimed. |
| 3 | Check indexes change available queries. | Use DOC-RUSTY-KASPAD-DOCKER, RK-REPO, RK-P2P-FLOW; confirm the interface preserves the protocol field or evidence surface being claimed. |
| 4 | Check logs and ports are verification surfaces. | Use DOC-RUSTY-KASPAD-DOCKER, RK-REPO, RK-P2P-FLOW; confirm the interface preserves the protocol field or evidence surface being claimed. |
| 5 | Check release and image freshness are operational risks. | Use DOC-RUSTY-KASPAD-DOCKER, RK-REPO, RK-P2P-FLOW; 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#
- indexers-and-accepted-evidence
- developer-integration
- testing-and-tooling