Rusty Kaspa v2.0.1 is the current Toccata release. v2.0.0 set activation at DAA 474,165,565. The next checks are upgraded-node behavior, accepted v1 transactions, wallet support, explorer support, SDK support, app receipts, and user activity.
Current status
Kaspa current status
Kaspa is a live mined UTXO network. Its blockDAG lets honest blocks appear in parallel; GHOSTDAG orders them into one history. Live L1 behavior and roadmap work need separate labels.
Legend
Live
Targeted
Roadmap
Research
Not live
Checked: June 30, 2026 at 16:19 UTC. Public mainnet REST checks reported kaspa-mainnet, virtual DAA above the activation score, matching block and header counts, about 27.545 billion KAS from the supply endpoint, and a 2.59565436 KAS block reward. Toccata: Rusty Kaspa v2.0.1 is the current Toccata release; v2.0.0 set activation at DAA score 474,165,565. Use Toccata status for post-activation checks.
Freshness triggers
What would change this page
Observable accepted mainnet transactions using the new rules carry better 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 Status Updates for dated snapshots. Use this status 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. Use the solo mining guide for miner-to-node setup; use current dashboards for mining economics and distribution.
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 473,005,279, 1,102,009 blocks, about 27.542 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 throughput as roughly 8-9x higher and confirmation-time improvement around 30%. Instant-finality claims and exact 10x confirmation-improvement claims overstate that source. | rusty-kaspa releases; Crescendo roadmap note; Kaspa.org lore |
| June 29 L1 snapshot | Live snapshot | Public mainnet REST readout at 16:19 UTC: virtual DAA above 474,165,565; matching block and header counts; about 27.545 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 | Live protocol | 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.1 is the current Toccata release; v2.0.0 set mainnet activation at DAA 474,165,565. | v2.0.1 release; v2.0.0 activation 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 repo; programmability docs |
| Native DeFi | Roadmap | A design target after Toccata-era L1 foundations. Mature live Kaspa-native app-layer claims need shipped app and usage evidence. | Design case |
| 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 |
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 | Measured version | Consequence |
|---|---|---|
| Mainnet speed means a fixed huge TPS number. | 10 BPS is live. Simple-payment capacity is roughly 2.5k to 3.4k TPS under transaction-shape assumptions, while covenant apps, ZK proofs, tokens, and vProg-style systems need their own workload labels. See Kaspa TPS Explained. | A single number can turn a real technical edge into a brittle marketing claim. |
| Block rate alone gives an exact 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 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 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 implementation evidence. Mainnet labels come from releases, activation records, upgraded-node behavior, and observable network behavior.
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 sets mainnet activation at DAA score 474,165,565; v2.0.1 is the current Toccata release. The Toccata node setup guide adds operator guidance for upgrades, fee policy, API field changes, and Testnet-10 checks. The merged Rusty Kaspa ZK SDK PR adds an R0ScriptBuilder wrapper for turning RISC Zero receipts into Kaspa scripts. The tn10-toc3 pre-release scheduled final TN10 hardening; a June 29 check of Testnet-10 REST status showed virtual DAA 503,616,667. |
activated mainnet release evidence. Current evidence includes release notes, activation parameters, the operator guide, TN10/TN12 testing, and SDK/tooling preparation. After activation, track wallets, explorers, examples, and accepted mainnet transactions. |
| 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 29 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. Open KIP PRs add important future context: KIP-24 specifies transaction version 1 fields and hashing for compute budgets, covenant bindings, user lanes, and ZK-friendly payload/rest txids; KIP-22 proposes P2MR ScriptPublicKey work for quantum-resistance and MAST-style scripts. | Design and testnet implementation evidence. TN10 KIP status does not set the mainnet label by itself; mainnet wording follows the activation record and observable network behavior. |
| Open KIP PRs | KIP-24 is open for transaction version 1 fields and hashing; its draft text says v1 transactions add per-input compute budgets, optional output covenant bindings, user-lane subnetworks, and a BLAKE3 payload/rest txid split for ZK and based-executor workflows. KIP-22 is open for P2MR ScriptPublicKey, described as a Merkle-root pay-to-script form meant to hide public keys until spend time and support quantum-resistance and MAST-style conditional scripts. | Design and implementation evidence. Merged-KIP and mainnet activation claims need separate evidence. KIP-24 is closer to Toccata transaction plumbing; KIP-22 is future cryptography/script-design work. |
| Argent | michaelsutton/argent is a June 2026 experimental actor-style frontend for Silverscript covenant contracts. Its README describes actors, state, transitions, named emits, terminal become dispatch, and generated Silverscript for examples such as Stones and Tickets. |
Fresh research/tooling evidence. It is explicit prototype work. Audit, production readiness, stable ABI, generated transaction builder, launch-proof tooling, and mainnet activation evidence remain absent. |
| vProgs | The kaspanet/vprogs README describes an early-development Rust framework for based computation on Kaspa, with core, storage, state, scheduling, transaction-runtime, and node layers. A June 18 merge, Feat: Settlement into Covenants, gathered settlement-covenant work, transaction/batch/aggregation provers, SMT support, L1 bridge plumbing, and RISC Zero backend work into master. | Roadmap implementation progress. Builders can study and experiment with the framework. Production Kaspa app paths and native DeFi need separate shipped evidence. See vProgs Explained. |
| 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 v2.0.0 release added Toccata-aligned support and the full Rusty Kaspa managed-wallet API for Python. The v2.0.1 release adds get_seq_commit_lane_proof, SMT sync progress events, covenant-binding fixes, and a Rusty Kaspa v2.0.1 dependency bump. |
Developer-tooling progress. Protocol-upgrade status still comes from node, KIP, and activation evidence. It helps Python builders and integrators prepare for Toccata-era wallet, UTXO, lane-proof, and covenant workflows. |
| 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 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 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 activation remains scheduled.
June 15, 2026
Refreshed the mainnet REST snapshot to virtual DAA 461,207,885, 1,403,205 blocks, about 27.511 billion KAS, and 2.59565436 KAS per block. Added a dedicated vProgs explainer and updated the vProgs evidence boundary from a commit-burst note to the current public README architecture.
June 20, 2026
Refreshed the mainnet snapshot to virtual DAA 465,403,885, 1,277,659 blocks, about 27.522 billion KAS, and 2.59565436 KAS per block. Updated Toccata wording for Rusty Kaspa v2.0.1 while keeping v2.0.0 as the activation-parameter source. Added Argent as early Silverscript research/tooling evidence.
June 21, 2026
Refreshed the mainnet snapshot to virtual DAA 466,400,699, 1,410,360 blocks, about 27.524 billion KAS, and 2.59565436 KAS per block. Added the Rusty Kaspa Toccata node setup guide as operator and integrator evidence for upgrades, fee policy, API field changes, pools, miners, exchanges, wallets, explorers, and Testnet-10 checks.
June 23, 2026
Refreshed the mainnet snapshot to virtual DAA 467,931,952, 1,213,420 blocks, about 27.528 billion KAS, and 2.59565436 KAS per block. Rechecked the Rusty Kaspa release API, Toccata guide, KIP-16/17/20/21 raw files, Testnet-10 REST status, vProgs README, and Argent README.
June 25, 2026
Refreshed the mainnet snapshot to virtual DAA 469,680,863, 1,234,055 blocks, about 27.533 billion KAS, and 2.59565436 KAS per block. Added Python SDK v2.0.0/v2.0.1, merged Rusty Kaspa ZK SDK PR #953, vProgs settlement-into-covenants PR #36, open KIP-24 transaction-v1/ZK-prover context, open KIP-22 P2MR quantum-resistance context, and the Toccata Explained route.
June 29, 2026
Refreshed the mainnet snapshot to virtual DAA 473,005,279, 1,102,009 blocks, about 27.542 billion KAS, and 2.59565436 KAS per block. Rechecked Rusty Kaspa v2.0.1/v2.0.0, the Toccata guide, Testnet-10 REST status, KIP-16/17/20/21 raw files, vProgs README, Argent README, and kaspa-python-sdk releases; no mainnet activation status change. After the activation score, scheduled wording should change only where the DAA target and post-activation behavior support it.
June 26, 2026
Refreshed the mainnet snapshot to virtual DAA 470,805,556, 1,494,605 blocks, about 27.536 billion KAS, and 2.59565436 KAS per block. Rechecked Rusty Kaspa v2.0.1, Testnet-10 REST status, KIP-16/17/20/21 raw files, KIP-24, and KIP-22; no mainnet activation status change.
FAQ
Common status questions
Is DAGKnight live?
No. DAGKnight is a parameterless/adaptive consensus upgrade direction. Current mainnet behavior uses GHOSTDAG.
Is Toccata live?
Toccata activated at DAA 474,165,565. Rusty Kaspa v2.0.1 is the current Toccata release, and v2.0.0 set the activation parameters. Use Toccata status for post-activation checks before quoting app or tooling state.
Are Kaspa smart contracts live?
No mature Kaspa-native programmability on mainnet yet. 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.