In brief
Create the code-reading path for validation, proof of work, constants, difficulty, pruning, reachability, storage, and upgrade behavior.
What this page explains#
Create the code-reading path for validation, proof of work, constants, difficulty, pruning, reachability, storage, and upgrade behavior. 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-REPO, KIPS-REPO, RK-PARAMS, RK-CONSTANTS, RK-POW-KHEAVYHASH. 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 Core Protocol Source Path, the model is built around these anchors: Rusty Kaspa is the primary current implementation authority, but readers need a map before treating the repository as a flat list of files.; The consensus pipeline explains where headers, bodies, transactions, and virtual state are processed.; Proof of work gives blocks an objective work signal; kHeavyHash and header checks belong to source-backed mining and validation pages.; Difficulty adjustment and activation pages show how timing, work, and rule changes are checked against source and KIPs.; Pruning is about keeping enough evidence for security and synchronization while bounding stored history.. 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. Rusty Kaspa is the primary current implementation authority, but readers need a map before treating the repository as a flat list of files.. 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.
2. The consensus pipeline explains where headers, bodies, transactions, and virtual state are processed.. Virtual state is the bridge from ordered consensus consequences into the state surfaces that tools can inspect. Mempool visibility says a node is considering a transaction; accepted evidence says the transaction was incorporated through consensus processing. UTXO diffs, accepting data, and indexer replay are the review trail for applications that need durable state.
3. Proof of work gives blocks an objective work signal; kHeavyHash and header checks belong to source-backed mining and validation pages.. Mining and proof-of-work explanations belong to the node/miner path, not the ZK path. The node prepares candidate block templates from consensus and mempool state; mining hardware or pool software searches for acceptable work. Hardware catalogs and profitability references are volatile, while the durable protocol boundary is proof of work verification and template validity.
4. Difficulty adjustment and activation pages show how timing, work, and rule changes are checked against source and KIPs.. 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.
5. Pruning is about keeping enough evidence for security and synchronization while bounding stored history.. A node is useful only after its network, peer, sync, and index assumptions are understood. Process uptime is not the same as useful state. P2P handshake, IBD progress, logs, ports, and optional indexes each answer a different operator question, so troubleshooting starts by locating the failed layer rather than retrying commands blindly.
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#
| Step | Check | Evidence gate |
|---|---|---|
| 1 | Check Rusty Kaspa is the primary current implementation authority, but readers need a map before treating the repository as a flat list of files.. | Read RK-REPO, RK-PARAMS, RK-CONSTANTS; identify the exact Rusty Kaspa module, test, KIP, or release that owns this behavior. |
| 2 | Check The consensus pipeline explains where headers, bodies, transactions, and virtual state are processed.. | Read RK-REPO, RK-PARAMS, RK-CONSTANTS; identify the exact Rusty Kaspa module, test, KIP, or release that owns this behavior. |
| 3 | Check Proof of work gives blocks an objective work signal; kHeavyHash and header checks belong to source-backed mining and validation pages.. | Read RK-REPO, RK-PARAMS, RK-CONSTANTS; identify the exact Rusty Kaspa module, test, KIP, or release that owns this behavior. |
| 4 | Check Difficulty adjustment and activation pages show how timing, work, and rule changes are checked against source and KIPs.. | Read RK-REPO, RK-PARAMS, RK-CONSTANTS; identify the exact Rusty Kaspa module, test, KIP, or release that owns this behavior. |
| 5 | Check Pruning is about keeping enough evidence for security and synchronization while bounding stored history.. | Read RK-REPO, 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.
Expanded Category Guide#
This category carries implementation orientation. It should map concepts to Rusty Kaspa source areas without claiming that broad source IDs prove every exact branch.
Use this category as a curated path. Start with the category README to understand the boundary, then read the mechanism pages, then follow source-path or open-gap pages for claims that need stronger evidence. If a page contains needs checking rows, keep those claims visibly unresolved until a reader reads the cited public source directly.
The category should not be treated as final authority by folder name alone. The authority comes from page Source Notes, Source Lists, public URLs, and the status labels attached to each claim.
Related Pages#
- core-protocol-source-path
- rusty-kaspa-consensus-map
Topic pages#
- Rusty Kaspa Consensus Map: Rusty Kaspa is the primary current implementation authority, but readers need a map before treating the repository as a flat list of files.
- Header, Body, And Virtual Pipeline: The consensus pipeline explains where headers, bodies, transactions, and virtual state are processed.
- Proof Of Work And kHeavyHash: Proof of work gives blocks an objective work signal; kHeavyHash and header checks belong to source-backed mining and validation pages.
- DAA, Difficulty, And Activation: Difficulty adjustment and activation pages show how timing, work, and rule changes are checked against source and KIPs.
- Pruning And Pruning Proofs: Pruning is about keeping enough evidence for security and synchronization while bounding stored history.
- Reachability: Reachability answers ancestry questions in a DAG and supports GHOSTDAG, pruning, and validation work.
- P2P And IBD: P2P and initial block download connect a local node to the network and determine whether local evidence is useful.
- Storage, Indexes, And State Surfaces: Storage and indexes expose state to tools, but indexer observation is not itself consensus authority.
- Activation, KIPs, And Release Evidence: KIPs and upgrades are a status map, not an automatic statement of deployed behavior.
- Source Walkthrough Exercises: Exercises turn the Source List into contributor practice: trace one behavior from wiki claim to module to test evidence.
Topic notes#
This category is accepted when the subpages explain the actual topics, not merely the source links. Each subpage carries public source IDs, claim labels, Open Questions, and a path from first contact into source review.