The one paragraph summary: blockchains cap throughput to protect security, so Kaspa replaced the chain with a blockDAG where parallel blocks all count; GHOSTDAG orders the DAG and penalizes badly connected blocks; confirmations accumulate ~10 per second against the backbone chain; pruning and per-block difficulty adjustment keep a 10 BPS network runnable at home; mining pays every honest block under a smoothly halving emission; the UTXO model makes merging parallel blocks tractable; and two hard forks took the network to 10 BPS and then made it programmable.
Topics
- Basics - What is Kaspa? and Why Kaspa Exists: orientation, and the throughput-security problem Kaspa was built to solve.
- BlockDAG - the structure itself, GHOSTDAG ordering, confirmations & finality, pruning, and DAGKnight ahead.
- Mining - proof of work in a DAG, the difficulty adjustment, and the chromatic emission schedule.
- Transactions - the UTXO model, P2SH, and PSKT & PSKB.
- Upgrades - the two named hard forks: Crescendo (throughput) and Toccata (programmability).
- Programmability - the overview, Covenants++, SilverScript, Zero Knowledge, and VProgs.
Build
- Developer Resources - SDKs, node RPC, tooling.
- Build a Transaction - the UTXO model, in code.
New here? Start with What is Kaspa?, then follow the pages in order from Why Kaspa Exists.