On this page
  1. What the network does today
  2. History and community governance
  3. Supply, issuance and the meaning of an unlock
  4. Native KAS, custody and trading
  5. The risks behind the design

Kaspa is an active proof-of-work network that uses a blockDAG to order blocks created in parallel. KAS is its native coin, used for transfers and network fees and paid to miners for securing the system. It is not an Ethereum token, an ownership share in a company or a claim on a reserve of another asset.

The project's central design choice is to let parallel block production contribute to the ledger's ordering. A blockDAG is a directed acyclic graph of blocks: connections can branch without forming a loop. GHOSTDAG supplies the consensus ordering used by Kaspa, rather than requiring every useful block to fit into one immediate chain tip.

What the network does today

Kaspa's current project overview describes a mainnet operating at ten blocks per second. The open-source Rust node implementation and its Crescendo release history document the software behind that transition. A high block rate is a network design characteristic, not a guarantee that a merchant or exchange will credit a payment within the same interval.

As checked on November 17, 2026, the project describes Toccata as activated on June 30, 2026. It adds covenant-based programmability: spending conditions that can carry constraints into later transactions. The associated Silverscript repository provides a language and compiler targeting Kaspa Script.

These tools broaden what developers can build, but the existence of a compiler does not establish that a particular application is secure or widely used. The project's overview still describes DAGKnight as the next consensus upgrade. Future block-rate targets should remain roadmap items until deployment evidence establishes otherwise.

History and community governance

Kaspa launched its mainnet in November 2021. Project materials describe a fair launch without a premine, presale or insider coin allocation. Its research lineage includes work on parallel-block consensus, followed by an open-source implementation and a later rewrite in Rust.

There is no company dividend attached to holding KAS. Kraken's asset statement describes a community-maintained codebase without a central governance structure. In that model, evaluating a protocol change means examining software proposals, released code and adoption by network participants. A token balance alone should not be confused with a corporate voting right.

Open development makes implementation details available for review. It does not eliminate disagreements over upgrades or the possibility of bugs. Readers comparing governance models can use our Ethereum profile for a contrasting network design, without assuming the two systems share the same consensus or upgrade process.

Supply, issuance and the meaning of an unlock

KAS has an approximately 28.7 billion maximum supply. New coins are issued through mining. The Rust implementation calculates subsidies from a monthly schedule, with the scheduled rate roughly halving over a year through successive reductions. That is different from describing issuance as one abrupt annual halving.

The implementation also adjusts per-block subsidies for the move to a higher block rate. More blocks per second should not be interpreted as an equivalent multiplication of the intended issuance rate. Historical tables expressed around an earlier block rate need that context.

The fair-launch model has no original venture-investor allocation waiting for a conventional vesting unlock. Mining issuance is still new supply, however, and already circulating coins can be sold. An absence of presale vesting does not prove that ownership is evenly distributed or that selling pressure cannot develop.

Current market values belong in the site's market panel. A fixed supply ceiling does not determine demand, liquidity or a future price.

Native KAS, custody and trading

CoinGecko identifies the asset as Kaspa, ticker KAS, with API ID kaspa. Native KAS belongs on the Kaspa network. A similarly named asset or a wrapped representation on another network requires separate identity and custody checks; this profile does not supply an Ethereum contract address for native KAS.

The project's wallet directory covers mobile, desktop and hardware options. Availability is not an endorsement of every product. Check the wallet's genuine distribution channel, support for the network and recovery procedure. Back up recovery information privately, and confirm a small test transfer before moving a larger balance.

Exchanges may offer KAS in supported jurisdictions, but their withdrawal networks, holds and confirmation requirements remain their own. Our crypto wallet guide explains the difference between leaving assets with a service and controlling signing keys yourself.

The risks behind the design

Proof of work relies on miners and economic incentives, while the node software must correctly validate the ledger. Code defects, concentration of mining resources and disputes over upgrades remain relevant questions. A fast block rate does not remove them.

Programmable applications add their own implementation and custody risks. Evaluate the specific application, its spending rules and its release status separately from Kaspa's base network. The useful case for KAS starts with its actual role in that network, then asks whether the surrounding software and services fit the transaction a user wants to make.