In brief
A practical start page points readers toward the first action they are trying to take: hold keys, run a node, mine, build, or study source behavior.
What this page explains#
A practical start page points readers toward the first action they are trying to take: hold keys, run a node, mine, build, or study source behavior. This page sits in Foundations. 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 gives the reader durable handles before any source walk begins. It keeps identity, motivation, vocabulary, history, and first practical routes separate so a later consensus or developer page does not have to carry every introduction at once.
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-GETTING-STARTED, WIKI-WALLET, WIKI-NODE, WIKI-MINING, DOC-KASPA-BUILD. 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 Getting Started, the model is built around these anchors: wallet work begins with key ownership and UTXO spendability; node work begins with synchronization, peers, indexes, and logs; mining work begins with block templates and proof of work; developer work begins with APIs, SDKs, and Source Priority; each path needs a freshness check before operational instructions are reused. 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. wallet work begins with key ownership and UTXO spendability. A start page acts like a branch selector. It names the action the reader is trying to take, then points to the wallet, node, mining, developer, or source checking path that carries the real procedure. It does not compress all operational mechanics into the first page.
2. node work begins with synchronization, peers, indexes, and logs. A start page acts like a branch selector. It names the action the reader is trying to take, then points to the wallet, node, mining, developer, or source checking path that carries the real procedure. It does not compress all operational mechanics into the first page.
3. mining work begins with block templates and proof of work. A start page acts like a branch selector. It names the action the reader is trying to take, then points to the wallet, node, mining, developer, or source checking path that carries the real procedure. It does not compress all operational mechanics into the first page.
4. developer work begins with APIs, SDKs, and Source Priority. A start page acts like a branch selector. It names the action the reader is trying to take, then points to the wallet, node, mining, developer, or source checking path that carries the real procedure. It does not compress all operational mechanics into the first page.
5. each path needs a freshness check before operational instructions are reused. A start page acts like a branch selector. It names the action the reader is trying to take, then points to the wallet, node, mining, developer, or source checking path that carries the real procedure. It does not compress all operational mechanics into the first page.
This mechanism section is a branch map. It identifies the first practical routes and points each route to the page where the detailed source-backed procedure belongs.
How to check it#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check wallet work begins with key ownership and UTXO spendability. | Use WIKI-WALLET and the wallet operation pages; keep signing, backup, and accepted-evidence mechanics in the wallet section. |
| 2 | Check node work begins with synchronization, peers, indexes, and logs. | Use WIKI-NODE and the node operation pages; keep sync, P2P, indexes, and logs in the node section. |
| 3 | Check mining work begins with block templates and proof of work. | Use WIKI-MINING and the mining operation pages; keep templates, proof of work, and pool/solo details in the mining section. |
| 4 | Check developer work begins with APIs, SDKs, and Source Priority. | Use DOC-KASPA-BUILD and the developer integration pages; keep API, SDK, and Source Priority details in the developer section. |
| 5 | Check each path needs a freshness check before operational instructions are reused. | Use WIKI-GETTING-STARTED plus the specific downstream operation page for the selected path. |
When using this page for a wiki article, keep orientation separate from mechanics. The page can name the path and the next concept, but detailed wallet, node, mining, consensus, transaction, or Toccata behavior belongs in the downstream page that carries the stronger Source List.
Related Pages#
- why-blockdag
- foundations
- terminology