Why blockDAG Matters

What this page explains#

This page gives the first transition from ordinary chain intuition into Kaspa's blockDAG model, while keeping paper vocabulary separate from implementation 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-KASPA, PAPER-GHOSTDAG, RK-GHOSTDAG, WIKI-BACKGROUND. 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 blockDAG Matters, the model is built around these anchors: a chain treats simultaneous valid blocks as competition for one previous-block line; a DAG can keep multiple parent references without removing the need for ordering; parallel blocks create an ordering problem that GHOSTDAG must solve; blue score, selected parent, and virtual state are later mechanics, not first-contact terms; paper explanations are useful research background but do not replace the node source. 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. a chain treats simultaneous valid blocks as competition for one previous-block line. 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.

2. a DAG can keep multiple parent references without removing the need for ordering. 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. parallel blocks create an ordering problem that GHOSTDAG must solve. 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. blue score, selected parent, and virtual state are later mechanics, not first-contact terms. 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. paper explanations are useful research background but do not replace the node source. 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 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#

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-kaspa
• foundations
• getting-started