Fact check
Kaspa claims checker
Most bad Kaspa claims come from one mistake: blending testnet work, roadmap design, and live mainnet behavior into a single sentence. The table below pulls them back apart.
This page covers protocol claims. Product and app pitches go to Status. A demo, txid, repo, or testnet artifact offered as proof goes to Build on Kaspa.
Last checked: August 1, 2026 against release tags, raw KIP files, project READMEs, and mainnet readings. Recheck at emission checkpoints, after new primary sources, or when wallet/app/tooling support changes.
Common claims
Live, roadmap, research, or not yet?
| Claim | Status | Best wording | Source path |
|---|---|---|---|
| Kaspa is proof-of-work | Live | Kaspa is mined, proof-of-work, full stop. | rusty-kaspa |
| Kaspa is a blockDAG using GHOSTDAG | Live | GHOSTDAG orders parallel blocks into one history instead of discarding the losers. | GHOSTDAG page |
| Kaspa is 10 BPS | Live | 10 blocks per second, the Crescendo-era rate. | releases |
| Kaspa already runs at 100 BPS | Research | 10 BPS is live. Kaspa.org puts 100 BPS in a proposed 2027 hard-fork/research bucket. | Kaspa.org lore |
| Kaspa payments become irreversible immediately | Wrong | Inclusion is fast; confirmation confidence rises probabilistically over time. | finality page |
| Toccata has activated on mainnet | Live protocol | Toccata is live, activated at DAA 474,165,565; v2.0.1 is the current release. App, wallet, explorer, SDK, and user adoption are separate, still-open checks. | Toccata page |
| TN10 Toccata test means mainnet activation | Testnet only | tn10-toc2, tn10-toc3, and the Testnet-10 DAA evidence are testnet-only. v2.0.0 is what set the mainnet activation score. | v2.0.0 activation release |
| TN12 proves mainnet covenants | Testnet only | Covenants are live on mainnet, but TN12 is not why. That claim rests on the v2.0.0 activation score; TN12 is testnet prototyping evidence. | status |
| Kaspa has mature native smart contracts | Not yet | Toccata shipped the covenant and proof-check layer; mature native DeFi and full app infrastructure are still ahead, through later vProgs work. | smart-contract status |
| July 2026 is a sudden emission cliff | Misleading | Emission steps down by a fixed factor every 2,629,800 seconds. Steps fire on DAA score, so quote the score: 24.49971474 KAS/sec from 478,611,000, then 23.12465141 from 504,909,000, which the network passed around August 5, then 21.82676446 from 531,207,000. | tokenomics |
| DAGKnight is current mainnet consensus | Research | DAGKnight is the consensus upgrade after Toccata, and it has a published paper and a prototype branch behind it. What it does not have is a merge: KIP-2 still reads Status: Proposed and the branch has not moved since March 22. Mainnet ordering runs GHOSTDAG. | KIP-2 raw file |
| vProgs have shipped as production app infrastructure | Roadmap | The repo calls itself early development and prototype phase, and it has zero releases and zero tags. Its tn10-flow example runs the flow against a private testnet-10 fork node, not the public one. A live Kaspa-native app layer needs its own shipped-product evidence. | vprogs repo |
| Argent proves Kaspa smart contracts are production-ready | Research | Argent's own README says the main pieces are present: compiler, generated Silverscript, portable artifacts, runtime transaction building, multi-actor routing, and closed and open ICC. What it does not have is an audit. Silverscript has to finish its own audit first, then Argent needs hardening of its own, and nothing here has run on mainnet. | Argent README |
| Native DeFi has shipped as a mature Kaspa L1 product layer | Roadmap | Kaskad/Igra-style L2 lending is ecosystem context around Kaspa, separate from native L1 DeFi. Native L1 DeFi still needs its own app primitives, wallets, liquidity, custody, risk controls, and users. | app layer |