Nothing to do.
September 28, 2026
What changed in Kaspa
New node software, more tools for Python builders, and progress on token standards. Here is what shipped and what it changes.
- Run a node or mining pool? Rusty Kaspa v2.1.0, released September 22, improves node sync and fixes security flaws in network handling and the mining bridge. Its release notes urge operators to upgrade. Mainnet still uses GHOSTDAG at 10 blocks a second.
- Build with Python? Python SDK v2.1.0 shipped September 24. It adds experimental SilverScript and ZK proof tools, with examples for Testnet-10. The SDK is a stable release; those new bindings are experimental.
- Follow token standards? KCC-0, the rules for the standards process, is now Final. The token standard, KCC-20, is still Draft. A proposal to move it to Last Call is open. Wallets and apps still need to agree on how to use it.
- Watch app development? vProgs has active proposals, but no release. Argent still needs audit and hardening. The builder guide separates tools you can try from apps with mainnet use.
- What is being used? At 14:29 UTC on September 28, the covenant index recorded 967 active covenant IDs and small token markets. Its large lifetime count mostly comes from short-lived vaults. The activity breakdown explains what the numbers can tell us.
Check every feature and its evidence · See the changes to KCCs
Current status
What is live now
Live on mainnet right now
Proof-of-work GHOSTDAG consensus, ten blocks a second since CrescendoThe May 2025 upgrade that took Kaspa's mainnet from one block a second to ten., and ToccataActivated 30 June 2026: a coin can carry enforceable spending rules, covenants, not just move address to address.'s spend rules, asset rules, ZK proof checks, and sequencing commitments.
In development
DAGKnight is KIP-2, still Proposed; GHOSTDAG runs consensus today. vProgs remain a prototype, with a private testnet-10 fork example. Argent's inter-covenant communicationSeparately compiled covenant apps joined into one all-or-nothing transaction; works on Toccata today, unaudited offline demos only. already composes covenant apps atomically on Toccata, in unaudited demos; vProgs would add shared mutable state, many users changing one app's state at once.
What each status label means
| Label | What it means here |
|---|---|
| Live | Running on Kaspa mainnet right now, backed by code, a release, or protocol docs. |
| Testnet only | Proved on a test network. That is not evidence of mainnet behavior. |
| Roadmap | Planned work with no committed activation date. |
| Research | Design or architecture work with no live or testnet proof yet. |
| Wrong | A claim people repeat that the sources contradict. |
Status
What Kaspa has, and what it does not
Sources checked September 28, 2026. L1 snapshot read near 14:19 UTC; covenant counts use a separate 14:29 UTC indexer snapshot.
Features and upgrades
| Feature | Status | Meaning | Source |
|---|---|---|---|
| Proof of work | Live | Kaspa runs on proof-of-work mining. Work and new coins never depend on a list of validators. | rusty-kaspa |
| UTXO model | Live | Kaspa tracks spendable outputs, the same model Bitcoin uses. Ethereum tracks balances instead. | rusty-kaspa |
| GHOSTDAG | Live | GHOSTDAG keeps blocks that lose the race to be first, instead of throwing them out. It then orders every kept block into one history. | Kaspa Research, Research Q&A |
| Crescendo, ten blocks a second | Live | SuttonCore Kaspa developer; led the Rust rewrite and much of 2026's covenant and scripting work. put it at roughly 8 to 9 times the throughput and about 30% faster confirmations, not instant finality. A flat "10x faster confirmations" claim goes past his own numbers. | releases; Crescendo roadmap note |
| L1 snapshot, September 28, 2026 · about 14:19 UTC | Snapshot | Virtual DAA score 551,848,158, about 27.726 billion KAS circulating, and 2.18267645 KAS/block on kaspa-mainnet. Dated API observation; the endpoints were read over several seconds. Do not use this endpoint's block or header counts as network totals. | blockDAG API; supply API; block reward API; explorer |
| Emission schedule | Live | Steps down ~5.61% every 2,629,800 seconds, by DAA score, not calendar. Schedule: 23.12465141 KAS/s from DAA 504,909,000; 21.82676446 from 531,207,000. These are score thresholds, not a live subsidy reading. No cliff. | coinbase.rs subsidy table; Kaspa Wiki tokenomics |
| Toccata | Live | L1 spend/asset rules, SilverscriptCompiles to Kaspa script, so a covenant reads as rules instead of hand-assembled opcodes., ZK proof checks, sequencing commitments. v2.0.0 set activation at DAA score 474,165,565; the score arrived about 30 June 2026. v2.0.1 shipped 15 June. | v2.0.1; v2.0.0; Toccata guide |
| Base RTD framing | Live | Real-time decentralization is HashdagKaspa co-founder Yonatan Sompolinsky's research writing site, where he lays out design ideas ahead of protocol work.'s name for Kaspa's core trade: Bitcoin-style proof-of-work security with confirmations that feel seconds-scale on a normal network. | hashd.ag/raw |
| vProgs | Roadmap | Apps that prove richer logic while sharing Kaspa ordering. L1 never becomes one global machine that runs everything. | vProgs repo; programmability docs |
| Native DeFi | Roadmap | A design target that follows the Toccata-era foundations. A live Kaspa-native app layer needs shipped apps and real usage. | Design case |
| DAGKnight | Research | A parameterless consensus direction, meaning it adapts instead of being tuned by hand. It does not run mainnet today. GHOSTDAG does. | KIP-2, still Proposed; hashd.ag |
| 100 blocks a second, netsplit-resilientDescribes a payment that would keep confirming correctly even if part of the network loses contact with the rest, a break called a netsplit. payments | Research | An unverified roadmap claim. No checked mainnet release or accepted specification establishes 100 BPS or confirmation progress during a network split. | No anchor source. The only place this appears is a kaspa.org roadmap page, a source this site does not accept. |
| RTD-derived oracles, TangVMA proposed add-on, not yet built, that would let a smart contract watch outside data and trigger itself instead of waiting for someone to trigger it by hand. | Research | Apps can build oracle, attestation, and coordination-market systems on top of Kaspa. The protocol ships none of them as products. | hashd.ag/raw |
Claims people repeat
| Claim | Verdict | Evidence |
|---|---|---|
| Kaspa already runs at 100 blocks a second | Research | Ten is live. A hundred is an unconfirmed roadmap figure, no release, KIP, or code, appearing only in kaspa.org's roadmap prose, a source this site stopped citing. |
| Kaspa payments become irreversible immediately | Wrong | Inclusion is fast; confidence in a confirmation rises over time rather than switching on. Source: the confirmation-risk demo. |
| Toccata has activated on mainnet | Live | Activated at DAA score 474,165,565 on June 30. v2.0.0 set the score; v2.0.1 shipped June 15, before activation. App, wallet, explorer, SDK, and user adoption are separate, still-open checks. Source: the feature table above. |
| The TN10Testnet-10, one of Kaspa's test networks, where upgrades get tried out before they reach the live mainnet. Toccata test is what activated mainnet | Testnet only | No: tn10-toc2, tn10-toc3, and the Testnet-10 DAA evidence are testnet-only. v2.0.0 set the mainnet activation score. Source: v2.0.0. |
| TN12Testnet-12, a separate Kaspa test network used the same way as TN10: trying out changes before mainnet. proves mainnet covenants | Testnet only | Covenants are live on mainnet, but TN12 isn't why: that rests on the v2.0.0 activation score. TN12 is prototyping evidence. |
| Kaspa has mature native smart contracts | Not yet | Toccata shipped covenants and proof-checks only; mature DeFi and full app infrastructure are still ahead, via vProgs. See the three rungs. |
| July 2026 was a sudden emission cliff | Misleading | The current observed reward is 2.18267645 KAS/block, corresponding to 21.82676446 KAS/s after DAA 531,207,000. Steps occur by DAA score, not calendar date. Source: tokenomics. |
| KCC-0020A Kaspa Call for Conventions: a proposal for how different Kaspa wallets and apps can agree on a shared format, like a token standard. It does not change Kaspa's consensus rules; a KIP does that. is a ratified fungible-token standard | Not yet | KCC-1, KCC-2, and KCC-20 are merged Draft documents. KCC-0's process document is now Final after PR #25 merged September 21; the repository index still says Draft. KCC-20's standard transfer treats different extension commitments as different fungibility classes. The three Draft conventions are not consensus rules or final interoperability standards. Detail: KIPs and KCCs. |
| KCC-0021 and KCC-0402 are adopted standards already running in production | Wrong | KCC-21 was closed without merging on September 25. KCC-402 remains open. A project using a proposal does not make it an adopted standard. Source: kccs repo. |
| DAGKnight is current mainnet consensus | Research | KIP-2 remains Proposed. The unmerged dagknight branch was still active through its 8 September 2026 head, ad45e241; no Rusty Kaspa release activates it, and mainnet remains GHOSTDAG. |
| vProgs have shipped as production app infrastructure | Roadmap | No: zero releases, zero tags, the repo calls itself early development. Its tn10-flow example runs against a private testnet-10 fork node, separate from the public one. Source: vprogs repo. |
| Argent proves Kaspa smart contracts are production-ready | Research | Compiler, generated Silverscript, and ICC exist. Silverscript 1.0 is released; Argent's README still requires further audit and hardening before general production use. Source: Argent README. |
| Native DeFi has shipped as a mature Kaspa L1 product layer | Roadmap | Genuine early usage, small scale; lending still absent from mainnet. Kaskad/Igra L2 lending is ecosystem context, not native L1 DeFi. Counts: build-on-kaspa. |
No match. Try Toccata, DAGKnight, emission, covenant, or press All.
Evidence
The code behind each label
Every label above traces to a repository, release, or proposal file: this is the trail.
Eight tracks: what exists in public, and how to read it
| Track | What exists in public | How to read it |
|---|---|---|
| Toccata and Silverscript | v2.0.0 set the mainnet activation score; v2.0.1 followed. Node setup guide: upgrades, fee policy, changed API fields. Merged: ZK SDK PR (RISC Zero receipts to Kaspa scripts), sequencing-lane PR it depends on, both on the public toccata branch. Testing ran on tn10-toc2 and tn10-toc3, with covenant opcodes on TN12 separately. | Rusty Kaspa v2.1.0 is the current node release. Toccata activation is unchanged. Silverscript v1.0.0 shipped on 9 September 2026 as a stable release. Compiler release status does not certify individual apps, wallets, or deployments. |
| Toccata KIPs | All four read Status: Active in their raw files: KIP-16 (opcodes for verifiable computation), KIP-17 (covenants and scripting), KIP-20 (covenant IDs), KIP-21 (partitioned sequencing commitment). They moved together in one commit on 15 July 2026. |
The spec repo has caught up with the activation record instead of trailing it. |
| Open KIP pull requests | KIP-24 covers transaction version 1 fields and hashing. KIP-25 covers a compute budget on script execution. KIP-22 proposes a Merkle-root pay-to-script form that hides public keys until spend time. | Version 1 transactions and computeBudget already run on mainnet while the KIPs specifying them are open, so cite the operator guide or the node for those two. KIP-22 has no implementation behind it. |
| Argent | argent-lang/argent is an actor-based language and compiler for covenant apps on UTXO rails. It compiles .ag source to Silverscript and portable artifacts that argent-runtime turns into transactions. Two sibling repos appeared in July: argent-playground and argent-template. |
Compiler and runtime exist, but Argent has no release or tag as of September 28, 2026. Its README says it is not release-ready and needs further audit and hardening before general production use. Offline playground demos do not establish a deployment. |
| vProgs | The kaspanet/vprogs README describes an early-development Rust framework for based computation, with core, storage, state, scheduling, runtime, and node layers. A June merge gathered settlement covenants, batch and aggregation provers, sparse Merkle tree support, and a RISC Zero backend into master. | The main branch is unchanged since July 28, but proposed work is active. No releases or tags. Builders can study the prototype; it is not a production app release. |
| DAGKnight | KIP-2 remains Proposed. The unmerged dagknight branch was still active through its 8 September 2026 head, ad45e241; no Rusty Kaspa release activates it, and mainnet remains GHOSTDAG. |
Research and prototype evidence. Mainnet still runs GHOSTDAG, and higher block-rate claims need their own activation record. |
| Builder tooling | Python SDK v2.1.0, released September 24, is the latest stable release. It adds experimental SilverScript compiler bindings, ZK proof script tools, and Testnet-10 examples. Older wallet, lane-proof, and covenant support remains part of the SDK. | Developer tooling, not protocol status. Upgrade claims still come from node, KIP, and activation evidence. |
| Indexing | PR #860 is open for review. It proposes an optional --txindex, a GetTransaction RPC path, inclusion and acceptance metadata, live updates, and pruning tied to retention-root changes. A separate relay draft explores propagating indexed data. |
Open, not merged. It would help wallets, explorers, and indexers once it lands. |
Running infrastructure? Six paths, and what each has to change
Ordinary wallet users: nothing to do. Everyone below has a row.
Upgrade to v2.1.0 for sync and security fixes. Read the release notes before upgrading.
Use fee estimation, or 100 sompi * max(compute grams, 2 * transaction bytes); binds relayed transactions too.
Update SDKs; handle tx version 1, storageMass, computeBudget, output covenants, UTXO covenant_id.
Test block templates and SubmitBlock against Testnet-10; a block stripping post-Toccata fields can turn invalid.
Check GetBlockRewardInfo and GetSeqCommitLaneProof: skipped, it breaks payouts.
References: Toccata node setup guide and Go Kaspad v0.12.23.
Two document series
A KCC is not a KIP
| KIP | KCC | |
|---|---|---|
| Decides | Consensus and core-node behavior | Conventions between independent implementations |
| Binding on | Every node that wants to stay on the network | Whoever chooses to converge |
| Adopted so far | KIP-16, 17, 20 and 21 active; KIP-2 still proposed | KCC-1, KCC-2, and KCC-20 are merged Draft documents. KCC-0's process document is now Final after PR #25 merged September 21; the repository index still says Draft. KCC-1, KCC-2, and KCC-20 remain Draft. |
The kaspanet/kccs README draws the line itself: "KCCs do not propose changes to Kaspa consensus or core-node behavior." The live tracker reads both repositories direct.
Someone pitching you
Testing a product claim built on Kaspa
Protocol status is settled above; a project built on Kaspa is a separate question, usually answered by what the pitch leaves out.
Five kinds of pitch, and the signal worth trusting in each
| Pitch | Real signal | Weak signal | Ask this |
|---|---|---|---|
| Launchpad | Issuance, a wallet flow, a liquidity path, visible holders, abuse controls. | A token button and a roadmap. | What can launch today, and where does the liquidity come from? |
| DeFi | Risk parameters, an oracle model, a liquidation path, an audit trail, working transactions. | The word DeFi stapled to a token page. | Is this mainnet, testnet evidence, or an idea riding on Toccata's name? |
| AI agent | The agent signs, pays, receives, proves work, or triggers a bounded workflow on-chain. | Chatbot copy wrapped around a token. | What action happens on Kaspa, and who can verify it? |
| Wallet | Clear signing, recovery, balances, history, error states, source verification. | Nice screens with no transaction handling underneath. | Does a normal user know what they are signing? |
| Institutional use | Custody, compliance, reporting, settlement, liquidity, support. | One vague partnership post. | Which institution, which requirement, and what is the evidence? |
This checks whether a pitch names the parts a reviewer looks for, not whether the product is worth building.