Kaspa dokončila standardy KCC-1, KCC-2 a KCC-20 pro rozhraní podmíněných transakcí, autorizaci a převody zastupitelných tokenů. Jde o dobrovolné ekosystémové konvence, které nevyžadují změnu konsenzu.
Kaspa’s KCC Coordination Forum has finalized three standards covering covenant interfaces, authorization, and fungible tokens, establishing shared specifications for developers building applications on the network.
Summary
KCC-1 defines shared interfaces for wallets, compilers, indexers, and other tools working with covenants. KCC-2 specifies five standard authorization schemes, including public keys, scripts, and covenant identifiers. KCC-20 sets token transfer rules and supports receiving tokens through an existing compatible output. Finalization establishes ecosystem conventions without changing consensus rules or requiring every participant to adopt them. KCC Coordination Forum said in an Oct. 21 announcement that KCC-1, KCC-2 and KCC-20 were final and ready for adoption across the ecosystem. The forum invited builders to join its public channel for questions, implementation discussions, and support.
Greetings $KAS. KCC-1, KCC-2 and KCC-20 are now Final, meaning they are ready for full adoption across the ecosystem.
We invite Kaspa builders to join the public KCC channel to ask questions, get support, discuss implementations and share what you build.
Come build with us.
— KCC Coordination Forum (@kccforum) October 21, 2026 Kaspa’s canonical standards repository lists all three documents as Final. Its index identifies KCC-1 as the covenant specification, KCC-2 as the authority specification, and KCC-20 as the application standard for fungible-token covenants.
The repository describes KCCs as shared conventions for independent implementations. Its documentation separates those conventions from changes to consensus or core-node behavior, which belong in Kaspa Improvement Proposals.
Kaspa standards cover different parts of application development KCC-1 defines common terms, data layouts and an application binary interface, or ABI, for covenants. The specification describes how software encodes information, calls program functions, and identifies the state carried between transactions.
Its authors, Romain Billot, Michael Sutton and Ori Newman, identify compilers, wallets, indexers and transaction builders among the tools that need to agree on those details. The document says independent implementations need common formats beyond simply producing scripts that pass consensus checks.
The KCC-1 specification leaves developers free to choose their programming language, compiler, and framework. Its shared interface covers program entry points, state templates, and rules for handling transactions involving multiple inputs.
Within the same document, the authors distinguish basic interface rules from features that depend on covenant identifiers. Programs without covenant bindings can follow KCC-1, but the specification says they do not receive the lineage and authorization guarantees supplied by KIP-20.
KCC-2 defines who can authorize an operation KCC-2, written by Billot and Sutton, specifies how programs identify an authority and the minimum checks required to establish its approval. An authority can be a public key, a commitment to a key, a script, or a continuing covenant lineage.
The specification assigns standard identifiers to five authorization schemes. Its public-key options cover Schnorr and ECDSA signatures, while its other options allow a script or covenant lineage to participate as an authority.
For public-key-hash authorization, KCC-2 requires the transaction to reveal the corresponding public key, match its hash against the stored authority value, and provide a valid signature. Higher-level specifications define the signed message and any further conditions.
The authority registry reserves separate ranges for standard and custom schemes. KCC-2 permits participants to adopt custom schemes without waiting for standardization, provided their definitions specify the format, meaning, and approval checks.
Under its covenant-identifier scheme, approval requires an input from the identified covenant lineage. KCC-2 says a higher-level convention can impose further checks on that input’s program and state.
KCC-20 sets token transfer and receiving rules KCC-20 builds on the first two standards, defining token amounts, ownership, and transfer interfaces. The document names Sivan Helfer, Sutton, Newman, and Billot as its authors.
Its specification requires each token covenant to publish program information that software can use to decode state and construct transfers. Configurations must disclose supported ownership schemes and limits on token inputs and outputs.
A feature called borrowed receive lets a sender use a recipient’s existing compatible token output as the destination. KCC-20 says the transaction recreates that output with more tokens, preserves its ownership and extended state, and cannot reduce its KAS value.
The security section warns that replacing the output changes its transaction reference, invalidating unconfirmed transactions spending the previous reference. A wallet must discover the replacement before spending it, according to the document.
The standard links an Argent reference implementation with generated SilverScript contracts and Rust conformance tests.
Final status carries implementation requirements KCC-0, the document governing the standards process, requires more than completion of a final review period. It says a standards-track convention needs human-readable and machine-readable test vectors, plus at least one public implementation that passes the machine-readable checks.
Dependencies must be Final for other KCCs or Active for KIPs, according to the same rules. KCC-0 says status changes occur through pull requests and the repository index must be updated with them.
KCC-0 describes machine-readable test vectors as the authoritative form for automated testing when they accompany human-readable examples. Its submission rules require security considerations to address threats, trust assumptions, and potential replay issues before a standards-track document can enter Last Call.
The governing document states that finalization does not require every ecosystem participant to implement a convention. Substantive changes generally require a replacement KCC, while corrections and clarifications follow the document’s amendment rules.
Kaspa’s application development has previously included separate Layer 2 infrastructure. Gate announced a Kasplex Layer 2 integration in April, enabling KAS deposits and withdrawals through the EVM-compatible network, as crypto.news reported.
In its earlier integration announcement, Gate said customers could transfer KAS from the base network to a Kasplex wallet. Kasplex’s project materials describe a two-way bridge and say developers familiar with Ethereum tools can deploy contracts by changing their remote procedure call endpoints.
Kasplex describes its design as a lightweight rollup that places EVM bytecode in Kaspa transactions and executes it off-chain. Its documentation says Kaspa supplies transaction ordering and data availability, while bridged KAS serves as the Layer 2 gas token.
Zelcore 8.39.0 přináší přepracovaný export daňových údajů, podporu Kaspy včetně KRC-20 a Ledgeru a migraci FLUX z Ergo na hlavní řetězec Fluxu v poměru 1:1 bez poplatku pro držitele k bloku 1 878 291.
Fluxers! Zelcore 8.39.0 is out. It rebuilds Tax & CSV export from the ground up, brings a big set of Kaspa features including names, KRC-20 tokens and Ledger support, lets you free a FluxNode’s collateral instantly, adds InstaSwap with private and zero-knowledge swaps, and opens the migration for FLUX on Ergo.
Tax & CSV export, rebuilt Tax season is where wallets usually let you down. This release fixes that properly.
One export for every coin. Open it from the Export CSV button on any coin, or from Tax & CSV export in the wallet menu. Choose the wallets, coins and period, and save one combined file or one file per coin.
Complete history. The export now reads each address’s history all the way to the end, rather than stopping after one page. Fees are counted for the wallet that paid them, contract calls, internal transfers and both sides of a swap are written out, and every row is valued from full price history. Anything Zelcore cannot price or classify is flagged — never dropped, and never quietly valued at zero. Cosmos Hub, Osmosis, Cardano, Sui and BNB Beacon Chain can now be exported too.
Templates for your tax tool. Ready-made layouts for Koinly, CoinTracker, CoinLedger, CoinTracking, Blockpit, ZenLedger, TokenTax and eleven more, plus neutral and accountant layouts — each following the tool’s own published sample file. Save as CSV, XLSX or JSON. The Zelcore classic and Koinly layouts are free for everyone; the other tool layouts, fiat values and custom mappings come with Zelcore+.
Your own mappings. Add, reorder and rename columns, set the date format, timezone, decimal separator and sign convention, and preview the result against your own history. For tools that sync by address, you can export a list of your public addresses — never any keys.
Private and fast. The export dialog lists every server it will contact, and an encrypted cache on your device means a repeat export only reads what is new.
Kaspa, all the way Kaspa names. Send KAS or KRC-20 tokens to a KNS name such as alice.kas. The resolved address is shown under the name before you can send. KRC-20 tokens. Tokens your wallet holds are discovered for you, and verification shows a token’s logo, decimals, supply and minting state before you import it. Kaspa on Ledger. Import a Kaspa address from a Ledger device and send KAS. UTXO consolidation. With more than 80 UTXOs, one tap merges them, showing the count and total fee before you sign. Live and complete. Incoming payments appear within seconds, Load More reaches older history, KRC-20 screens list transfers, mints and trades, and Sign Message works with Kaspa addresses. KCC tokens at your address are found and shown with balance, supply and history, and the Igra bridge can now move iKAS back to KAS. Free a FluxNode’s collateral instantly Deleting a FluxNode in Zelcore now frees its collateral at once, with no transaction, and the node stays deleted across restarts. The freed collateral appears under Available to lock, with a Lock button ready when you want to put it back to work.
The FluxNode map is rebuilt too: faster, theme-aware and smooth to zoom. Hover a location to see its nodes, click a country to filter, and switch on Only my nodes to see just yours.
InstaSwap: private and zero-knowledge swaps InstaSwap joins Zelcore as a swap provider in three forms: InstaSwap routes your swap through decentralized exchanges; InstaSwap Private makes the deposit and payout impossible to link on chain; and InstaSwap ZK settles through a zero-knowledge shielded pool. Badges on each offer show which kind you are looking at.
FLUX on Ergo comes home In Fusion, holders of FLUX on Ergo at block 1,878,291 can now migrate it 1:1 to the Flux main chain, with no fee. We wrote a step-by-step guide: Claims for FLUX on Ergo Are Open.
Faster, lighter, everywhere Half the code at launch. Zelcore loads less than half as much code at startup; support for some chains now loads the first time you use them. Hardware wallets, front and centre. Hardware Wallet now sits in the import menu without the Experimental label, and actions a hardware wallet cannot sign are hidden or refused clearly rather than failing part-way. Ledger sends now wait patiently for your approval on the device. Every language complete. All 18 languages now cover every screen, with about 27,000 translations added and 5,000 improved. CumulusVPN in Apps, alongside FluxDrive and the other Flux network apps. Get it Zelcore updates itself on desktop, and the latest version is at zelcore.io/download.
Kaspa snižuje těžařskou odměnu každý měsíc přibližně o 5,6 %, takže se za 12 měsíců sníží na polovinu, na rozdíl od přibližně čtyřletého cyklu snižování odměny u Bitcoinu.
Kaspa ($KAS) trims its mining reward about 5.6% each month, producing one full halving a year, while Bitcoin halves roughly every four years. Here is how the schedule works.
Kaspa ($KAS) reduces its mining reward every month, rather than in a single step every four years as Bitcoin ($BTC) does. The result is a smoother issuance curve, but one that pushes miners toward fee income much sooner, according to a post from @BSCNews.
How Kaspa's monthly reduction worksBitcoin's protocol cuts the miner reward in half every 210,000 blocks, roughly every four years. The most recent halving, in April 2024, took the reward from 6.25 to 3.125 BTC per block, per Blockstream.
Kaspa uses what it calls a chromatic emission schedule. The reward is reduced every month by a factor of (1/2)^(1/12), or about 5.6%. After 12 such cuts, the reward has fallen by half, so Kaspa effectively halves once a year without a single cliff event.
The reward began at 440 KAS per second. According to the original post, it now sits near 20.6 KAS per second, or about 2.06 KAS per block. Schedule data from Tokenradar shows the per-second reward at roughly 21.8 for the period from September to October 2026, which is consistent with a further monthly cut to around 20.6.
Kaspa sets its reward per second, not per block. That means the move to 10 blocks per second splits the same payout across more blocks, which is why the per-block figure is far smaller than the per-second figure.
What it means for miners and supplyBecause Kaspa's reward halves four times as often as Bitcoin's, transaction fees will have to make up a larger share of miner income much sooner. Bitcoin's halving affects only the subsidy, not fees, which depend on demand for block space. The same logic applies to Kaspa.
Most of the supply has already been issued. The original post puts about 27.75 billion KAS in circulation out of a total supply of roughly 28.7 billion. Spark Money reports that over 27.5 billion KAS had been mined by mid-2026, around 96% of the cap.
The front-loaded issuance has been a point of debate. One analysis noted that some investors worry miners create constant sell pressure when large amounts of a coin reach the market quickly. How fee revenue develops as the reward keeps shrinking will be a key test for Kaspa's long-term security model.
SourcesSpark Money: Bitcoin vs Kaspa mining and emission compared
Blockstream Help Center: What is the Bitcoin halving?
Tokenradar: Kaspa (KAS) tokenomics and emission schedule
Největší známá peněženka Kaspa, Entity X, zpomaluje nákupy KAS: v červnu činil čistý příliv kapitálu asi 56 milionů KAS, v září už jen 7 milionů KAS. V září peněženka akumulovala kolem 24 milionů KAS a zároveň stáhla 17 milionů tokenů. Začátkem října už peněženka stáhla dalších 4,52 milionu KAS.
The largest known whale wallet on the Kaspa network, tracked by @kaspaunchained as Entity X, appears to be pulling back on its $KAS buying activity. On-chain data from the Kas.live explorer shows a clear deceleration in net inflows over recent months, raising questions about what the shift in behavior might signal for the broader market.
Accumulation Slows Sharply Since Summer Peak The data tells a straightforward story. In June, Entity X posted a net inflow of roughly 56 million KAS. That figure dropped to around 32 million in July, then fell further to approximately 20 million in August. September marked the weakest month yet: the wallet accumulated around 24 million KAS but also withdrew 17 million tokens, resulting in a net inflow of just 7 million KAS.
As of early October, the whale has already withdrawn a further 4.52 million KAS, suggesting the cooler posture has carried into the new month.
Despite the reduced buying pace, the position remains substantial. Entity X currently holds an unrealized profit and loss figure worth $65.71 million, according to the same explorer data.
Context: A Broader Shift in Kaspa Whale Dynamics Entity X has attracted significant attention in the Kaspa community, with the wallet said to have accumulated over a billion KAS and described as one that "almost never sells," alongside speculation about institutional or Gulf capital backing. Whether those rumors hold any weight remains unverified, but the wallet's scale is not in dispute.
Kaspa's emission schedule shows that roughly 27.37 billion KAS have already been mined, representing approximately 95.39% of its hard-capped 28.7 billion supply, with remaining issuance approaching zero by late 2026. That supply dynamic adds weight to how large holders position themselves, since new tokens entering circulation are becoming increasingly scarce.
The slowdown in Entity X's accumulation does not necessarily indicate selling pressure. The wallet's net position continues to grow, and withdrawals from on-chain wallets often reflect movement to cold storage rather than exchange deposits. Still, the declining pace of net inflows is a notable shift from the aggressive buying seen earlier in the summer.
Observers will be watching whether October marks a continued cooling off or a temporary pause before another accumulation phase begins.
Sources:
CoinMarketCap: Kaspa Surges Amid Broad Crypto Rally and Social Hype Around Entity X
CryptoNews: Kaspa Is 95% Mined With Supply Running Out by Late 2026
Kaspa spustila na mainnetu nativní name service .k 13. září 2026, která umožňuje používat krátké .k názvy místo dlouhých adres. Podporuje i subnames pro více peněženek pod jednou identitou.
Kaspa Gets Its Own Native Name Service@dotk_name went live on the Kaspa mainnet on September 13, 2026, introducing a name service built directly into the protocol layer. Rather than relying on an off-chain registry,
The practical upside is straightforward: instead of sharing a long alphanumeric Kaspa address, users can register a short .k name and use that as their on-chain identity. The ownership logic lives in the protocol, removing the need to trust a third-party registry.
Subnames, Wallet Support, and Developer ToolsBeyond simple name registration, dotk now supports subnames, allowing a single .k name to branch into multiple addresses. A project team, for example, could set up handles such as dev.project.k or treasury.project.k, each pointing to its own separate wallet address. This makes .k names useful not just for individuals but for teams and decentralised projects that need to route funds to different purposes under one identity.
Wallet support arrived quickly after launch.
For developers building on top of the system, This gives application builders a clear path to resolve .k names and subnames without having to interact directly with the underlying covenant logic.
The launch positions Kaspa alongside other smart-contract-capable networks that have introduced human-readable naming layers, though dotk's approach of enforcing ownership at the consensus level rather than through a separate smart contract is a technical distinction worth noting for developers evaluating the protocol.
Sources:
dotk name system details on GitHub (Kastle integration request)
Kaspire wallet official site
Kaspire v0.11.31 release notes on GitHub
Kaspa spustila na mainnetu 30. června 2026 hard fork Toccata, který přináší covenants a ověřování pomocí zero-knowledge důkazů. Jde o krok před vProgs, jež mají umožnit složitější výpočty mimo řetězec.
Kaspa's Toccata hard fork went live on mainnet on June 30, 2026, marking a significant step in the network's push toward base-layer programmability.
What Toccata Actually Changes Under Toccata, , effectively letting a native Kaspa UTXO hold and enforce application state across transactions.
Core developer @michaelsuttonil described Toccata as a step toward "synchronously composable verifiable programs," framing it as the infrastructure layer that precedes a more ambitious programmability model.
vProgs: The Next Stage Toccata is explicitly a precursor to vProgs, short for verifiable programs. The model would allow application logic to run off-chain, with a zero-knowledge proof posted to base-layer nodes for verification, keeping L1 lean while enabling more complex computation.
The next major protocol upgrade on Kaspa's roadmap after vProgs is DAGKnight, targeting adaptive consensus and higher throughput.
Sources:
Kaspa Official Docs: Toccata Dev Guide
Michael Sutton: Kaspa Covenants++ Toccata Hard-Fork Outlook (Medium)
KaspaHub: Kaspa Toccata Hard Fork Overview
Kaspa spustila Silverscript v1, jazyk vyšší úrovně pro chytré kontrakty, který má zjednodušit tvorbu čitelných aplikací v účetní knize Kaspa. Vývojáři tak mohou psát složité skripty místo zhruba 60 řádků nízkoúrovňového kódu.
@Kaspaunchained has announced the launch of Silverscript v1, a high-level smart contract language designed to bring readable, complex, stateful applications to the Kaspa ledger. The release marks a meaningful step forward for a network that has, until now, lacked an expressive developer language at the base layer.
What Silverscript Does The practical impact for developers is significant: the language strips away the complexity of writing raw opcodes, condensing what previously required thousands of lines of low-level stack code into concise, human- and AI-readable scripts of around 60 lines.
This design allows developers to focus on application logic rather than low-level implementation details.
Context: Toccata and the Broader Kaspa Roadmap The v1 release closes an eight-month development cycle that ran alongside the Toccata framework.
Silverscript sits on top of this foundation as the primary authoring tool for covenant-based applications.
One caveat worth flagging for developers: the KCC20 token standard is still not live, meaning the full token infrastructure on Kaspa remains a work in progress even as the smart contract language itself reaches v1.
Sources:
Silverscript, Kaspa Official Docs
Silverscript Repository, GitHub
Kaspa Toccata Hard Fork Overview, Bitget News
U Kaspa se zúžil rozdíl mezi velkými držiteli a burzovními peněženkami na zhruba 280 milionů KAS, z asi 4 miliard před rokem. To může naznačovat přesun tokenů na burzy a vyšší prodejní tlak.
On-chain data for Kaspa ($KAS) is flashing an unusual signal: the gap between large private holders and exchange wallets has collapsed to levels not seen in at least a year, raising fresh questions about where big money is moving and why.
Supply Gap Narrows Sharply Wallets holding 10 million or more KAS have seen their combined balance fall to roughly 6.34 billion tokens, according to analysis flagged by @BSCNews. At the same time, exchange wallet balances have climbed to approximately 6.06 billion KAS, leaving a gap of only around 280 million units between the two cohorts. That is a dramatic compression from the roughly 4 billion unit difference recorded just one year ago.
The trend points to one of two dynamics, or a combination of both: large holders are moving tokens onto exchanges, potentially signalling an intent to sell, or exchange-held balances are being attributed to wallets that were previously counted in the large-holder tier. Either way, the structural shift is notable.
That context matters when interpreting what a shift in balances actually means for selling pressure.
What Whale Compression Can Signal However, the current data tells a more ambiguous story. The compression here is not obviously the result of broad redistribution to retail. Instead, it reflects large balances converging toward exchange wallets, which historically precedes increased selling activity.
The Kaspa community and analysts will be watching whether the narrowing gap translates into sustained exchange outflows or a broader distribution to smaller holders in the weeks ahead.
Kaspa operates as a proof-of-work, BlockDAG-based network.
Sources:
Who Really Owns Kaspa? On-Chain Data Reveals the Truth About Wallet Concentration (MEXC)
Kaspa Supply Distribution Table (Kaspalytics)
Kaspa Block Explorer (explorer.kaspa.org)
Kaspa zavádí KIP-9, který zpoplatňuje transakce podle výpočetní i úložné náročnosti a účtuje vyšší z obou poplatků. Cílem je ztížit levné zahlcování sítě daty.
A Dust Attack Exposed a Structural ProblemKaspa's unspent transaction output (UTXO) model carries a fundamental vulnerability. Unlike old block data, which nodes can eventually discard through pruning, coin records stored in the UTXO set never expire.
A real-world dust attack on the Kaspa network illustrated the stakes. An attacker flooded the chain with tiny coin fragments, each of which every full node on the network was required to store permanently. The event made clear that without a structural fix, ledger bloat could be weaponised cheaply and repeatedly. As Kaspa researcher Shai Wyborski noted in a post-attack analysis,
How KIP-9 Changes the Fee Calculus Co-authored by Kaspa core developer @michaelsuttonil, the proposal charges every transaction on two separate scales: computation and storage. The network applies whichever charge is higher.
The storage charge is dynamic. In plain terms, splitting coins into small, scattered outputs drives the fee up. Merging coins into fewer, larger ones brings the storage charge down to zero.
The practical result is that ledger bloat becomes either slow or expensive. According to the KIP's own analysis, wasting 50 GB of node storage in a single day would require a budget of 125 million KAS. Achieving the same outcome with only 100,000 KAS would take an estimated 750 years.
The approach reflects a broader design philosophy in Kaspa: rather than banning dust outright,
Sources
KIP-9 Full Proposal, kaspanet/kips on GitHub
Dust Attack Post-Mortem by Shai Wyborski, Medium
Quadratic Storage Mass and KIP-9, Kaspa Research Forum
Kasplex Network Activity Surges in 2026@Kasplex, the EVM-compatible Layer 2 blockchain built on @kaspaunchained, has posted a sharp acceleration in on-chain activity over the past two months. The network has now crossed 20,000 accounts, with more than 1,500 tokens created on-chain. Most strikingly, three-month transaction volume has jumped to over 600,000, up from roughly 100,000 reported in July, when average daily transactions stood at around 1,094.
The growth underlines rising developer and user interest in Kaspa's expanding application layer. Kasplex is a Layer 2 solution built on top of Kaspa's BlockDAG-based Layer 1, designed to add Ethereum-style smart contract functionality to a network that uses a UTXO model and has no native contract layer. In technical documentation, Kasplex describes itself as a lightweight rollup solution, embedding EVM bytecode into Kaspa L1 transactions and executing it off-chain while using Kaspa for ordering and data availability.
A Growing Ecosystem on a High-Throughput Base Layer Built on Based-Rollup technology and fully compatible with the Ethereum Virtual Machine, Kasplex is designed to introduce DeFi, NFT, and decentralised application functionality to the Kaspa ecosystem. Through a dedicated Relayer module, Kasplex enables conversion between Ethereum and Kaspa transaction formats, allowing developers and users to use familiar Ethereum wallets and tools, significantly lowering barriers for ecosystem interoperability.
The Layer 2's momentum sits on top of an already active base chain. Kaspa currently operates at 10 blocks per second, a milestone achieved with the Crescendo hard fork in May 2025. Scaling targets for 2026 and 2027 aim to push network throughput from 10 to 25, 40, and eventually 100 blocks per second. At the L1 level, the broader network's cumulative activity is substantial: Kaspa has now processed more than 2.3 billion transactions on its mainnet, alongside roughly 462 million blocks processed by the network.
Meanwhile, Gate has connected its exchange infrastructure to the Kasplex Layer 2 network, enabling $KAS deposits and withdrawals via L2. The integration is intended to lower user barriers, improve $KAS circulation, and deepen on-chain activity across the Kaspa ecosystem. As Kasplex continues to improve its infrastructure, the combination of rising transaction counts, a growing token ecosystem, and exchange-level support points to a network that is steadily moving beyond early-stage adoption.
Igra Labs se integrovala s Tangem a přináší Kaspa-native DeFi více než milionu uživatelů hardwarové peněženky. Držitelé $IGRA mohou používat aplikace Igra bez přesunu aktiv do horké peněženky.
Igra Labs Goes Live on Tangem@Igra_Labs has integrated with @Tangem, bringing Kaspa-native decentralised finance to more than one million hardware wallet users. The move gives $IGRA holders access to the Igra apps ecosystem while keeping private keys secured in cold storage, removing a trade-off that has historically pushed DeFi users toward less secure software wallets.
The integration is built on WalletConnect, delivered through Tangem app version 6.1.3. For Tangem users, that means approving transactions via NFC tap rather than exposing keys to an internet-connected device.
What the Integration Means for Kaspa DeFiIgra Network is the EVM-compatible execution layer built on top of Kaspa's proof-of-work BlockDAG.
By connecting to Tangem through WalletConnect, $IGRA holders can now interact with decentralised apps on Igra Network without moving assets to a hot wallet first.
That security baseline now extends to Kaspa-native DeFi for the first time, as the Igra and Tangem integration marks a meaningful step in making cold-storage-secured DeFi access a practical reality rather than a technical workaround.
Sources
Igra Network Public Mainnet Launch, Crypto Adventure
WalletConnect on Tangem, Tangem Official Blog
Kaspa Integrated on Tangem, Kaspa.org
Kaspa po hard forku Toccata hlásí reálné využití: za posledních 24 hodin vzniklo 1 196 covenant transakcí a na L2 Igra proběhlo asi 54 000 transakcí. 86 % posledních bloků už běží na verzi 2.0.1.
On-chain activity picks up across Kaspa's upgraded stackSeven weeks after Kaspa's Toccata hard fork went live on June 30, 2026, the new protocol machinery is showing measurable real-world use. Kaspalytics counts 1,196 covenant-creating transactions in the past 24 hours, with over 2,700 covenant outputs produced. Those outputs represent programmable spending rules running natively on Kaspa's Layer 1, one of the headline features of the upgrade.
Toccata's changes focus primarily on adding covenant-like programmability, transaction v1, script pricing, ZK verification, based-app primitives, and Silverscript tooling. The hard fork transforms Kaspa from a fast, payments-focused network into a programmable value settlement layer.
The zero-knowledge side is at an earlier stage. Just nine ZK precompile transactions were recorded in the same 24-hour window, split between Groth16 and R0Succinct proof verifications. The update introduced an OpZkPrecompile for trustless L1 ZK proof verification and partitioned sequencing commitments to scale based ZK applications. Low initial volumes are expected given how recently that infrastructure became available.
Igra L2 dominates network activityThe clearest adoption signal sits on layer 2. Igra, the EVM-compatible L2 anchored to Kaspa, logged around 54,000 transactions in 24 hours, dwarfing every other protocol on the network, with KRC inscriptions a distant second near 1,900. Igra Labs describes its network as an EVM-compatible programmable layer on Kaspa L1, with fast probabilistic finality and support for 3,000 TPS or more. An EVM-compatible Layer 2 on Kaspa adds a separate layer that can run Ethereum-style smart contracts while still leveraging Kaspa's fast and secure L1 for transaction processing and settlement.
Miner adoption of the post-Toccata software also looks clean. Some 86% of recent blocks come from node version 2.0.1, the post-Toccata release, suggesting the consensus change has settled without a lingering network split. As with any consensus change, failing to upgrade can cause a node to split off from the network , so the rapid migration to 2.0.1 points to a smooth transition across the mining community.
Taken together, the data paints a picture of an upgrade that has cleared its most critical technical hurdle, broad miner adoption, while the application layer is still in its early innings. Covenant activity and Igra's transaction volumes suggest developers and users are beginning to test what the new stack can do.
Sources:
Kaspa Toccata Hard Fork Guide, kaspanet/rusty-kaspa on GitHub
Kaspa's Biggest Upgrade Yet, Bitcoin Foundation
Kaspa Covenants++ Toccata Hard-Fork Outlook by Michael Sutton, Medium
Kaspa po aktivaci Toccata na mainnetu 30. června 2026 běží bez problémů a zachovala si svou UTXO architekturu. Aktivita covenantů ale rychle roste, protože jejich využití vzrostlo v prvních týdnech po spuštění více než 15násobně.
@kaspaunchained's Toccata protocol activated on mainnet on June 30, 2026, marking one of the most significant upgrades in the project's history. Critically,
The activation went smoothly. Hashrate readiness was near-total heading into the switch, and the network's UTXO architecture was left intact throughout the process, preserving Kaspa's core design while layering in new programmable capabilities.
Early On-Chain Activity and Network Performance Kaspa continues to operate at its established throughput of 10 blocks per second, a rate set by the earlier Crescendo hard fork.
Since Toccata went live, on-chain utilisation remains low relative to total capacity, but early covenant activity has grown quickly. Tokens, vaults, and developer experiments have been appearing on-chain, with covenant usage rising by more than 15 times in the first few weeks after activation.
$KAS Price and Market Position The Toccata upgrade followed a similar pattern. After a short rally around the activation date, $KAS has settled back.
The network's hashrate is also running below previous highs, weighed down by price pressure and reduced block emissions as Kaspa's supply schedule continues to wind down.
Looking ahead, the focus for $KAS will be on whether the programmability unlocked by Toccata translates into sustained developer and user growth.
Entity X zvýšila svou držbu Kaspy na 1,47 miliardy $KAS, tedy zhruba 42,9 milionu USD, a je největším známým neburzovním držitelem v síti. Poslední nákup zahrnoval 6,8 milionu $KAS z Bybit, Gate a Bitget.
A wallet cluster tracked on-chain as Entity X has lifted its total Kaspa ($KAS) position to 1.47 billion tokens, valued at approximately $42.9 million at current prices, making it the largest known non-exchange holder on the Kaspa network.
Fresh Inflows From Major Exchanges The latest leg of accumulation included a fresh inflow of 6.8 million $KAS drawn from liquidity pools at @Bybit_Official, @Gate, and @Bitget. The movement confirms a pattern of deliberate, exchange-sourced buying rather than peer-to-peer transfers, suggesting the entity is actively pulling tokens off trading venues and into cold or self-custodied storage.
On-chain data shows accumulation patterns consistent with whale positioning ahead of a known catalyst, a familiar playbook in crypto, but one that tends to accelerate when the underlying technical event is concrete rather than speculative. The @kaspaunchained ecosystem has been scaling toward a broader network upgrade, adding a layer of context to the timing of these moves.
Why the Kaspa Network Is Drawing Attention Kaspa has carved out a unique place in the cryptocurrency space as a pure proof-of-work Layer 1 blockchain built on a blockDAG (Directed Acyclic Graph) structure rather than a traditional linear chain. While Bitcoin processes a single chain of blocks and discards competing ones as orphans, Kaspa's BlockDAG architecture weaves those competing blocks into the ledger itself, enabling parallel block processing at a speed that no other proof-of-work network comes close to matching.
The Toccata hard fork successfully activated on Kaspa's mainnet, marking its most significant upgrade. It transitions the network from a high-speed proof-of-work payments chain to a programmable base-layer blockchain, introducing native Layer-1 covenant systems for expressive smart contracts, zero-knowledge proof verification opcodes, and support for KRC-20 tokens, all without requiring a global virtual machine.
Following that upgrade, the network is set to scale throughput through a series of structured block rate increases, moving from the current 10 blocks per second to 25 BPS, then to 40 BPS, and ultimately targeting 100 BPS as its long-term objective. On-chain data cited by analysts indicates declining Kaspa token balances on cryptocurrency exchanges, suggesting increased movement into self-custody wallets, a pattern interpreted as indicative of long-term holding behavior rather than active trading activity.
Whether Entity X represents a single institutional player or a coordinated group remains unknown. What the on-chain record shows clearly is a sustained, directional bet on the network at scale.
Sources:
Kaspa Roadmap 2026-2027: Every Upgrade Explained, Our Crypto Talk
Kaspa touted as 2026 altcoin standout with PoW BlockDAG edge, Crypto News
Kaspa Exchange Holdings On-Chain Data, Kaspalytics
Kaspa aktivovala hard fork Toccata, který přidává na Layer 1 programovatelnost, nativní KRC-20 tokeny a ověřování ZK důkazů. Síť tak míří od platební vrstvy k programovatelnému proof-of-work Layer 1.
Kaspa ($KAS) has activated the Toccata hard fork, an upgrade that marks a fundamental shift for what has long been marketed as the fastest pure proof-of-work blockchain. The fork moves Kaspa well beyond its payments-layer origins, introducing programmability directly at the base layer without abandoning the BlockDAG architecture or proof-of-work consensus that define the network.
Covenants, native tokens, and ZK proofs land on Layer 1 The centrepiece of the upgrade is the addition of covenants, programmable rules attached directly to transactions. Previously, Kaspa's UTXO model only controlled who could spend coins. After Toccata, developers can create conditions that determine how and when coins are spent, opening the door for smart wallets, escrow services, time-locked vaults, and decentralised finance applications.
The hard fork also introduces native KRC-20 tokens and covenant programming via the SilverScript compiler, transforming Kaspa from a fast payments layer into a programmable proof-of-work Layer 1 that can support DeFi and NFTs directly on its base layer. Previously, KRC-20 tokens operated through inscription-style mechanisms, relying on off-chain indexing and external infrastructure, which introduced inefficiencies and limitations. Under the new regime, token creation, transfers, and atomic operations become part of consensus rules, giving users lower fees, trustless atomic swaps, and seamless integration without bridges or wrapped assets.
The third pillar is zero-knowledge infrastructure. The Toccata upgrade adds zero-knowledge proof verification opcodes at the protocol level, enabling native ZK proof verification on Layer 1. With ZK verification primitives, Kaspa can serve as a settlement layer for ZK rollups: Layer 2 solutions can perform heavy computation off-chain and submit only compact validity proofs to Layer 1.
Core developer Michael Sutton has described Toccata as the point where Kaspa's high-frequency monetary base layer meets programmability in two layered forms: native L1 covenant systems, and based ZK systems built on top of the same foundations.
Two EVM-compatible Layer 2s already building on top The Toccata upgrade is complemented by two distinct Layer 2 solutions, Kasplex and Igra, with independent testing showing that both achieve full EVM compatibility and significant cost advantages, positioning them as viable alternatives to Ethereum for developers. Kasplex operates as a traditional rollup offering immediate EVM compatibility and faster finality, while Igra operates as a decentralised rollup built directly on Kaspa's BlockDAG, offering L1-backed security and community-node processing from day one.
On the Layer 1 covenant path, developers can write covenant-based applications directly on Kaspa using the SilverScript compiler, implementing advanced UTXO-based workflows and programmable transaction constraints within Kaspa's scripting environment. For more complex applications, the ZK infrastructure introduced in Toccata enables developers to build ZK applications that inherit transaction ordering from Layer 1 while performing computation externally and submitting cryptographic proofs back to the chain, supporting rollups, canonical bridges, and other proof-based applications anchored to Kaspa's DAG.
The upgrade represents a decisive architectural bet: that bounded, UTXO-native programmability can attract serious developer activity without the global-state overhead that comes with a full virtual machine. Whether that gamble pays off will depend on how quickly the ecosystem around Toccata's new primitives matures.
Sources
Kaspa Covenants++ Toccata Hard Fork Outlook, Michael Sutton (Medium)
Kaspa Toccata Hard Fork Deep Dive, Gate Blog
Kaspa Official Developer Docs
Kaspa spustila na mainnetu hard fork Toccata 30. června 2026, při DAA skóre 474 165 565 a přibližně v 16:15 UTC, který přidává nativní podporu pro covenanty, transaction introspection a zero-knowledge ověřování na L1. Projekt tím míří od čistě platební sítě k programovatelnosti.
Kaspa Crosses Into Programmable TerritoryKaspa's Toccata hard fork went live on mainnet on June 30, 2026, marking what the project describes as the biggest upgrade in its history. The hard fork activated at DAA score 474,165,565, roughly at 16:15 UTC. The upgrade draws a clear line between what Kaspa was and what it is now becoming: a chain that started as a high-speed payments network and is now reaching for full programmability at the base layer.
Toccata marks the point where Kaspa's high-frequency monetary base layer meets programmability in two layered forms: native L1 covenant systems, and based zero-knowledge systems built on top of the same foundations. That is a significant departure from Kaspa's original identity as a pure proof-of-work payments chain.
What Toccata Actually DeliversThe consensus-changing upgrade introduces native L1 covenant support and transaction introspection, allowing for expressive stateful contracts on $KAS, alongside an OpZkPrecompile for trustless L1 ZK proof verification and partitioned sequencing commitments to support ZK applications.
The upgrade introduces native KRC-20 tokens, covenant programming via SilverScript, and zero-knowledge verification directly on the base layer, designed to shift the network's appeal from pure transaction speed toward supporting application development and privacy-enhanced use cases.
The fork does not, however, ship finished applications. It lays the protocol infrastructure that developers need to build on top. The upgrade activates the protocol infrastructure for covenant-based Layer-1 applications and zero-knowledge systems anchored to Kaspa's BlockDAG. The race now begins for what actually gets built.
The hard fork brings new utility, which means new SDKs and APIs will increasingly target a new developer audience, while classic Kaspa APIs should continue working without change. For node operators and miners, the operational story is straightforward: upgrade nodes, and everything that already works should keep working.
Toccata follows Kaspa's Crescendo hard fork, which in May 2025 increased block production from one block per second to ten blocks per second, achieving one of the highest base-layer throughputs in the proof-of-work space. The question now is whether Toccata's programmability layer can attract the developer activity needed to match that technical foundation.
Sources:
Kaspa Official Toccata Upgrade Guide, kaspanet/rusty-kaspa on GitHub
Kaspa Covenants++ Toccata Hard Fork Outlook by Michael Sutton, Medium
Kaspa Toccata Hard Fork Deep Dive, Gate Blog
Kaspa price has surged about 15% over the past day as investors have positioned ahead of the network’s long-awaited Toccata hard fork despite continued weakness across the crypto market.
Summary
Kaspa surged 15% as traders positioned ahead of the scheduled Toccata hard fork. Investors expect the upgrade to add smart contracts, KRC-20 tokens, and DeFi functionality. Technical buying and short covering helped KAS outperform a weak crypto market. According to the Kaspa network, the Toccata hard fork is scheduled to activate on the mainnet at approximately 16:15 UTC on June 30. Exchanges including HTX temporarily suspended deposits and withdrawals ahead of the upgrade to support the transition.
🎼 Kaspa Mainnet Toccata Activation
The next major milestone for Kaspa is almost here.
Today is the Day!
📍 Activation: DAA Score 474,165,565
🕒 Expected: June 30, 2026 • 16:15 UTC
— ChoiiMhiee 𐤊 (@mhieechoii) June 30, 2026 The upgrade introduces native smart contract functionality through the SilverScript programming language, while also adding support for KRC-20 tokens, decentralized finance applications, and zero-knowledge privacy features.
Together, these additions remove one of the network’s biggest limitations by expanding Kaspa beyond its original role as a high-speed proof-of-work payment blockchain.
Toccata upgrade has changed Kaspa’s utility With the hard fork approaching, trading activity has accelerated as investors position for higher on-chain activity. According to the Kaspa network, the upgrade is expected to enable developers to build decentralized applications directly on Kaspa by introducing native smart contract functionality, expanding the network beyond its traditional payment use case.
On-chain activity has also supported the bullish narrative. The network is approaching a cumulative milestone of roughly 2.35 billion transactions, demonstrating continued usage of its BlockDAG architecture even as new features are introduced. Supporters of the network have long argued that BlockDAG enables higher parallel transaction throughput than conventional blockchain designs, reducing congestion during periods of elevated demand.
The technical setup amplified the move. Before the hard fork, Kaspa had spent several months trading inside a prolonged consolidation range, with buyers repeatedly defending the $0.025-$0.030 area. The upgrade arrived while many derivatives traders remained positioned for further downside, creating conditions for a short squeeze as spot demand increased.
Forced liquidations of bearish positions added momentum to the rally once price broke above its recent trading range.
The daily chart also shows the recovery pushing KAS back above its 20-day simple moving average near $0.030 while testing resistance around the 50-day moving average near $0.0317. At the same time, the MACD has produced a bullish crossover with the histogram turning positive, indicating improving momentum.
Kaspa 1-day USDT chart — June 30 | Source: crypto.news Still, the token trades below its declining 100-day and 200-day moving averages, suggesting that a sustained trend reversal would require additional buying pressure.
Technical buying has outweighed macro headwinds Kaspa’s rally has unfolded while much of the cryptocurrency market continues to struggle under an unfavorable macro backdrop. A stronger-than-expected 4.1% U.S. Core PCE inflation reading and the Federal Reserve’s hawkish policy stance under Chair Kevin Warsh have pressured risk assets in recent days, contributing to an estimated $1.79 billion in cumulative outflows from U.S. spot Bitcoin exchange-traded funds.
Unlike many proof-of-stake networks, however, Kaspa operates on a proof-of-work model with approximately 95.4% of its maximum supply already in circulation. With new token issuance steadily declining over time, the introduction of smart contracts and execution fees through the Toccata upgrade has strengthened the network’s utility without materially increasing supply.
Those supply dynamics, combined with renewed developer opportunities and short-covering activity, have helped Kaspa outperform most major cryptocurrencies even as capital has continued flowing out of other digital assets.
Whether the rally extends from here may depend on whether buyers can reclaim resistance around the 50-day and 100-day moving averages before challenging the longer-term 200-day average near $0.0353.
Disclosure: This article does not represent investment advice. The content and materials featured on this page are for educational purposes only.
Kaspa už zpracovala zhruba 2,347 miliardy transakcí na Layer 1, což ji řadí mezi nejaktivnější sítě. Po Crescendo hardforku běží na 10 blocích za sekundu.
According to data from the official @kaspaunchained explorer, Kaspa's Layer 1 blockchain has now processed roughly 2,347,000,000 transactions, placing it among the highest cumulative transaction counts of any major network. The figure represents a dramatic leap in activity for a proof-of-work chain that only launched in November 2021.
Built for Speed on a Proof-of-Work Foundation Kaspa's transaction throughput is underpinned by its blockDAG architecture, which uses the GHOSTDAG consensus protocol to allow parallel block creation rather than the single-block linear approach used by Bitcoin and Ethereum. Following the Crescendo hardfork earlier in 2025, Kaspa's block rate increased from one block per second to ten blocks per second, drastically boosting throughput. Since that upgrade, the network has operated at a steady 10 blocks per second, delivering 100-millisecond block times and sub-7-second finality.
The numbers behind that architecture are hard to ignore. On October 2, 2025, Kaspa set a new world record for proof-of-work throughput by reaching 5,584 transactions per second under real network conditions, surpassing its own previous record of 4,757 TPS achieved just days earlier. These figures were recorded on Kaspa's live mainnet under genuine transaction load, not testnet simulations. On October 5, 2025, the network processed 158,441,966 transactions within a single 24-hour window.
The Valuation Question: $770M Market Cap vs. 2.35 Billion Transactions Kaspa currently holds a live market cap of approximately $770 million, with a circulating supply of around 27.5 billion KAS coins out of a maximum supply of 28.7 billion. That places $KAS in a middle tier of Layer 1 assets by market value, despite its outsized on-chain activity relative to peers.
The supply picture is a key part of the valuation debate. Approximately 95.4% of Kaspa's 28.7 billion maximum supply is already in circulation, with emissions nearing zero by end-2026. New selling pressure primarily comes from miners selling rewards, not token unlocks. That dynamic could reduce dilution risk over time, but it also means the network must attract fresh demand to sustain price levels.
On the protocol side, a significant catalyst is imminent. The upcoming Toccata hard fork marks Kaspa's shift from a payments chain to a programmable Layer 1, introducing native KRC-20 token issuance, covenant programming via the SilverScript compiler, and zero-knowledge verification opcodes. The upgrade is seen as bullish for $KAS because it enables decentralized finance, NFTs, and complex applications to settle directly on Kaspa's secure base layer, potentially driving developer adoption and new utility.
Whether 2.35 billion transactions and an imminent programmability upgrade justify, or undervalue, a $770 million market cap is a question the market is still working through. The on-chain fundamentals are difficult to dismiss. The price action, for now, tells a more cautious story.
Following six months of testing with zero state divergence, Igra Network opens public access to a 3,000+ TPS smart contract environment secured by proof-of-work consensus. Fifteen protocols are deploying at launch alongside cross-chain connectivity through Hyperlane. A security audit by Sigma Prime completed with no unresolved issues.
Igra Labs has opened public access to Igra Network, a decentralized EVM-compatible execution layer built on Kaspa’s proof-of-work BlockDAG. The mainnet launch follows a testnet that processed over 730,000 transactions across 21 million blocks with zero state divergence.
Kaspa is a proof-of-work blockchain with a market capitalization nearing $1 billion and more than 500,000 active addresses. The ecosystem generated $486 million in trading volume on the day KRC-20 token protocol functionality launched, demonstrating significant latent demand for on-chain activity. Despite that demand, the ecosystem has operated with less than $1 million in DeFi total value locked due to the absence of a decentralized and programmable smart contract layer. Igra Network is built to close that gap. By inheriting Kaspa’s proof-of-work security while delivering full Ethereum Virtual Machine compatibility, the network gives the ecosystem’s existing user base and a global developer community of over 100,000 Solidity engineers a shared execution environment for the first time.
Igra operates as a based rollup, a design in which transaction ordering is delegated entirely to the base layer rather than handled by a centralized sequencer. Kaspa miners sequence Igra transactions without the ability to read their contents, a structural property that provides resistance to MEV extraction, front-running, and transaction censorship at the protocol level rather than as an application-layer patch.
The network delivers over 3,000 transactions per second with sub-second inclusion latency, powered by Kaspa’s 10-block-per-second BlockDAG architecture and parallel transaction sequencing. Unlike linear blockchains where transactions queue in a single ordering chain, the BlockDAG processes multiple blocks simultaneously, providing the throughput required for DeFi workloads at scale. A security audit by Sigma Prime, the firm behind Ethereum’s Lighthouse consensus client, completed clean with no unresolved issues.
Fifteen protocols have committed to deploy at launch spanning DeFi, infrastructure, wallets, and stablecoins. Launch partners include Kaskad (Aave V3-style lending and borrowing), ZealousSwap (Uniswap v2 decentralized exchange), Zealous Auctions Protocol (Continuous Clearing Auctions token launch), Hyperlane (cross-chain messaging and USDC.e bridging), Kasperia and Kasware (wallets), KAT Bridge (KRC-20 Token and KRC-721 NFT bridging), Dagscan (block explorer), and Kaspa.com (DEX and launchpad). Ecosystem partners collectively manage over $5 million in total value locked across the Kaspa ecosystem. Kaspa’s native token wraps 1:1 to iKAS on Igra through a trust-minimized bridge backed by locked KAS on L1, serving as the network’s gas token.
Igra Labs plans to introduce a second-generation execution engine incorporating Block-STM parallel processing in the second half of 2026, alongside agent-native infrastructure for machine-to-machine payment, identity, and orchestration, positioning the network for the emerging autonomous agent economy.
“There is over a billion dollars in ecosystem value on Kaspa and $486 million in volume on a single day when KRC-20 launched, yet almost no sufficiently decentralized programmable infrastructure exists to capture it,” said Pavel Emdin, CEO of Igra Labs. “That gap is now closed. Igra delivers full EVM programmability without compromising on the security properties that brought people to proof-of-work.”
“Fifteen teams committed before mainnet went live. Hyperlane gives us cross-chain connectivity and stablecoin access from day one, and Kaskad brings institutional-grade lending to proof-of-work for the first time,” said Ashton Wood, Head of Ecosystem and Business Development at Igra Labs. “The infrastructure is live and the ecosystem is ready.”
The Igra Labs core team includes former DAGLabs engineers who contributed to shipping Kaspa’s original mainnet, alongside Panther Protocol alumni and EVM client contributors. The project is governed by a Swiss association, with a functioning DAO governance structure following a successful token generation event.
A public token auction for the IGRA governance and security token is scheduled for late March 2026 through ZAP (Zealous Auctions Protocol), an on-chain continuous clearing auction on Igra Network (https://igralabs.com/public-auction/overview). The same mechanism powered Aztec’s $59 million sale—on-chain price discovery, no lockup or vesting, tokens fully liquid on claim. Participation is open to anyone with iKAS on the network ($0.006 floor; three-point-five percent of supply). Details at igralabs.com. Secondary on-chain trading through ZealousSwap DEX.
About Igra Network
Igra Network is a based rollup on Kaspa’s proof-of-work BlockDAG delivering full EVM compatibility, 3,000+ TPS, sub-second finality, and architectural MEV resistance without a centralized sequencer. Learn more at igralabs.com (https://igralabs.com).
Kaspa's upcoming Toccata hard fork will add two new programmability paths to the network: native L1 covenant programming and based zero-knowledge (zk) application infrastructure, with mainnet activation now scheduled for June 5–20, 2026, pushed back from the original May 5 target.
Michael Sutton of Kaspa Core published a detailed update on what the hard fork includes, why the date moved, and how the next few months are expected to unfold. The fork was originally initiated by Ori Newman as an effort to bring covenants into Kaspa's script engine, partly in response to the OP_CAT discussion in Bitcoin circles. It has since grown into something considerably larger.
What Is The Toccata Hard Fork?Toccata is a scheduled hard fork for the Kaspa network that introduces new capabilities directly into the base layer. A hard fork, for those less familiar, is a protocol upgrade that is not backward-compatible. All nodes must upgrade to continue participating in the network.
The name follows Kaspa's tradition of using musical references for major upgrades. This one takes its name from a classical musical form, the toccata, a piece designed to showcase technical skill across a keyboard instrument.
At a high level, Toccata adds two things to Kaspa:
Native L1 covenant programming via a new compiler called SilverscriptBased zk application infrastructure, built on top of those same covenant foundationsThese are not interchangeable systems. They serve different use cases and target different developer audiences.
What Are Covenants And Why Do They Matter For Kaspa?Covenants are conditions placed on how funds in a transaction output can be spent in the future. In a standard Bitcoin or Kaspa transaction, once coins are sent, the recipient can do whatever they like with them. Covenants change that by embedding spending rules directly into the script.
Kaspa uses a UTXO model, similar to Bitcoin, where each transaction consumes existing outputs and creates new ones. Covenants in a UTXO system allow developers to build surprisingly complex stateful multi-contract flows, even though the underlying computation remains local to each UTXO.
To make covenant development more accessible, Kaspa Core is finalizing Silverscript, a compiler initiated by Ori Newman, Michael Sutton, IzioDev, and Manyfest. Silverscript is designed to make it easier and safer to write and deploy complex covenants directly on Kaspa L1, without developers needing to work at the raw script-engine level.
What Are Based ZK Applications?The second programmability pillar introduced in Toccata is based zk applications. This is the more technically dense of the two and worth unpacking carefully.
ZK stands for zero-knowledge, a cryptographic method that lets one party prove something is true without revealing the underlying data. ZK proofs are increasingly used in blockchain scaling because they allow off-chain computation to be verified on-chain cheaply and securely.
"Based" in this context means the zk system fully follows L1 sequencing. A based zk application cannot add or drop transactions independently. It is anchored to Kaspa's own transaction order, which is what makes it trustworthy without a separate sequencer.
Toccata introduces several components to support this:
ZK verification opcodes, including a flexible Groth16 verifier and a RISC Zero STARK verifierA sequencing commitment access opcode, enabling based applications to anchor themselves to L1 orderingKIP-21, a partitioned sequencing commitment architecture that ensures a zk app's proving costs scale with its own activity, not with overall DAG activityThe RISC Zero STARK verifier is already implemented and activated on testnet 12. Whether it activates on mainnet is still being decided.
Why Proving Costs MatterFor any zk application to be practical, the cost of generating proofs needs to stay proportional to what the application itself does. If a zk app had to prove work relative to all activity on the broader DAG, costs would become unpredictable and unmanageable. KIP-21 solves this by partitioning sequencing commitments, keeping each app's workload self-contained.
What Is Already In Place?A significant portion of the hard fork is already implemented. The following features are already built:
Extended script-engine opcode support, the core covenants backbone, under KIP-17Covenant IDs for lineage management as a consensus and engine feature, under KIP-20ZK opcodes with a zk-verifier precompile subsystem, under KIP-16, authored by Alexander SafstromSequencing commitment access opcodeKIP-21, authored by Sutton and implemented by Maxim Biryukov, fully implemented and pending reviewProof-of-concept milestones, including inline zk covenants and based zk covenants with a KAS canonical bridge, have also been completed by Maxim and were instrumental in shaping the final design of the fork.
Why Did The Hard Fork Date Move To June?The original mainnet target was May 5, 2026. It has since moved to a window of June 5–20, 2026.
The reason is architectural. Once zk circuits and runtimes bind to a sequencing commitment hashing structure, any structural changes after the fact become breaking changes. Getting the design wrong and patching it later would be far more disruptive than taking the extra time now.
KIP-21 is already designed to be future-compatible with the commitment scheme that will eventually be required by vprogs, Kaspa's longer-term roadmap for synchronously composable verifiable programs. Locking in the right structure before mainnet activation avoids costly migrations later.
The feature freeze is expected on April 15, 2026.
What Happens Between Feature Freeze And Mainnet?After the April 15 feature freeze, Kaspa Core plans a clean restart of the dedicated testnet, TN12, with the full final feature set included. This is not a simulation of the hard fork transition. It is a clean network for testing the complete feature set in its final form.
From there, the team will merge the accumulated months of work from a long-lived pending branch back into the master codebase. That process involves final auditing, closing open items, perfecting hard-fork activation logic, and handling database upgradability.
Once that work is complete, a test hard fork will run over TN10, the long-term testnet, to simulate a full mainnet-style transition. The mainnet date will only be hardcoded after that rehearsal runs to the team's satisfaction.
What Node Operators Should ExpectFor miners and node operators, the upgrade is designed to be straightforward. Nodes need to be updated, and existing functionality should continue working. Disk space requirements are expected to increase by roughly 20 to 50 percent. No dramatic infrastructure changes are anticipated.
What Toccata Actually Delivers For KaspaToccata adds two working programmability systems to Kaspa's base layer: native L1 covenant scripting through Silverscript, and based zk application infrastructure through KIP-16, KIP-20, and KIP-21. A large portion of the technical work is already done. What remains is finalizing interfaces, merging the pending branch into master, and running a full rehearsal on TN10 before the mainnet date is confirmed.
The June 5–20, 2026 window exists because the team chose to get the sequencing commitment architecture right the first time rather than fix it later under live conditions. For node operators, the upgrade is designed to be straightforward, with no major infrastructure changes beyond a modest increase in disk space.
ResourcesKaspa on X: Post (April, 2026)
Blog article by Michael Sutton: Kaspa Covenants++ “Toccata” Hard-Fork Outlook
Kaspa už zpracovala více než 1,957 miliardy on-chain transakcí k 20. dubnu 2026 a blíží se hranici 2 miliard. To přichází těsně před hard forkem Toccata, jehož aktivace na mainnetu je nyní plánována mezi 5. a 20. červnem 2026. Ten má z Kaspy udělat programovatelnou Layer 1.
Kaspa has processed more than 1.957 billion cumulative on-chain transactions as of April 20, 2026, putting the network within days of the 2 billion mark at current activity levels. The timing matters. The milestone lands right before the Toccata hard fork, Kaspa's largest protocol upgrade to date, now set for mainnet activation between June 5 and June 20, 2026.
The transaction count is not a vanity metric. It reflects what the network has actually processed since launch, running on a proof-of-work BlockDAG at 10 blocks per second without the congestion that slows down linear chains like Bitcoin.
What do the numbers actually show?According to the official Kaspa explorer, the network has crossed a block height of 412,700,579 with an average block time of 0.1 seconds. Circulating supply sits at 27.37 billion $KAS, which is 95.39% of the 28.7 billion maximum. Active wallet addresses stand at 538,449, and the current block reward is 2.914 KAS. The next reward reduction is scheduled for May 5, 2026.
The throughput story has been consistent. Hourly bursts have topped 1 million transactions during peak activity, driven by L1 transfers and Layer 2 protocols like Igra L2 that settle on Kaspa. Analysts have pointed out that Kaspa has processed more transactions in four years than Bitcoin has in roughly 17. That comparison is not about superiority. It is about what a parallel-block architecture produces when it runs under real demand.
KAS has caught some tailwind alongside the milestone. The token trades around $0.0347, up 8.67% on the week, with a market cap near $949.75 million and 24-hour volume of $26.61 million, a 20.23% rise over the prior day.
What is Toccata, and why does it matter?Toccata, officially named Kaspa Covenants++, is a non-backward-compatible hard fork that turns Kaspa from a payments-focused settlement layer into a programmable Layer 1. Nodes must upgrade, and the rollout has followed a tight schedule.
The feature freeze happened on April 15, 2026. Testnet 12 is already running covenant and ZK testing, and developers plan a full transition rehearsal on TN10 before the mainnet date is locked in. The activation window slipped from the original May 5 target to give core developer Michael Sutton (@michaelsuttonil) and the team time to finalize the sequencing commitment architecture that ZK circuits and runtimes bind to.
Toccata introduces several things at the base layer:
Native assets and tokens directly on-chainCovenants via extended opcodes under KIP-17, letting UTXOs carry forward enforceable spending rules such as timed releases and multi-stage logicSilverScript, a new high-level compiler and SDK designed to make covenant programming saferZK opcodes and verifiers, including Groth16 and RISC Zero STARK on testnet, for privacy tools and trust-minimized bridgesEarly groundwork for vProgs, the synchronously composable verifiable programs, planned for a later phaseSutton has been direct about the scope. "We are not there yet," he said of vProgs, the synchronously composable verifiable programs on the longer roadmap. The current focus, he notes, is standalone ZK apps with L1 bridging.
What happens after Toccata activates?For node operators, disk usage is expected to rise by 20 to 50%, and existing functionality continues to work. New SDKs and APIs will support the added capabilities without breaking current tools.
As with any non-backward-compatible fork, execution is the open variable. The TN10 rehearsal and the April feature freeze are meant to compress that risk before mainnet.
The longer roadmap keeps pushing throughput. Targets sit at 25, 40, and eventually 100 blocks per second. The goal is to keep the base layer lean while programmability runs through L1 sequencing rather than a global virtual machine.
The 2 billion transaction mark is worth noting on its own. It is also the baseline Toccata is built on. If the upgrade lands cleanly, Kaspa shifts from a chain that moves value fast to one that can enforce rules on how that value moves, without giving up the speed that got it here.
For the latest updates, visit the official Kaspa website.
Sources:
Kaspa Explorer — Live network statistics for total transactions, block height, circulating supply, and active wallet addressesToccata Hard Fork Outlook — Official Kaspa.org breakdown of Toccata features, timeline, and activation window, based on the post by core developer Michael SuttonKAS.live Hardfork Countdown — Community countdown tracker for the June 5, 2026 Toccata activationKaspa Main Site — Official project site with BlockDAG architecture and GHOSTDAG protocol documentationCoinMarketCap Kaspa Page — Price, market cap, volume, and supply data for KAS
Gate integrovala Kasplex Layer 2 na Kaspa, takže uživatelé mohou přes burzu převádět KAS mezi L1 a EVM-kompatibilním L2. Kasplex používá KAS jako jediný gas token a zaměřuje se na smart kontrakty a DeFi.
Gate has integrated Kasplex Layer 2 on Kaspa, opening a direct bridge for users to move KAS onto an EVM‑compatible DeFi environment.
Summary
Gate has connected its exchange infrastructure to the Kasplex Layer 2 network on Kaspa, enabling KAS deposits and withdrawals via L2. Kasplex uses $KAS as its sole gas and network token, aiming to bring EVM‑compatible smart contracts and DeFi to Kaspa’s high‑throughput BlockDAG chain. The integration is meant to lower user barriers, improve KAS circulation and deepen on‑chain activity across the Kaspa ecosystem. Gate has officially integrated the Kasplex Layer 2 network, allowing users to move Kaspa’s native token KAS between the Kaspa Layer 1 chain and Kasplex L2 directly through the exchange. According to Gate, customers can now “transfer KAS from Kaspa L1 to the Kasplex L2 wallet,” a step the platform says will “significantly” reduce entry barriers while “enhancing asset circulation and on‑chain interaction” for KAS holders.
Kasplex is a Layer 2 solution built on top of Kaspa’s BlockDAG‑based Layer 1 and is designed to add Ethereum‑style smart contract functionality to a network that, like Bitcoin, uses a UTXO model and has no native contract layer. In technical documentation, Kasplex describes itself as “a lightweight Rollup solution based on Kaspa,” embedding EVM bytecode into Kaspa L1 transactions and executing it off‑chain to update Layer 2 state while using Kaspa for ordering and data availability.
Kasplex’s KAS‑only gas model and DeFi goals In posts on X, the Kasplex team has stressed that the network uses bridged $KAS as its only gas token, rather than introducing a separate L2 asset, in order to “preserve economic alignment and keep value within the Kaspa ecosystem.” The project offers a two‑way bridge for moving KAS between L1 and L2 and says smart‑contract deployment is “as simple as redirecting RPC endpoints,” with the aim of making it easy for developers familiar with EVM tooling to launch applications on Kasplex.
Kasplex’s architecture is pitched as a way to unlock DeFi, NFTs and other dApps on Kaspa by combining the base chain’s high‑throughput BlockDAG design with EVM‑compatible execution. Kasplex notes that by using Kaspa L1 for canonical transaction ordering and data, its Rollup‑style design can support automated market makers, lending and borrowing markets, stablecoins and other composable protocols that “cannot be realized on the primary chain” alone.
Kaspa itself has become one of the more actively traded mid‑cap layer‑1 tokens, with a live price of about $0.0345, a 24‑hour trading range between roughly $0.0340 and $0.0353, and a recent 24‑hour volume near $26.4 million. CoinMarketCap data puts Kaspa’s all‑time high at $0.2075, meaning KAS currently trades more than 80% below its peak, a gap backers hope additional L2 utility can help narrow over time.
Kaspa community posts have framed Kasplex as “a huge milestone ahead of imminent mainnet,” highlighting growing momentum around node decentralization, liquidity pools and wallet integrations, including tutorials on bridging KAS and adding the L2 network to Kasware and MetaMask. By wiring Kasplex directly into its deposit and withdrawal rails, Gate is betting that a smoother path onto L2 will translate into more KAS moving into smart contracts, and more activity across Kaspa’s expanding DeFi stack.
