Kaspa One Stop
Search loads when you begin.

DAA, Difficulty, And Activation

Difficulty adjustment and activation pages show how timing, work, and rule changes are checked against source and KIPs.

Reading pathCore Protocol Source Path
  1. Core Protocol Source Path
  2. Proof Of Work And kHeavyHash
  3. Header, Body, And Virtual Pipeline
  4. P2P And IBD
  5. Storage, Indexes, And State Surfaces
  6. Pruning And Pruning Proofs
  7. DAA, Difficulty, And Activation
  8. Activation, KIPs, And Release Evidence
  9. Rusty Kaspa Consensus Map

In brief

Difficulty adjustment and activation pages show how timing, work, and rule changes are checked against source and KIPs.

What this page explains#

Difficulty adjustment and activation pages show how timing, work, and rule changes are checked against source and KIPs. This page sits in Core Protocol Source Path. 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 is a code-reading path. It treats source files as evidence with boundaries: a constant proves one kind of thing, a pipeline proves another, and a test proves only the scenario it covers.

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 RK-DAA, RK-PARAMS, RK-CONSTANTS, KIP-0003, KIP-0004. 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 DAA, Difficulty, And Activation, the model is built around these anchors: DAA decides difficulty context from source-defined windows and parameters; DAA score appears in activation and state discussions; KIP status can be historical, current, or proposed; params and constants close many activation claims; release notes and source must agree before public current wording is used. 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. DAA decides difficulty context from source-defined windows and parameters. Source-review pages are practical maps. They start from one claim, identify the owning subsystem, inspect data structures and serialization, follow validation or execution, check tests and release context, and then write down what remains unresolved. The page is useful only if it says both what a source proves and what it does not prove.

2. DAA score appears in activation and state discussions. Core protocol source pages explain which subsystem owns the behavior. The reader should come away knowing whether the evidence belongs in params, constants, proof of work, header processing, body processing, virtual processing, DAA, pruning, reachability, storage, or tests.

3. KIP status can be historical, current, or proposed. Core protocol source pages explain which subsystem owns the behavior. The reader should come away knowing whether the evidence belongs in params, constants, proof of work, header processing, body processing, virtual processing, DAA, pruning, reachability, storage, or tests.

4. params and constants close many activation claims. Core protocol source pages explain which subsystem owns the behavior. The reader should come away knowing whether the evidence belongs in params, constants, proof of work, header processing, body processing, virtual processing, DAA, pruning, reachability, storage, or tests.

5. release notes and source must agree before public current wording is used. Readiness pages are evidence gates. A testnet result is useful only with network name, date, release or branch, node/wallet/tool versions, and accepted evidence. Release notes and source paths support stronger claims; old testnet observations remain historical unless refreshed.

This mechanism section is a source checking guide. Each paragraph names the subsystem that owns the claim and keeps constants, params, pipelines, tests, releases, and KIPs in their own evidence lanes.

How to check it#

StepCheckEvidence gate
1Check DAA decides difficulty context from source-defined windows and parameters.Read RK-DAA, RK-PARAMS, RK-CONSTANTS; identify the exact Rusty Kaspa module, test, KIP, or release that owns this behavior.
2Check DAA score appears in activation and state discussions.Read RK-DAA, RK-PARAMS, RK-CONSTANTS; identify the exact Rusty Kaspa module, test, KIP, or release that owns this behavior.
3Check KIP status can be historical, current, or proposed.Read RK-DAA, RK-PARAMS, RK-CONSTANTS; identify the exact Rusty Kaspa module, test, KIP, or release that owns this behavior.
4Check params and constants close many activation claims.Read RK-DAA, RK-PARAMS, RK-CONSTANTS; identify the exact Rusty Kaspa module, test, KIP, or release that owns this behavior.
5Check release notes and source must agree before public current wording is used.Read RK-DAA, RK-PARAMS, RK-CONSTANTS; identify the exact Rusty Kaspa module, test, KIP, or release that owns this behavior.

When using this page for source review, start with the claim class, then read the owner module, tests, KIP or release context, and any dependent interface. Record what the source proves and what it does not prove before strengthening wiki wording.

  • pow-and-kheavyhash
  • core-protocol-source-path
  • pruning-and-pruning-proofs
Source-linkedReviewed 2026-07-09 · 6 public sourcesEvidence and sources
Evidence and sources6 public sources · reviewed 2026-07-09
Proof Of Work And kHeavyHashCore Protocol Source PathPruning And Pruning Proofs