Status updates
Use these when you need a current snapshot instead of a timeless explainer: what is live, what changed, what remains roadmap, and which claims need checking.
Latest
L1-focused May status check with a June 29 follow-up: mainnet API state, block reward, supply, emission schedule, v2.0.1/v2.0.0 Toccata release status, TN10/TN12 boundary, KIP status, Argent, vProgs, ZK SDK, Python SDK, quantum-resistance proposal context, DAGKnight, and common overclaim corrections.
Compact live mainnet / testnet / targeted / roadmap / research / wrong / unsupported table for major Kaspa claims.
Use this when an exact claim needs a status label and copyable wording.
Update format
| Section | Question |
|---|---|
| Live now | What can a user, node operator, wallet, miner, or builder verify today? |
| Changed since last update | What releases, KIPs, testnet events, mainnet API readings, emission checkpoints, or source updates changed the status? |
| Still open | What needs mainnet release, activation parameters, upgraded-node behavior, accepted mainnet evidence, or audit evidence? |
| Claims to clean up | Which repeated public claims need safer wording? |
| Source links | Which first-party L1 sources support the update: GitHub releases, KIPs, Kaspa.org/docs, public node/API readings, research, or activation artifacts? |