Reported by `api.kaspa.org/info/coinsupply`.
Kaspa guide
What is Kaspa?
Kaspa is a live Proof of Work blockDAG network. It keeps Bitcoin-style mining and UTXO ownership, and uses GHOSTDAG to order parallel blocks into one payment history.
This site tracks what Kaspa does today, what upgrades are being worked on, and which public claims need checking.
Choose your path
Start where your question starts.
Use one route at a time: beginner basics, short Kaspa answer, claim check, skeptical review, builder work, or source-backed writing.
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 stronger 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.
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. Covenant rules and richer proof-based apps need more activation evidence.
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 need activation evidence.
Markets, lending, funding rules, attestations, and shared commitments need stronger app-state, custody, oracle, and proof paths.
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. It is fast, not instantly irreversible.