Reported by `api.kaspa.org/info/coinsupply`.
Independent explainer
What is Kaspa?
Kaspa is a live proof-of-work network that uses a blockDAG instead of a single chain. Miners can create blocks in parallel, and GHOSTDAG orders those blocks into one shared payment history.
This site separates what is live today, what is targeted for activation, what is roadmap, and what still needs evidence.
New to crypto itself? Start with Start Here.
Toccata status
Activation scheduled
Rusty Kaspa v2.0.1 is the current Toccata release. Rusty Kaspa v2.0.0 set the activation target at DAA score 474,165,565, roughly June 30, 2026 at 16:15 UTC. The June 27 check still had mainnet below that score.
Open Toccata Explained for what changes, Toccata status for the activation check, or Smart-Contract Status for app wording. Primary sources: Rusty Kaspa v2.0.1 release and v2.0.0 activation release.
BlockDAG model
Compare the chain and the graph
A simplified model of one selected chain versus a graph that can include parallel blocks before ordering them.
Network readout
Current network snapshot
Live API readout for orientation. Use a node, explorer, source, or proof path for independent verification.
If the live readout stalls, treat the cards below as temporarily unavailable and use Status and Sources for durable claims.
Circulating supply divided by max supply.
Current blockDAG count from the network readout.
Kaspa's ordering-height style progress marker.
Kaspa.org publishes the fair-launch proof path: empty genesis UTXO set, Bitcoin timestamp anchors, checkpoint linkage, and scheduled emission after the Nov. 22, 2021 checkpoint.
Extra checks: run the proof, REST API docs, and DAGVIZ.
Waiting for live data.
Status
Live, testnet, roadmap, research
Check whether the claim is live mainnet, testnet evidence, roadmap, or research before repeating it.
Build path
What can be built now?
Money movement is live. Receipts and source-verifiable reads can be built today. Toccata brings covenant rules and richer proof-based app foundations into the next build path.
Wallets, payments, receipts, exchange flows, mining/node visibility, and better confirmation-risk UX.
Apps can show txid, amount, address, accepted status, source, timestamp, and fallback verification links.
Vault limits, delays, escrow, assurance contracts, asset rules, and bounded UTXO state machines are the near-term app surface.
Markets, lending, funding rules, attestations, and shared commitments need richer app-state, custody, oracle, and proof paths.
For the full path, open the builder guide.
Transaction path
Wallet to confirmation
A transaction is created, broadcast, mined, ordered, then gains confirmation confidence.
Wallet prepares inputs, outputs, amount, and fee.
The transaction reaches nodes and miners.
A miner includes it in a proof-of-work block.
The block joins the DAG and GHOSTDAG orders history.
Confidence increases with more accepted work and time.