Kaspa (KAS)

Promise

Kaspa's Rust node documentation reports a historical increase in block rate through the Crescendo upgrade. The useful research question is what that reported rate describes and which independent observations would be needed to assess the network's current operation. This dossier reviews the node's documentation and its stated testing boundaries.

Established facts

The supplied evidence identifies a pinned Rust full-node implementation called rusty-kaspa, which serves as a replacement for an earlier Go node. This software includes associated libraries and distinguishes between an actively developed master branch and a stable branch corresponding to a stable release. The documentation reports that the Crescendo hard fork occurred on May 5, 2025, around 15:00 UTC. This event changed the stated block rate from 1 to 10 blocks per second. A block rate refers to the frequency at which new blocks are added to the chain; it does not measure transaction throughput, final settlement speed, wallet performance, or investment outcomes. The README also describes a UTXO index, where UTXO stands for unspent transaction output, a data structure tracked by wallet software. Additionally, the codebase contains an in-process DAG simulation. A directed acyclic graph is a mathematical structure used here to model virtual blocks. The examples provided for virtual delay in this simulation do not reflect observed mainnet behavior. No client or simulation was executed during this review. Current hashrate, miner independence, consensus implementation, deployed versions, usage patterns, supply distribution, ownership concentration, liquidity conditions, and complete incident history remain unknown based on the supplied materials.

Unknowns

The reported Crescendo transition and block rate were not independently replayed or measured here. Current deployed versions, consensus implementation, hashrate and miner independence also remain unknown within the gathered evidence.

The simulation examples describe virtual conditions, without observed mainnet results. Actual use, token supply, ownership, liquidity and the complete incident record lack dated independent evidence in this dossier. No node or simulation was executed during the review.

Consequences

A stated block rate describes how often blocks are produced. Measuring transaction throughput, settlement behavior or wallet experience would require separate observations with explicit conditions. The historical increase alone supplies no investment-return estimate.

The distinction between development and stable branches helps identify the software version to test. Mainnet, testnet and virtual simulation evidence also require their own scopes. Results from a virtual-delay example would need separate validation before informing a conclusion about live network behavior.

Verdict

Unrated, with 0% coverage of the scoring criteria. The Rust implementation and historical upgrade are documented as maintainer statements. Current network operation remains unproven within this review, and the coverage percentage records the absence of admitted scoring observations.

What would change it

A dated identity check and an independently reproduced examination of deployed software would establish a clearer operational scope. Live block observations, mining-participation evidence and explicitly scoped throughput tests could examine the relevant claims. Economic and incident evidence would then require calibration and editorial review before a rating.