Kaspa

Can this project keep operating and funding itself for years?

Kaspa's official material describes a proof-of-work BlockDAG operating at 10 blocks per second and a fair-launch model. Those durable design claims support viability, though public materials do not establish long-term fee-demand metrics.12

Can outsiders see and check what the team and the protocol do?

Kaspa publishes open-source Rust code and builder documentation covering Toccata capabilities, though the official lore page and builder page use inconsistent wording on Toccata deployment status.134

Does the protocol earn real fees or income from use?

Not applicable: kAS is assessed as a Store of Value asset; network fees go to proof-of-work miners and do not establish protocol-level revenue accruing to KAS holders. Weight 0.00 in the monetary profile, so it neither lifts nor lowers the score.

Is the technology being built and shipped, and does it matter?

Kaspa combines 10-blocks-per-second GHOSTDAG proof-of-work operation with documented programmable UTXOs, covenants, transaction introspection, zero-knowledge verification, and sequencing support.34

Who uses, builds and holds it, and how durable is that base?

Official Kaspa material and open-source repositories show an active PoW miner and builder ecosystem, though public sources provide limited independently verified active-application metrics.35

Do supply, issuance and unlocks protect holders from dilution?

Kaspa's official lore page documents a fair launch without a pre-mine or insider token allocation, supporting distribution fairness and bounded emission dilution.15

1. 1kaspa.org/loreCited for Sustainability, Transparency, Tokenomics
2. 2kaspa.org/featuresCited for Sustainability
3. 3kaspa.org/buildCited for Transparency, Innovation, Community
4. 4github.com/kaspanet/rusty-kaspaCited for Transparency, Innovation
5. 5coingecko.com/en/coins/kaspaCited for Community, Tokenomics

The Kaspa thesis rests on combining proof-of-work security, BlockDAG concurrency at 10 blocks per second, and UTXO-native programmability. Official builder documentation identifies covenants, transaction introspection, zero-knowledge verification, and sequencing support as core Toccata capabilities.

• High-throughput PoW BlockDAG. Official materials document GHOSTDAG consensus operating at 10 blocks per second without orphan blocks.
• Fair-launch token distribution. Kaspa launched with zero pre-mine, zero venture allocation, and a transparent emission schedule.
• Programmable UTXO architecture. Builder documentation covers covenants, transaction introspection, zero-knowledge verification, and L2 sequencing.
• Rust client maturity. The Rusty Kaspa codebase supports high block rates and peer-to-peer concurrency across the validator and miner network.

• Documentation status ambiguity. Official Kaspa pages use conflicting wording on whether Toccata features are fully live or part of the next hard fork.
• Limited adoption telemetry. Public materials describe technical capabilities rather than independently verified application usage or economic demand.
• Expanded technical surface. Adding covenants and ZK verification to a UTXO network increases complexity and requires sustained production testing.
• Proof-of-work market sensitivity. Miner economics and KAS market valuation remain exposed to hash-price swings and crypto-market volatility.

Kaspa competes among proof-of-work networks by pairing GHOSTDAG 10-blocks-per-second throughput with UTXO-native programmability. Rather than copying account-based EVM chains, it focuses on covenants, transaction introspection, and zero-knowledge verification atop a fair-launch PoW base layer.

Kaspa pairs a distinctive 10-blocks-per-second proof-of-work BlockDAG design with programmable UTXO capabilities under Toccata. While fair-launch tokenomics and GHOSTDAG engineering support its technical credibility, inconsistent official status documentation and sparse application-adoption data temper conviction.