Kaspa’s Block-DAG Proof-of-Work Design and Governance
Summary
The document explains Kaspa’s use of a directed acyclic graph instead of a single linear block chain. It says this design allows blocks to be produced and processed in parallel, paired with asynchronous proof of work, and presents these features as a way to increase throughput while retaining a proof-of-work consensus model. It also describes the project’s emission approach, mining hardware ambitions, proposed DAGKnight upgrade, and roadmap topics such as zero-knowledge virtual machines and social recovery.
The article frames these design choices as supporting scalability, security, decentralization, and community governance. Its evidence is largely descriptive and attributed to the project or its proponents; it does not provide benchmarks, comparative security analysis, implementation status for planned features, or independent validation of the claims about energy efficiency and miner extractable value resistance. Readers should distinguish the described current design from upcoming roadmap items and treat claims of superiority over other networks as unverified within this document.
Key ideas
- Kaspa uses a block-DAG structure that permits multiple blocks to coexist and be processed in parallel.
- The article presents asynchronous proof of work as an alternative to a longest-chain approach.
- Kaspa’s emission schedule and community-led development are described as part of its distribution and governance model.
- DAGKnight, zero-knowledge virtual machines, and social recovery are presented as planned or upcoming capabilities.
- The document offers project-level claims without independent benchmarks or security comparisons.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.