Rusty Kaspa v2.0.0 gives the release and activation parameters. Post-activation node behavior and mainnet observations would move claims out of the pending lane.
Current status
Kaspa current status.
Kaspa is live as a mined UTXO network where a blockDAG and GHOSTDAG order parallel blocks. This page is scoped to L1 protocol status: live mainnet behavior, Toccata readiness, emissions, and roadmap boundaries.
Legend
Live
Targeted
Roadmap
Research
Not live
Checked: June 5, 2026. A public mainnet REST snapshot reported kaspa-mainnet, virtual DAA score 452,435,711, about 27.488 billion KAS from the supply endpoint, and a 2.59565436 KAS block reward. Toccata: Rusty Kaspa v2.0.0 is the mainnet release, scheduled to activate at DAA score 474,165,565, roughly June 30, 2026 at 16:15 UTC. It is released and scheduled, not activated yet.
Freshness triggers
What would change this page.
Observable accepted mainnet transactions using the new rules carry stronger evidence than testnet examples or roadmap posts.
Mainnet API readings, Rusty Kaspa releases, KIP states, and emission-schedule checkpoints should be refreshed before quoting exact values.
Use the Status Updates page for dated snapshots. Use this page for the current public wording standard.
Usable today
What users can do now.
Send, receive, and self-custody KAS on the live Proof-of-Work UTXO blockDAG.
Run or study nodes, explorers, visualizers, pruning behavior, and GHOSTDAG ordering.
Kaspa is ASIC-mined today; mining economics and distribution should be checked with current dashboards.
Wallet UX, payment flows, analytics, education, and infrastructure can use today's 10 BPS foundation.
Compare public REST readings with a node, release notes, KIP status, and accepted mainnet behavior before turning a snapshot into a claim.
Snapshot
Status in one table.
If you only remember one rule, remember the split: live mainnet behavior, testnet evidence, targeted upgrade work, roadmap architecture, and research are different statements.
PoW, UTXO, GHOSTDAG, Crescendo 10 BPS, and base real-time PoW framing.
Mainnet API readings showed virtual DAA score 452,435,711, about 27.488 billion KAS, and 2.59565436 KAS per block.
Emission steps down monthly. May 2026 is 27.5 KAS/sec; June 7 shifts to 25.9565436 KAS/sec. This is not a one-day July cliff.
| Feature / idea | Status | Plain meaning | Anchor source |
|---|---|---|---|
| Proof of Work | Live | Kaspa is mined. Work and issuance are external to any validator identity set. | rusty-kaspa |
| UTXO model | Live | Kaspa tracks spendable outputs; Ethereum tracks global account balances. | rusty-kaspa |
| GHOSTDAG | Live | The live ordering rule that lets parallel blocks contribute to consensus. | Kaspa Research |
| Crescendo 10 BPS | Live | The 10 blocks-per-second era is live. Michael Sutton framed practical throughput as roughly 8-9x higher and confirmation-time improvement around 30%, not instant finality or a clean 10x confirmation improvement. | rusty-kaspa releases; Crescendo roadmap note; Kaspa.org lore |
| June 5 L1 snapshot | Live snapshot | Public mainnet REST readout: virtual DAA 452,435,711; about 27.488 billion KAS from the supply endpoint; 2.59565436 KAS per block. Recheck before quoting exact numbers. | mainnet blockDAG API; supply API; block reward API |
| Emission schedule | Live design | The official schedule steps down monthly: 27.5 KAS/sec from May 8, 2026, 25.9565436 KAS/sec from June 7, and 24.49971475 KAS/sec from July 7. Avoid "July emission cliff" wording. | Kaspa Wiki tokenomics; block reward API |
| Base RTD framing | Live | Real-time decentralization is Hashdag's framing for Kaspa's core edge: Bitcoin-style PoW security and censorship-resistance goals with seconds-scale confirmation feel under normal network conditions. | Kaspa.org lore; hashd.ag/raw |
| Toccata | Targeted | Hard-fork track for L1 spend rules, asset rules, Silverscript, ZK proof checks, sequencing commitments, standalone based-zk applications, and vProgs groundwork. Rusty Kaspa v2.0.0 is released and schedules mainnet activation at DAA 474,165,565; current mainnet DAA remains below that activation score. | v2.0.0 release; Toccata guide; tn10-toc3 release; Kaspa KIPs |
| vProgs | Roadmap | Apps that prove richer logic while sharing Kaspa ordering, without turning L1 into one global execution VM. | vProgs talk |
| Native DeFi | Roadmap | A design target after Toccata-era L1 foundations, not a mature live Kaspa-native app layer today. | Why Kaspa |
| DAGKnight | Research | A major parameterless/adaptive consensus direction. It is not current mainnet behavior. | Kaspa.org lore; hashd.ag |
| 100 BPS / partition-resilient payments | Research | Kaspa.org now places 10 millisecond blocks, 100 BPS work, and partition-resilient local payment flows in a proposed 2027 hard-fork bucket. Treat this as roadmap/research until specifications, code, releases, and activation evidence exist. | Kaspa.org lore |
| RTD-derived oracle / TangVM flows | Research | Oracle, TangVM, attestation, and coordination-market systems can be built by apps over Kaspa primitives, but they are not protocol-prescribed products. | hashd.ag/raw |
Today
Current user actions.
Base network
Send and receive KAS, self-custody, use wallets and explorers, and experience the live high-rate blockDAG.
Infrastructure
Run nodes, study pruning, inspect mining, follow releases, and learn how GHOSTDAG orders the DAG.
Supply and reward
Check the public supply and block-reward endpoints when quoting current issuance. The June 5 check showed about 27.488 billion KAS and a 2.59565436 KAS block reward.
Upgrade evidence
Follow Rusty Kaspa releases, KIP PR states, activation parameters, and observed mainnet behavior. Testnet activation is useful evidence, not mainnet activation.
L1-first app work
The goal is not separate sequencer empires. Toccata gives L1 covenant and based-zk foundations; full vProgs later target shared Kaspa sequencing and synchronous composition.
Common misconceptions
Statements that need context or measurement.
Most confusion comes from mixing live protocol facts, test results, public targets, app headlines, project headlines, and research into one claim. Use these checks before repeating a Kaspa claim.
| Claim people repeat | Better version | Why it matters |
|---|---|---|
| Mainnet speed means a fixed huge TPS number. | 10 BPS is live. TPS depends on transaction size, policy, block capacity, fees, network conditions, and whether you mean test capacity or normal organic demand. | A single number can turn a real technical edge into a brittle marketing claim. |
| Block rate alone gives a clean finality multiplier. | Faster blocks improve inclusion and capacity. Confirmation confidence is a separate probabilistic question. | Users care about both when a payment appears and how confident they should be that it will not reverse. |
| Testnet or lab numbers are mainnet guarantees. | Testnets and experiments are useful signals. They need current source context before being used as live public claims. | Future capability, engineering tests, and shipped network behavior should not be flattened. |
| Real-time means instant finality. | Real-time is the fast-PoW user-feel and decentralization frame. It is not a claim that every transaction is instantly irreversible. | This keeps the pitch strong without overselling settlement certainty. |
| DAGKnight, Toccata, vProgs, or native DeFi are live because code or talks exist. | Code, talks, branches, and demos are evidence of work. Activation or production status needs stronger primary evidence. | Development evidence is useful, but it belongs below release or activation evidence. |
| Toccata means one atomic action can already span several independent apps. | Toccata is the foundation for covenant rules, ZK proof checks, sequencing commitments, and based-zk applications. Full cross-app atomic composition belongs to later vProgs. | Fast L1 coordination and same-operation app composability are different claims. |
| July 2026 is a sudden emission cliff. | Kaspa emission steps down monthly. The official schedule shows 27.5 KAS/sec from May 8, 25.9565436 from June 7, and 24.49971475 from July 7. | The scarcity story should use the actual schedule instead of a dramatic one-day cliff claim. |
| Open KIPs or branches prove an upgrade is activated. | Open KIPs, branches, and pre-releases are development evidence. Activation needs release artifacts, activation parameters, upgraded node behavior, and observable mainnet behavior. | This keeps the upgrade story grounded in primary L1 evidence instead of roadmap momentum. |
Implementation evidence
Code evidence.
Code and pull requests are not activation records. They are useful for seeing what is being tested, polished, or prototyped before a public status label changes.
Open code and implementation evidence
| Track | Recent public evidence | How to read it |
|---|---|---|
| Toccata / Silverscript | TN12 dependency sync, KCC20 bootstrap fixes, and book/build fixes landed May 4-5, 2026. TN12 field testing surfaced developer-ergonomics issues around covenant and ZK opcode use. The v1.3.0-toc.5 pre-release sanity-tested mainnet pre-activation compatibility. The v2.0.0 release schedules mainnet activation at DAA score 474,165,565. The tn10-toc3 pre-release scheduled final TN10 hardening; a June 5 check of Testnet-10 REST status showed virtual DAA 483,034,659. | Released and scheduled. Toccata is not live until mainnet reaches the activation score and post-activation behavior is observable. Current evidence includes release notes, activation parameters, TN10/TN12 testing, and SDK/tooling preparation. |
| Toccata KIPs | Kaspa.org Build lists sequencing commitments in the Toccata bundle and labels it live on TN12 ahead of mainnet activation. Raw KIP checks on June 5 showed KIP-16 and KIP-20 as proposed plus implemented and activated in TN10, and KIP-17 and KIP-21 as implemented and activated in TN10. | Targeted design and testnet implementation evidence. TN10 KIP status does not make Toccata live on mainnet; mainnet wording still waits for activation and observable post-activation behavior. |
| vProgs | The kaspanet/vprogs repo had an April 15, 2026 implementation burst: RISC0 backend, ZK VM, transaction and batch provers, ABI, codec, and Sparse Merkle Tree work. | Roadmap implementation progress. Builders can study and experiment with the framework. Production Kaspa app paths and native DeFi need separate shipped evidence. |
| DAGKnight | The public rusty-kaspa dagknight branch shows March 22, 2026 commits for free-search support, ranking/search refinements, conflict-zone work, tie-breaking placeholder, and UMC majority-coverage movement. | Research and prototype evidence. Current mainnet behavior remains GHOSTDAG; live finality and higher-BPS claims need separate activation evidence. |
| Builder tooling | kaspanet/kaspa-python-sdk is now a standalone public SDK repo. The v1.1.0 release added GetVirtualChainFromBlockV2 plus UtxoProcessor and UtxoContext bindings, with a versioned changelog and generated documentation. | Developer-tooling progress, not a protocol upgrade. It helps Python builders track UTXOs and integrate with Kaspa, while protocol status still comes from node, KIP, and activation evidence. |
| Infrastructure indexes | rusty-kaspa PR #860 is open for review. It proposes an optional --txindex, a GetTransaction RPC path, inclusion and acceptance metadata, live updates from consensus notifications, resync from scratch, and pruning tied to retention-root changes. |
Builder and infrastructure work. It could help wallets, explorers, indexers, and large app-state workflows. It remains an open pull request until merged and released. |
Builder note: early tests and open PRs are useful signals for developers. They stay below release or activation evidence until a primary artifact changes the status.
Changelog
Status-sensitive updates.
Open status changelog
May 4, 2026
Separated base RTD framing from downstream oracle, TangVM, and coordination-market ideas. Base RTD is treated as Hashdag's real-time PoW framing for Kaspa; RTD-derived app systems remain app-level research or architecture work.
May 4, 2026
Marked Toccata as targeted with the then-current mid-June public window. This was later superseded by the June 5 v2.0.0 release, which schedules activation at DAA score 474,165,565.
May 5, 2026
Added the Crescendo nuance: 10 BPS is separate from confirmation improvement. Public summaries should distinguish roughly 8-9x throughput improvement from faster, still probabilistic, confirmation dynamics.
May 5, 2026
Clarified why Toccata moved from the older May 5 target: sequencing commitments needed to be finalized before zk systems and runtimes depend on them. The current release source is now v2.0.0.
May 6, 2026
Added code-grounded implementation evidence for the Toccata/Silverscript, vProgs, and DAGKnight tracks. These notes describe current development; activation status still comes from release and network evidence.
May 6, 2026
Added Python SDK and TxIndex as builder/infrastructure evidence. These help developers and indexers while leaving protocol status unchanged.
May 15, 2026
Added the redesigned Kaspa.org source frame: real-time decentralization as the official north star, Toccata next, DAGKnight after Toccata, and 2027 work around 100 BPS plus partition-resilient payment flows. Kept 100 BPS and partition-resilience in the research/roadmap lane.
May 15, 2026
Added KIP-21 and infrastructure notes from the current source list. Sequencing commitments are targeted/TN12 evidence, while production API/indexer choices remain builder-infrastructure decisions.
May 18, 2026
Updated TN10 wording after checking the Testnet-10 REST API. TN10 had passed the tn10-toc2 activation score, which is useful testnet evidence and still not mainnet activation evidence.
May 20, 2026
Refreshed the page as an L1-only status check. Added mainnet API readings, block reward, supply, smooth emission-schedule wording, TN10/Toccata status, and open KIP guardrails; removed app and project tooling from the main status table.
June 2, 2026
Refreshed mainnet API readings and Toccata guardrails. Added tn10-toc3 final TN10 hardening evidence and TN10 KIP status while keeping mainnet activation in the pending lane.
June 5, 2026
Updated the Toccata boundary after Rusty Kaspa v2.0.0 was released. The release schedules mainnet activation at DAA score 474,165,565, roughly June 30, 2026 at 16:15 UTC. Current mainnet DAA is still below that score, so the safe status is released and scheduled, not activated.
FAQ
Common status questions.
Is DAGKnight live?
No. DAGKnight is a parameterless/adaptive consensus upgrade direction, not current mainnet behavior.
Is Toccata live?
No. Rusty Kaspa v2.0.0 has been released and schedules activation at DAA score 474,165,565, roughly June 30, 2026 at 16:15 UTC. Current mainnet DAA is still below that score, so Toccata remains scheduled rather than activated.
Are Kaspa smart contracts live?
Not as mature Kaspa-native programmability on mainnet. The near-term path runs through Toccata, spend rules, asset rules, ZK proof checks, sequencing commitments, and later vProgs.
Are cross-app actions live?
Not as full atomic app-to-app composition. Toccata can improve fast, verifiable coordination through L1 foundations; later vProgs target richer actions across app boundaries.