What Is Kaspa? KAS Coin and BlockDAG Network Explained
Kaspa is an open-source proof-of-work Layer 1 network built around a blockDAG architecture. KAS is its native coin, used for transfers, transaction fees, and mining rewards.
Kaspa differs from traditional proof-of-work blockchains because blocks created at nearly the same time do not automatically compete for a single position in one linear chain. Its GHOSTDAG consensus protocol allows parallel blocks to coexist and places them into a consistent order.
Following the Crescendo network upgrade on May 5, 2025, Kaspa increased its mainnet block rate from 1 block per second to 10 blocks per second. This gives the network a target interval of approximately 0.1 seconds between blocks.
This guide explains what Kaspa is, how its blockDAG works, what KAS is used for, how its supply is issued, and what users should verify before sending or receiving the coin.
Kaspa at a Glance
| Network detail | Kaspa data |
|---|---|
| Network type | Proof-of-work Layer 1 |
| Native coin | KAS |
| Ledger structure | BlockDAG |
| Consensus protocol | GHOSTDAG |
| Mining algorithm | kHeavyHash |
| Current target block rate | 10 blocks per second |
| Approximate target block interval | 0.1 seconds |
| Mainnet launch | November 7, 2021 |
| Launch model | Fair launch |
| Premine | None |
| Presale or ICO | None |
| Estimated maximum supply | 28,704,026,601 KAS |
| Smallest KAS unit | 1 sompi |
| Sompi per KAS | 100,000,000 |
| Base-layer consensus | Proof of work, not proof of stake |
Kaspa is not an ERC-20 or BEP-20 token. Native KAS operates on the Kaspa network and should be sent only to addresses and services that support that network.
Kaspa vs KAS: What Is the Difference?
Kaspa and KAS are closely related, but the terms describe different things.
| Term | Meaning |
|---|---|
| Kaspa | The Layer 1 network, protocol, node software, and wider project |
| KAS | The native coin recorded and transferred on the Kaspa network |
Kaspa is the infrastructure. KAS is the asset that moves through it.
This distinction also explains why KAS is generally classified as a coin rather than a token. It is native to its own Layer 1 ledger instead of being created through a smart contract on Ethereum, BNB Chain, or another external blockchain.
For users, the practical rule is straightforward: a platform must explicitly support native Kaspa deposits and withdrawals. Support for Ethereum, BNB Chain, or another network does not automatically mean that the platform can receive KAS.
When Did Kaspa Launch?
The Kaspa mainnet launched on November 7, 2021.
It used a fair-launch model with:
- no premine;
- no initial coin offering;
- no private token sale;
- no preallocation to founders or investors;
- no separate insider vesting allocation.
New KAS entered circulation through proof-of-work mining from the start of the network. This means miners competed for block rewards under the public network rules rather than receiving coins from a preminted supply.
Kaspa was originally developed from research associated with DAGLabs and researchers including Yonatan Sompolinsky. Before the mainnet launch, the project moved toward community ownership and open-source development.
What Is KAS Used For?
KAS performs several base-layer functions within the Kaspa network.
Sending and Receiving Value
Users can send KAS from one Kaspa address to another. The transaction is propagated to network nodes, included in the blockDAG, and ordered under the consensus rules.
Paying Transaction Fees
KAS is used to pay network transaction fees. Fees compensate miners for including and processing transactions. The fee is not necessarily a fixed amount for every transfer. It can depend on transaction mass, the number of unspent transaction outputs used, the number of outputs created, wallet fee settings, and current network demand.
Mining Rewards
Miners receive newly issued KAS and transaction fees for contributing computational work to the network. The mining reward declines over time under Kaspa's emission schedule. As issuance falls, transaction fees are expected to represent a larger part of miner revenue.
Kaspa documentation gives approximately 0.000023 KAS as an example of a typical minimum-fee transaction. Some wallets may use a higher default, such as approximately 0.0001 KAS per UTXO. These figures are examples rather than guaranteed fees for every transfer.
How Does the Kaspa Network Work?
Kaspa uses proof of work and a directed acyclic graph of blocks, commonly called a blockDAG.
In a traditional linear blockchain, blocks are generally arranged one after another:
When two miners create blocks at nearly the same time, a linear blockchain may eventually accept one branch as the main chain while treating another valid block as stale or orphaned.
A simplified blockDAG can contain several blocks created in parallel:
Kaspa's protocol does not require every parallel block to be discarded. GHOSTDAG identifies and orders blocks so that multiple valid blocks can contribute to the network's history.
This approach is designed to retain proof-of-work security while allowing a higher block-production rate than conventional linear proof-of-work chains.
What Is GHOSTDAG?
GHOSTDAG is Kaspa's consensus protocol for ordering blocks in the blockDAG.
Its role is to help nodes reach agreement when many blocks are produced close together in time. Rather than selecting only one block from every set of competing parallel blocks, GHOSTDAG classifies and orders blocks according to the amount and structure of proof of work in the DAG.
In simplified terms, GHOSTDAG allows the network to:
- accept blocks created in parallel;
- determine how those blocks relate to one another;
- identify the well-connected portion of the DAG;
- establish a consistent transaction order;
- reject or separate blocks that do not fit the accepted consensus structure.
The protocol is a generalization of Nakamoto consensus. Kaspa therefore remains a proof-of-work network even though its ledger is not arranged as one conventional chain of blocks.
How Fast Is Kaspa?
Kaspa currently targets 10 blocks per second, or one new block approximately every 0.1 seconds.
This rate became active with the Crescendo hard fork on May 5, 2025. Before Crescendo, the mainnet operated at 1 block per second.
| Period | Target block rate | Approximate interval |
|---|---|---|
| Before Crescendo | 1 block per second | 1 second |
| After Crescendo | 10 blocks per second | 0.1 seconds |
At 10 blocks per second, the network targets approximately:
- 600 blocks per minute;
- 36,000 blocks per hour;
- 864,000 blocks per day.
These numbers describe target block production, not a guaranteed user-facing settlement time.
A transaction can appear in the blockDAG quickly, but an exchange or wallet may wait for additional confirmation score before crediting a deposit. The required waiting period depends on the receiving service, its risk policy, the transaction amount, and current network conditions.
For practical transfer details, see the Kaspa transaction time and confirmations guide.
Does 10 Blocks per Second Mean Instant Transactions?
Not exactly.
Three separate events are often grouped together under the word "confirmation":
- the transaction reaches the Kaspa network;
- the transaction is included and ordered in the blockDAG;
- the receiving wallet or exchange credits the deposit.
The first two are controlled primarily by the network. The third is controlled by the destination service.
An exchange may continue waiting after a transaction appears in a Kaspa explorer. This does not necessarily mean that the transaction is stuck. The platform may be applying its own deposit-confirmation threshold.
Users should therefore check both:
- the transaction status in a Kaspa explorer;
- the deposit requirements published by the receiving platform.
What Mining Algorithm Does Kaspa Use?
Kaspa uses the kHeavyHash proof-of-work mining algorithm.
Miners perform computational work to create candidate blocks. Network nodes validate the submitted blocks and apply the consensus rules to determine how they fit into the blockDAG.
Mining serves two main purposes:
- securing the network against invalid history changes;
- distributing newly issued KAS through block rewards.
Kaspa does not use proof-of-stake validators for base-layer consensus. Holding KAS does not provide a native consensus reward in the same way that staking a proof-of-stake coin may produce validator rewards.
Does Kaspa Use Accounts or UTXOs?
Kaspa uses a UTXO-based transaction model.
UTXO stands for unspent transaction output. Instead of storing every balance as one editable account number, the network tracks spendable outputs created by previous transactions.
For example, a wallet balance of 100 KAS could consist of:
- one UTXO containing 100 KAS;
- two UTXOs containing 40 KAS and 60 KAS;
- many smaller UTXOs that add up to 100 KAS.
When the wallet sends a transaction, it selects enough UTXOs to cover the payment and fee. Any remaining value can be returned as a new change output.
This matters because transactions using many separate UTXOs can have greater transaction mass and may require a higher fee than a simpler transaction.
Kaspa Supply and Tokenomics
Kaspa has an estimated maximum supply of:
28,704,026,601 KAS
This is commonly rounded to 28.7 billion KAS.
Kaspa's source code contains a hard cap below 29 billion KAS. The more precise 28,704,026,601 figure is an emission estimate because minor differences can result from reward rounding, DAA-score transitions, parallel blocks, and the network's early reward phase.
Kaspa Supply Facts
| Supply property | Details |
|---|---|
| Estimated maximum | 28,704,026,601 KAS |
| Rounded maximum | Approximately 28.7 billion KAS |
| Code-level upper boundary | Below 29 billion KAS |
| Preminted supply | 0 KAS |
| Founder allocation | No premine allocation |
| Primary distribution method | Proof-of-work mining |
| Smallest unit | 0.00000001 KAS |
| Smallest unit name | Sompi |
The exact circulating supply changes as miners receive new block rewards. For that reason, a live market-data source should be used when displaying the current circulating amount.
How Does the Kaspa Emission Schedule Work?
Kaspa's monetary policy has two main phases.
Initial Phase
The initial phase began with the mainnet launch on November 7, 2021. During the earliest portion of the launch, rewards varied between 1 and 1,000 KAS per block. The protocol later moved to a constant emission rate equivalent to 500 KAS per second. This pre-deflationary phase ended in May 2022.
Chromatic Phase
The chromatic emission phase began with an initial rate equivalent to 440 KAS per second. Instead of reducing rewards suddenly once every four years, as Bitcoin does, Kaspa reduces its emission smoothly every month.
The monthly reduction factor is:
This equals approximately:
In practical terms, the emission rate declines by approximately 5.61% each month compared with the previous emission period.
After 12 monthly reductions, the emission rate is half of what it was one year earlier. Kaspa therefore has an effective annual halving, but it happens through gradual monthly steps rather than one abrupt reward cut.
| Emission feature | Kaspa model |
|---|---|
| Reward adjustment | Monthly |
| Monthly multiplication factor | Approximately 0.943874 |
| Approximate monthly reduction | 5.61% |
| Annual result | Emission rate halves |
| Distribution | Mining rewards |
The policy defines the number of KAS issued over time rather than requiring one fixed reward per block. When the network moved from 1 to 10 blocks per second, the reward per block was adjusted so that the intended emission rate did not increase tenfold.
Why Is the Emission Schedule Called Chromatic?
The schedule is called chromatic because its monthly reduction factor mirrors the mathematical relationship between neighboring semitones in a 12-tone equal-tempered musical scale.
A musical octave doubles or halves a frequency across 12 equal steps. Kaspa applies a comparable ratio to block-reward emission:
- each month represents one step;
- 12 monthly steps represent one octave;
- after one octave, the emission rate is halved.
The musical terminology does not change how users transact with KAS, but it explains the name of the monetary-policy phase.
Was Kaspa Preminted?
No.
Kaspa launched without a premine, ICO, presale, or predetermined allocation of coins. Every KAS in circulation was produced through mining under the public proof-of-work rules.
This differs from networks that create the full supply before launch and divide it among founders, investors, foundations, ecosystem funds, and public-sale participants.
A fair launch does not mean that every participant mined the same amount. It means that the protocol did not assign a preminted balance to insiders before public mining began.
What Is a Sompi?
A sompi is the smallest unit of KAS.
This is similar to the relationship between Bitcoin and satoshis:
Wallets normally display balances in KAS, while protocol-level calculations can use sompi for precise amounts and fees.
Kaspa vs a Traditional Blockchain
| Feature | Kaspa | Traditional linear PoW chain |
|---|---|---|
| Ledger form | BlockDAG | Single primary chain |
| Parallel blocks | Can coexist and be ordered | Competing blocks may become stale |
| Consensus | GHOSTDAG proof of work | Nakamoto-style longest or heaviest chain |
| Current Kaspa rate | 10 blocks per second | Varies by network |
| Native asset | KAS | Network-specific coin |
| Base consensus staking | No | Usually no for PoW chains |
The main distinction is not simply that Kaspa creates blocks more frequently. Its blockDAG and consensus design are intended to let the network use parallel block production without forcing most concurrent blocks outside the accepted ledger history.
Kaspa vs Bitcoin
Kaspa and Bitcoin share several core characteristics:
- both are Layer 1 networks;
- both use proof of work;
- both use UTXO-based transactions;
- both distribute native coins through mining;
- both have capped supply models;
- neither requires proof-of-stake validators for base consensus.
However, their architectures and monetary schedules differ.
| Feature | Kaspa | Bitcoin |
|---|---|---|
| Native coin | KAS | BTC |
| Ledger architecture | BlockDAG | Linear blockchain |
| Target block rate | 10 per second | Approximately 1 per 10 minutes |
| Reward reduction | Gradual monthly reductions | Abrupt halving about every four years |
| Estimated maximum supply | About 28.7 billion KAS | 21 million BTC |
| Mining algorithm | kHeavyHash | SHA-256 |
| Mainnet launch | November 7, 2021 | January 3, 2009 |
A higher block rate does not by itself make one asset more valuable or more secure. The networks have different histories, levels of adoption, mining ecosystems, and risk profiles.
Does Kaspa Support Staking?
Kaspa does not use staking to secure its base layer.
The network relies on miners and proof of work. Users do not become Kaspa consensus validators by locking KAS, and the protocol does not provide a native proof-of-stake reward simply for holding the coin.
Third-party platforms may use the word "staking" for lending, deposit rewards, liquidity programs, or custodial yield products involving KAS. Those services are separate from Kaspa's base consensus and can introduce counterparty, liquidity, and platform risks.
For a detailed distinction, see Can You Stake Kaspa?
What Does a Native Kaspa Address Look Like?
A native Kaspa address is generated for the Kaspa network and commonly includes a network prefix such as:
The complete address contains a longer sequence of characters after the prefix.
Users should not rely only on the first few characters when verifying a destination. Before sending KAS:
- compare the complete address;
- confirm that the platform supports native KAS;
- verify the network shown on the withdrawal page;
- use copy and paste or a QR code carefully;
- consider sending a small test transaction first when using a new destination.
A wallet address should not be manually converted into an Ethereum, BNB Chain, Bitcoin, or other network address.
More details are available in the Kaspa wallet and address guide.
Before You Send or Receive KAS
Use this checklist before confirming a transaction:
- Confirm that both services support the native Kaspa network.
- Check the full receiving address, not only its beginning or end.
- Review the amount and network fee.
- Confirm whether the destination requires a minimum deposit.
- Check the destination's confirmation or crediting policy.
- Make sure you are not sending a wrapped or bridged asset instead of native KAS.
- Save the transaction ID after sending.
- Use a small test transfer when the destination is unfamiliar.
Native cryptocurrency transfers are generally irreversible. A valid transaction sent to the wrong address usually cannot be cancelled by a wallet provider, miner, explorer, or exchange.
Common Kaspa Misunderstandings
Kaspa and KAS Are Separate Projects
They are not separate projects. Kaspa is the network, while KAS is its native coin.
KAS Is an Ethereum Token
Native KAS is not an ERC-20 token. It exists on the Kaspa Layer 1 network.
Kaspa Uses Proof of Stake
Kaspa uses proof of work and mining. It does not use proof-of-stake validators for base-layer consensus.
Every Parallel Block Is an Orphan
Kaspa's blockDAG design allows parallel blocks to coexist and be ordered. This is one of its main differences from a conventional linear blockchain.
Ten Blocks per Second Means Every Deposit Is Credited in 0.1 Seconds
A 0.1-second target block interval does not guarantee that an exchange will credit a deposit in 0.1 seconds. Receiving platforms apply their own confirmation and risk thresholds.
Kaspa Has Exactly 29 Billion Coins
The code-level cap remains below 29 billion KAS, but the commonly cited estimated maximum is 28,704,026,601 KAS, usually rounded to 28.7 billion.
Kaspa Rewards Drop Once per Year
The annual emission rate halves, but the reduction occurs gradually every month rather than through one annual reward event.
Conclusion
Kaspa is a proof-of-work Layer 1 network that uses a blockDAG and GHOSTDAG consensus instead of arranging all accepted blocks into one traditional linear chain.
Its mainnet launched on November 7, 2021, without a premine, ICO, or presale. Following the Crescendo upgrade on May 5, 2025, the network increased its target rate from 1 to 10 blocks per second.
KAS is the native coin used for transfers, network fees, and mining rewards. Its estimated maximum supply is 28,704,026,601 KAS. Issuance declines by approximately 5.61% each month, producing an effective halving of the emission rate once per year.
For practical use, the most important points are:
- KAS must be sent over the native Kaspa network;
- Kaspa uses mining rather than proof-of-stake validation;
- fast block production does not guarantee immediate exchange crediting;
- addresses, networks, minimum deposits, and confirmation requirements should be checked before every transfer.
FAQ
What is Kaspa crypto?
Kaspa is an open-source proof-of-work Layer 1 network that uses a blockDAG architecture and GHOSTDAG consensus. Its native cryptocurrency is KAS.
What is the Kaspa coin?
KAS is the native coin of the Kaspa network. It is used for transfers, transaction fees, and proof-of-work mining rewards.
Is KAS a coin or a token?
KAS is a coin because it is native to its own Layer 1 network. It is not an ERC-20 or BEP-20 token.
When was Kaspa launched?
The Kaspa mainnet launched on November 7, 2021.
Did Kaspa have a premine or ICO?
No. Kaspa launched without a premine, ICO, private presale, or initial allocation of coins to founders and investors.
How many blocks per second does Kaspa process?
Kaspa currently targets 10 blocks per second. This block rate became active during the Crescendo hard fork on May 5, 2025.
What is the Kaspa block time?
At 10 blocks per second, the target interval between blocks is approximately 0.1 seconds.
What consensus does Kaspa use?
Kaspa uses proof of work and the GHOSTDAG consensus protocol to order blocks in its blockDAG.
What mining algorithm does Kaspa use?
Kaspa uses the kHeavyHash proof-of-work mining algorithm.
What is the maximum Kaspa supply?
Kaspa's estimated maximum supply is 28,704,026,601 KAS, commonly rounded to approximately 28.7 billion KAS.
Why do some sources show 29 billion KAS?
The source code contains a hard boundary below 29 billion KAS. The more precise expected emission is approximately 28.704 billion KAS because of the reward schedule, rounding, DAA transitions, and early network issuance.
How often does Kaspa halve?
Kaspa's emission rate effectively halves once per year, but the decrease occurs gradually. Rewards are reduced every month by a factor of approximately 0.943874, equal to a monthly decline of about 5.61%.
What is the smallest unit of KAS?
The smallest unit is one sompi. One KAS contains 100,000,000 sompi.
How much is a typical Kaspa transaction fee?
Kaspa documentation gives approximately 0.000023 KAS as an example of a typical minimum-fee transaction. The actual fee can change based on transaction mass, UTXO count, wallet settings, and network conditions.
Does Kaspa use staking?
No. Kaspa does not use proof-of-stake staking for base-layer consensus. Its network is secured by proof-of-work miners.
Is Kaspa a blockchain?
Kaspa is a distributed ledger, but its accepted blocks form a blockDAG rather than one conventional linear blockchain. The term "Kaspa blockchain" is often used informally, although blockDAG is the more technically precise description.
Is Kaspa built on Ethereum?
No. Kaspa operates its own Layer 1 network and is not built on Ethereum.
Why is Kaspa considered fast?
Kaspa produces blocks at a target rate of 10 per second and can order parallel blocks through GHOSTDAG. This allows network activity to be recorded more frequently than on many linear proof-of-work chains.
Are Kaspa transactions instant?
Transactions can enter the blockDAG quickly, but final crediting is not guaranteed to be instant. Wallets and exchanges may wait for additional confirmation score before making funds available.
What should I check before sending KAS?
Confirm native Kaspa network support, verify the complete receiving address, review the fee and minimum deposit, and check the destination platform's confirmation requirements.