In brief
This page explains the problem Kaspa is trying to address before it introduces deeper protocol terms.
What this page explains#
This page explains the problem Kaspa is trying to address before it introduces deeper protocol terms. 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-KASPA, WIKI-HOME, PAPER-GHOSTDAG, PAPER-DAGKNIGHT. 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 Why Kaspa, the model is built around these anchors: the first question is why a proof of work network would need a different block structure; throughput, confirmation experience, and decentralization claims must be handled carefully; research papers explain design pressure but not all current behavior; the guide routes readers from public motivation into source-backed mechanics; claims about superiority or guarantees are avoided unless exact sources support them. 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. the first question is why a proof of work network would need a different block structure. FAQ material answers the user-facing question directly, then links to the page that owns the mechanism. Volatile answers about releases, wallets, testnets, and tools keep freshness labels, while unresolved answers stay visible as Open Questions.
2. throughput, confirmation experience, and decentralization claims must be handled carefully. Foundation pages turn a short public idea into a stable learning path. The explanation names why the topic appears, which later page carries the mechanism, and what source class can support stronger claims. The goal is orientation that does not pretend to be implementation proof.
3. research papers explain design pressure but not all current behavior. Foundation pages turn a short public idea into a stable learning path. The explanation names why the topic appears, which later page carries the mechanism, and what source class can support stronger claims. The goal is orientation that does not pretend to be implementation proof.
4. the guide routes readers from public motivation into source-backed mechanics. Foundation pages turn a short public idea into a stable learning path. The explanation names why the topic appears, which later page carries the mechanism, and what source class can support stronger claims. The goal is orientation that does not pretend to be implementation proof.
5. claims about superiority or guarantees are avoided unless exact sources support them. Foundation pages turn a short public idea into a stable learning path. The explanation names why the topic appears, which later page carries the mechanism, and what source class can support stronger claims. The goal is orientation that does not pretend to be implementation proof.
This mechanism section is intentionally shallow-to-deep: it gives the first usable explanation, then names the later page where source-level mechanics belong. Foundation pages must not smuggle in covenant, ZK, or readiness claims unless the Source List and Source Notes support that exact bridge.
How to check it#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check the first question is why a proof of work network would need a different block structure. | Use WIKI-KASPA, WIKI-HOME, PAPER-GHOSTDAG; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 2 | Check throughput, confirmation experience, and decentralization claims must be handled carefully. | Use WIKI-KASPA, WIKI-HOME, PAPER-GHOSTDAG; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 3 | Check research papers explain design pressure but not all current behavior. | Use WIKI-KASPA, WIKI-HOME, PAPER-GHOSTDAG; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 4 | Check the guide routes readers from public motivation into source-backed mechanics. | Use WIKI-KASPA, WIKI-HOME, PAPER-GHOSTDAG; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 5 | Check claims about superiority or guarantees are avoided unless exact sources support them. | Use WIKI-KASPA, WIKI-HOME, PAPER-GHOSTDAG; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
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#
- what-is-kaspa
- foundations
- why-blockdag