Claims

Kaspa claims checker

Kaspa claims fail when testnet work, roadmap design, and live mainnet behavior get blended together. Label the claim before repeating it.

Use this for protocol claims. Use Reality Check for product or app pitches. Use Builder Evidence when a demo, txid, repo, or testnet artifact is being used as proof.

Summary: Describe Kaspa by status: live PoW blockDAG, post-activation Toccata work, roadmap vProgs/native app paths, and research such as DAGKnight. App/project claims are outside this site's status labels unless L1 transaction evidence itself is the point.

Last checked: June 30, 2026. Recheck at emission checkpoints, after new primary sources, or when wallet/app/tooling support changes.

Common claims

Live, roadmap, research, or not yet?

ClaimStatusBest wordingSource path
Kaspa is proof-of-workLiveKaspa is a mined proof-of-work network.rusty-kaspa
Kaspa is a blockDAG using GHOSTDAGLiveKaspa uses GHOSTDAG to order parallel blocks into one history.GHOSTDAG page
Kaspa is 10 BPSLiveKaspa is in the Crescendo-era 10 BPS network.releases
Kaspa already runs at 100 BPSResearch10 BPS is live; Kaspa.org places 100 BPS in a proposed 2027 hard-fork/research bucket.Kaspa.org lore
Kaspa payments become irreversible immediatelyWrongKaspa has fast inclusion and probabilistic confirmation confidence.finality page
Toccata has activated on mainnetLive protocolToccata v2.0.1 is the current Toccata release; v2.0.0 set activation at DAA 474,165,565. App, wallet, explorer, SDK, and user evidence remain separate checks.Toccata page
TN10 Toccata test means mainnet activationTestnet onlyThe tn10-toc2 and tn10-toc3 releases plus Testnet-10 DAA evidence are testnet-only evidence. v2.0.0 set the mainnet activation score.v2.0.0 activation release
TN12 proves mainnet covenantsTestnet onlyTN12 evidence is testnet evidence; mainnet claims need the activation score and mainnet evidence.status
Kaspa has mature native smart contractsNot yetKaspa's programmability route runs through Toccata and later vProgs; mature native DeFi is not live.smart-contract status
July 2026 is a sudden emission cliffMisleadingKaspa emission steps down monthly; quote the monetary-policy schedule instead of a one-day cliff.tokenomics
DAGKnight is current mainnet consensusResearchDAGKnight is a future consensus direction. Current mainnet behavior uses GHOSTDAG.dagknight branch
vProgs have shipped as production app infrastructureRoadmapvProgs are roadmap architecture and early framework work. Mature live Kaspa-native app-layer claims need shipped product evidence.vprogs repo
Argent proves Kaspa smart contracts are production-readyResearchArgent is experimental actor-style frontend work for Silverscript covenant contracts. It is research/tooling evidence. Audit, stable ABI, transaction-builder, production, and activation claims need separate evidence.Argent repo
Native DeFi has shipped as a mature Kaspa L1 product layerRoadmapKaskad/Igra-style L2 lending can be ecosystem DeFi context, but native Kaspa L1 DeFi still depends on future app primitives, wallets, liquidity, custody, risk controls, and users.app layer

Wording

Copyable answers

Newcomer

Kaspa is a live proof-of-work blockDAG. GHOSTDAG orders parallel blocks into one payment history.

Toccata

Toccata activated at DAA 474,165,565. Treat TN10/TN12 evidence as testnet evidence; use mainnet DAA and upgraded-node behavior for the mainnet label.

Finality

Kaspa has fast inclusion and increasing confirmation confidence. Irreversibility still depends on confirmation depth and risk tolerance.

Emission

Use monthly step-down wording: 27.5 KAS/sec from May 8, 25.9565436 from June 7, and 24.49971475 from July 7.

L1 scope

Do not use market listings, app demos, or project tools as evidence that L1 rules have activated.

Sources

Use releases, code, KIPs, docs, research, and observable network evidence before changing a live-status claim.

Next checks

Answer the exact question