Kaspa (KAS)
Unlock Schedule
Kaspa (KAS) Token Unlock & Vesting Schedule
The chart shows gross modeled releases of every allocation: vesting unlocks, new issuance and reserve distributions, each allocation counted once. These have different meanings; a scheduled release is not evidence that tokens entered circulation or were sold. Review the coverage, sources and assumptions below.
Each color segment in the chart corresponds to a specific allocation group described in the Allocations section below. Underlying assumptions and data models used to reconstruct this schedule are explained in detail under Assumptions, while broader utility insights and token use cases are covered in Tokenomics & Utility.
Tokenomics & Utility
Supply and distribution
Kaspa’s planned maximum supply is approximately 28.7 billion KAS. New coins enter circulation through mining rewards. Its “chromatic” emission schedule reduces the reward in small monthly steps, with the scheduled reward roughly halving over each year. That makes new issuance decline gradually rather than through a single large annual cut. (wiki.kaspa.org)
The launch method shaped who could receive the first coins. There was no launch allocation set aside for founders or private-sale buyers. Earlier funding of DAGLabs was funding for development, while any KAS obtained by the company and its backers after launch came through mining on the public network. Community members have also funded some development projects with voluntary contributions. (wiki.kaspa.org)
KAS has two direct jobs in the protocol: it is the coin people transfer, and it pays transaction fees. Mining rewards bring new coins into circulation and give miners a reason to provide computing power. As scheduled issuance falls, transaction fees remain another source of payment for miners. KAS holders do not need to lock coins to operate the network; block creation uses proof of work. (wiki.kaspa.org)
Assumptions
Kaspa launched without a premine: new KAS enters circulation through proof-of-work mining rewards that decline roughly monthly. The chart shows an explicitly rough estimate for the launch period and dated projections from Kaspa’s published emission table, not a measurement of every coin mined. Mining continues beyond that table’s last displayed month, so its remaining release dates and totals are left open. Named community-funded development and Ledger budgets concern redistribution of coins already mined; their recipient-payment dates are not established and they must not be added to new supply.
- PoW Block Rewards: New issuance depends on network activity, such as staking, so it cannot be dated in advance.
- Community-funded Rust Rewrite: Releases depend on recipients claiming tokens or on grants being awarded.
- Community-funded DAGKnight Development: Releases depend on recipients claiming tokens or on grants being awarded.
- Ledger Integration Crowdfund: The sources give the amount but no release dates.
- Ledger Kudelski Security Audit Crowdfund: The sources give the amount but no release dates.
- 1. https://wiki.kaspa.org/en/tokenomics
- 2. https://kaspa.org/wp-content/uploads/2022/09/KASPA-EMISSION-SCHEDULE.pdf
- 3. https://github.com/kaspanet/rusty-kaspa/blob/master/consensus/src/processes/coinbase.rs
- 4. https://github.com/kaspanet/rusty-kaspa/blob/master/consensus/core/src/config/params.rs
- 5. https://github.com/kaspanet/kaspad/blob/master/domain/consensus/utils/constants/constants.go
- 6. https://wiki.kaspa.org/en/funding-process-concept
- 7. https://wiki.kaspa.org/en/faq
- 8. https://wiki.kaspa.org/en/timeline
- 9. https://kaspa.org/
Allocations
Description
#75
Kaspa is a decentralized, open-source proof-of-work cryptocurrency that implements the innovative GHOSTDAG protocol. Unlike traditional blockchains, GHOSTDAG allows blocks created in parallel to coexist and be ordered by consensus, resulting in Kaspa being the first blockDAG.
| Sector: | Layer 1 |
| Blockchain: | Other L1 |