Proof of Work, UTXO ownership, blockDAG structure, GHOSTDAG ordering, and Crescendo-era 10 BPS mainnet.
Dated status check
Kaspa status check - May 2026.
This is the current snapshot for people checking what is live, what changed, what remains roadmap, and which Kaspa claims need tighter wording.
Last checked: May 15, 2026. Status-sensitive claims should be refreshed after Toccata activation evidence, release notes, or new primary source updates.
Snapshot
What is live now.
Wallets, transfers, mining, explorers, nodes, public APIs, and the normal live payment path.
KRC20 and KRC721-style tooling can support token, coupon, access-pass, reward, and collectible workflows around Kaspa data.
What changed
New source notes to add.
The redesigned Kaspa.org now makes real-time decentralization the public north-star framing, not just a community shorthand.
Kaspa.org presents Toccata next, DAGKnight after Toccata, and a separate proposed 2027 hard-fork bucket for 100 BPS and partition-resilient payment work.
KIP-21 sequencing commitments remain a status-sensitive Toccata item. Treat TN12 and proposal evidence as useful, but wait for release and activation artifacts before mainnet wording changes.
REST APIs, public nodes, archival/indexer paths, and transaction-history access are now a clearer builder/adoption watch item, not just background plumbing.
Current watchlist
What is pending or later.
| Track | Status | What to verify next |
|---|---|---|
| Toccata | Targeted | TN12 state, audit/rehearsal, branch merge, release notes, activation parameters, and observable mainnet behavior. |
| Smart contracts/native app rules | Targeted | Use Toccata evidence for covenant-style L1 rules; avoid mature native DeFi claims until product evidence exists. |
| vProgs | Roadmap | Watch framework progress, developer examples, proof paths, and later activation evidence. |
| DAGKnight | Research | Watch research and implementation branches; do not call it current mainnet consensus. |
| 100 BPS / partition-resilient payments | Research | Watch for specifications, code, test evidence, and activation records before treating the proposed 2027 bucket as a shipped path. |
| RTD-derived oracle/TangVM flows | Research | Require concrete app designs, incentives, anchors, proofs, and accepted evidence. |
Claims corrected
Loose wording to avoid this month.
Say fast inclusion and probabilistic confirmation confidence.
Say targeted hard-fork track with TN12 testing until mainnet activation evidence exists.
Say ecosystem tooling around Kaspa data, not native L1 smart contracts.
Say research and upgrade direction, not current mainnet behavior.
Say 10 BPS is live; 100 BPS is a proposed future hard-fork/research bucket.
Say roadmap; real DeFi also needs wallets, liquidity, custody, oracles, risk controls, and users.
Use the verification ladder: explorer, second source, wallet/software, node or accepted-transaction evidence.