Is Kaspa Proof of Work?
Yes. Kaspa is mined Proof of Work. It is not Proof of Stake.
FAQ
Start with the answer. Then check the status, term, or source if the answer depends on evidence.
Toccata activated at DAA 474,165,565. The next checks are upgraded-node behavior, wallet support, explorer support, SDK support, app receipts, and user activity.
Common search Is DAGKnight live?No. DAGKnight is a research and upgrade direction. Current mainnet behavior uses GHOSTDAG.
Common search Does Kaspa have smart contracts?No mature Kaspa-native programmability on mainnet yet. The near-term path runs through Toccata and later vProgs.
Common search What is GHOSTDAG?Kaspa's live rule for ordering a blockDAG so parallel honest blocks can contribute to consensus.
Common search Why is KAS cheaper than BTC?Unit price is the wrong comparison. Market cap, adoption, liquidity, and certainty carry more signal.
Common mistakes What needs context?Speed, TPS, finality, testnets, apps, and adoption are different topics.
Live network
Yes. Kaspa is mined Proof of Work. It is not Proof of Stake.
GHOSTDAG is Kaspa's live consensus rule for ordering a blockDAG so parallel honest blocks can contribute to consensus.
It means roughly ten blocks per second in the Crescendo-era network. Throughput and finality still have protocol limits.
Common misconceptions
No. TPS depends on workload and transaction shape. A rough current simple-payment range is about 2.5k to 3.4k TPS, while covenant apps, ZK settlements, tokens, and vProgs need separate measurement context. See Kaspa TPS Explained.
No. Faster blocks can improve inclusion and capacity. Confirmation confidence is separate and still probabilistic.
Real-time means fast mined inclusion and user feel. Finality confidence is still probabilistic.
Testnets and experiments are development evidence. Mainnet guarantees need mainnet evidence.
No. Branches, pull requests, demos, and talks can show progress. Activation needs primary release, KIP, node, or network evidence.
Not by itself. Low fees make experiments cheap; adoption needs durable wallets, integrations, liquidity, apps, recurring users, and fee-paying demand.
Because unit price and valuation differ. Bitcoin has fewer units and a much larger market cap. The market prices Bitcoin as a proven monetary network with deep liquidity, institutional access, custody, derivatives, and global brand. Kaspa is priced more like a promising technical network that still has to prove durable adoption beyond technical merit.
Only if the market is discounting future adoption too heavily. The bullish case is that fast Proof of Work, Toccata, based-app development, and real products eventually create demand the market has not priced. The skeptical case is that Bitcoin already has monetary certainty while Kaspa still has execution, liquidity, wallet, app, and adoption risk.
Usually not. Lead with what works now, then say plainly what depends on future upgrades.
Roadmap and research
Toccata activated at DAA 474,165,565. Rusty Kaspa v2.0.1 is the current Toccata release; v2.0.0 set the activation parameters. Use Toccata status for post-activation checks.
No mature Kaspa-native programmability on mainnet yet. The near-term path runs through Toccata, spend rules, asset rules, ZK proof checks, sequencing commitments, and later vProgs.
Only partly. Atomicity is the boundary: two transactions landing near each other are weaker than one combined operation. Toccata gives Kaspa covenant, ZK, sequencing, and based-zk foundations for fast verifiable coordination. Full app-to-app actions that succeed or fail as one combined operation belong to the later vProgs roadmap.
Not by itself. A proof can show that a circuit checked against chosen inputs. A bridge or oracle-style app still needs an agreed anchor for the outside fact, such as a source-chain light client, finality certificate, accumulated-work view, oracle, reporter set, or challenge process.
No. Direct L1 covenant examples such as vaults, escrow, and assurance contracts can be built on Toccata itself. A based rollup becomes relevant later for richer execution, especially if the path is compatible with vProgs.
No. DAGKnight is a parameterless/adaptive consensus upgrade direction. Current mainnet behavior uses GHOSTDAG.
No. vProgs are roadmap architecture for apps that prove richer rules while sharing Kaspa ordering. Live app infrastructure needs activation and product evidence.
No. The thesis is L1-first: Toccata provides covenant and based-zk rails on Kaspa L1, while apps or runtimes can build on that shared ordering and payment surface. Full vProgs later target app-to-app composition beyond standalone based-zk apps.
No. Native DeFi remains roadmap/application architecture, dependent on future foundations and tooling.
No. Base RTD is Hashdag's real-time PoW framing for Kaspa. Oracles, TangVM, miner attestations, and public group-commitment markets are app-level research ideas built over Kaspa primitives. Product claims need separate implementation evidence.
The research framing uses adversarial or worst-case latency assumptions, including conditions rougher than smooth latency visible during normal network operation.
It means a cohesive, Rust-friendly developer and user experience. Kaspa L1 keeps its own execution model.
Comparison
No. A better short description is: Kaspa is Proof of Work redesigned around parallel blocks. It keeps mined security while using a blockDAG and GHOSTDAG ordering.
No. The live claim is narrower: faster Proof-of-Work inclusion and confirmation dynamics through a blockDAG, with storage, node resources, fees, and future app infrastructure still important.
Current GHOSTDAG has latency assumptions, like other synchronous consensus systems. DAGKnight is the future research direction for removing a fixed protocol latency parameter; it is not live today.
No. Pruning and missing explorer history are not privacy guarantees. UTXO state remains the consensus object, and broadcast transactions can still be observed or archived by others.