In brief
Kaspa is introduced as a proof of work cryptocurrency network whose core learning path quickly leads into blockDAG consensus, UTXO transactions, node operation, and source-backed verification.
What this page explains#
Kaspa is introduced as a proof of work cryptocurrency network whose core learning path quickly leads into blockDAG consensus, UTXO transactions, node operation, and source-backed verification. 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, RK-REPO, RK-GHOSTDAG. 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 What Is Kaspa, the model is built around these anchors: proof of work gives the network an objective work signal; blockDAG structure appears because blocks can be produced close together; GHOSTDAG is the ordering bridge, not a marketing label; wallet, node, miner, and developer paths should converge on accepted transaction and UTXO evidence rather than local intent alone; implementation and papers answer different questions. 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. proof of work gives the network an objective work signal. Foundation pages introduce why Kaspa needs these words before they explain the internals. The first-contact model is that proof of work gives blocks an objective work signal, blockDAG structure keeps parallel block information in view, and GHOSTDAG is the later ordering bridge. Source-level validation belongs in the consensus and core protocol pages.
2. blockDAG structure appears because blocks can be produced close together. Foundation pages introduce why Kaspa needs these words before they explain the internals. The first-contact model is that proof of work gives blocks an objective work signal, blockDAG structure keeps parallel block information in view, and GHOSTDAG is the later ordering bridge. Source-level validation belongs in the consensus and core protocol pages.
3. GHOSTDAG is the ordering bridge, not a marketing label. Foundation pages introduce why Kaspa needs these words before they explain the internals. The first-contact model is that proof of work gives blocks an objective work signal, blockDAG structure keeps parallel block information in view, and GHOSTDAG is the later ordering bridge. Source-level validation belongs in the consensus and core protocol pages.
4. wallet, node, miner, and developer paths should converge on accepted transaction and UTXO evidence rather than local intent alone. 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. implementation and papers answer different questions. 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.
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 proof of work gives the network an objective work signal. | Use WIKI-KASPA, WIKI-HOME, PAPER-GHOSTDAG; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 2 | Check blockDAG structure appears because blocks can be produced close together. | Use WIKI-KASPA, WIKI-HOME, PAPER-GHOSTDAG; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 3 | Check GHOSTDAG is the ordering bridge, not a marketing label. | Use WIKI-KASPA, WIKI-HOME, PAPER-GHOSTDAG; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 4 | Check wallet, node, miner, and developer paths should converge on accepted transaction and UTXO evidence rather than local intent alone. | Use WIKI-KASPA, WIKI-HOME, PAPER-GHOSTDAG; keep deep mechanics in the related consensus, transaction, operation, or Toccata page. |
| 5 | Check implementation and papers answer different questions. | 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#
- foundations
- why-kaspa