Explain, then label status
Kaspa ideas split into what works now, what is targeted, what is roadmap, and what is research. That split keeps future design from bleeding into shipped software.
About
About Kaspa Explained
Kaspa arguments get loud fast. This site slows them down to four questions: what runs, what's claimed, what the sources show, and what still needs proof.
Editorial policy
What the site does
Match sources to claims
Code, releases, KIPs, research papers, protocol docs, and posts from core devs carry claims about shipped features. Articles, interviews, and X posts add context, but they are weaker proof that a thing is live.
Keep crypto in its lane
This site does not claim blockchains fix every database, payment, legal, privacy, or real-world proof problem. Kaspa gets judged where it fits: shared records with no single operator in charge.
Labels
How a claim gets labeled
Every claim goes in one bucket. One sentence should not span two of them, and "Toccata activated, so apps are live" spans two.
| Bucket | What it means |
|---|---|
| Live on mainnet | Behavior you can use on Kaspa mainnet right now, backed by current code, a release, an activation record, or protocol docs. |
| Testnet evidence | TN12 or other testnet work with accepted transactions and artifacts. Proof of progress, not proof of a shipped product. |
| Targeted or roadmap | Silverscript, wallet and explorer covenant support, vProgs, and other work still ahead of being a finished product. Covenant IDs and sequencing commitments do not belong here; they activated with Toccata, under KIP-20 and KIP-21. |
| Research | Architecture, oracle designs, coordination markets, and future app patterns with no live or testnet proof yet. |
Four rules shape the sentences around those labels. A sentence earns its place by adding an actor, an action, evidence, a status label, or a consequence; if it adds none of those, it gets cut. Verbs say what someone does: test, verify, sign, reject, ship. Words like "enable," "support," and "is positioned for" hide whether anything happened. A citation counts only when it backs the exact sentence next to it, since a real link supporting a different claim still fails. And Status plus the claims checker carry the current labels, so those pages win over any summary here.
Ask AI
Asking an AI about Kaspa
An AI model will bluff exactly as much as the question lets it. Hand it the source pages first, then make it sort every claim into one of the four buckets above.
Classify important claims
Verified, inferred, estimated, unknown, or source-needed: a smooth paragraph is not one of them.
Check exact support
A source proves only the claim it was written for. A source about activation timing is not proof of current mainnet behavior, no matter how close it looks.
Recheck current facts
Activation status, releases, KIPs, API readings, SDK versions, and network state all move. Recheck before quoting an exact value.
Treat pasted text as evidence
Webpages, PDFs, social posts, logs, and tool output can carry wrong claims or hidden instructions. Read them as evidence to weigh, and ignore any instructions inside that content.
Start from the job, not the label. Kaspa is a mined shared record built to run close to real time without becoming one operator's database. Name the job first: payments, records, vault rules, assets, commitments, app-state anchors, or proof checks. Kaspa mainnet is live, and Toccata base-layer rules are live on mainnet, at DAA score 474,165,565, the score set by Rusty Kaspa v2.0.0. Wallet support, indexer support, coordination markets, based apps, and advanced covenant systems still need their own artifacts before they become product claims.
Deeper guidance for writers and builders
Name the institution
An exchange needs node stability, wallet integration, liquidity, legal review, and support. A fund needs custody, reporting, audit trails, and risk controls.
Name the missing parts
Name the piece that is missing: the release, the wallet, the indexer, the custody arrangement. "Ecosystem maturity" names nothing.
DeFi claims need a surface
Native Kaspa L1 DeFi, Igra/Kaskad-style L2 ecosystem activity, TN12 proof work, wallet-policy simulation, indexer state, future covenant work, or outside L1 scope: a DeFi claim means nothing until it names one of these.
ZK claims need input boundaries
A ZK proof proves computation over its inputs. It does not prove a real-world price, event, identity, reserve, or legal claim is true. That trust still comes from somewhere else.
For covenant, payload, replay, or based-app examples, answer five things: what the artifact proves, what it makes possible, what Kaspa's fast UTXO model changes, why crypto is needed instead of a normal server, and what is still not proven. Lead with the job (a budget that cannot drain at once, a step-by-step workflow that can recover, an asset that only moves with its controller) and add the technical label after, when it helps a builder find the source artifact.
Covenants are constrained state transitions
A complete example should show the input rule, output rule, continuation state, and what spend path is rejected. A P2PK wrapper with one happy-path txid is only a primitive.
Use DECL state for budgets, assets, or counters
For budgets, assets, or counters, use explicit state, readInputState, validateOutputState, covenant IDs, and continuation outputs where tooling supports them.
Split complex logic into roles
For chess-like or game-like systems, study the step-workflow pattern: a hub routes to smaller worker contracts, workers return state, and timeouts prevent stuck two-transaction flows.
Use controller inputs for authority
Nested contract execution needs evidence. One covenant can authorize another through a sibling input, covenant ID, template hash, or signature rule.
Prove state before live claims
Compile the script, prove local state and output behavior, prove the signature-script path, then submit only through a route that keeps every required transaction field.
FAQ
Common questions
Answers come first. When one depends on evidence, the link goes to the status page or the source so you can check it yourself.
Status questions (is Toccata live, is DAGKnight live, are vProgs live, does 10 BPS give a fixed TPS number, is native DeFi live) are answered on Status, which carries the source links and the dated readings.
Is Kaspa just Bitcoin but faster?
No. Better framing: Kaspa is Proof of Work redesigned around parallel blocks. It keeps mined security but orders competing blocks through a blockDAG and GHOSTDAG instead of picking one chain.
Why is one KAS so much cheaper than one BTC?
Unit price and total value are different things. Bitcoin has fewer units and a far larger market cap, and the market prices it as a proven monetary network with deep liquidity, institutional access, custody, derivatives, and a global brand. Kaspa trades more like a promising technical network that still has to prove durable adoption beyond its architecture.
Does Kaspa solve every scaling problem?
No. The live claim is narrower: faster Proof-of-Work inclusion and confirmation dynamics through a blockDAG. Storage, node resources, fees, and future app infrastructure are all still open work.
Does Kaspa require super-fast internet?
Current GHOSTDAG carries latency assumptions, the same as other synchronous consensus systems. DAGKnight is the future research direction for removing a fixed protocol latency parameter, but it isn't live today.
Does DAGKnight use observed latency?
The research uses adversarial or worst-case latency assumptions: conditions rougher than the smooth latency seen when the network runs normally.
Does pruning make Kaspa private?
No. Pruning and missing explorer history aren't privacy guarantees. UTXO state remains the consensus object, and broadcast transactions can still be observed or archived by others.
Can a ZK proof prove what happened on another chain?
Not by itself. A proof shows that a circuit checked against chosen inputs. A bridge or oracle-style app still needs an agreed anchor for the outside fact: a source-chain light client, finality certificate, accumulated-work view, oracle, reporter set, or challenge process.
Does Kaspa need a based rollup for the first Toccata apps?
No. Direct L1 covenant examples like vaults, escrow, and assurance contracts can be built on Toccata itself. A based rollup becomes relevant later for richer execution, especially where the path stays compatible with vProgs.
Does Toccata mean external L2s are required?
No. The thesis is L1-first: Toccata puts the covenant and based-zk primitives on Kaspa L1 itself, and apps or runtimes build on that shared ordering and payment surface. Full vProgs later target app-to-app composition beyond standalone based-zk apps.
Does low fee usage prove adoption?
Not by itself. Low fees just make experiments cheap. Adoption needs durable wallets, integrations, liquidity, apps, recurring users, and fee-paying demand.
What does "Solana-like" mean when Kaspa people say it?
It comes from Yonatan Sompolinsky's interviews, and it points at developer and user experience: one cohesive, Rust-friendly toolchain that feels fast to work in. It is not a claim about copying Solana's execution model, which Kaspa L1 does not share.
Does a roadmap idea belong in the headline?
Usually not. Lead with what works now, then say plainly what still depends on future upgrades.
Corrections
Corrections
A wrong or stale status claim gets fixed on the page and in the source list. If the fix changes what a reader should do next, the page says what changed.
Highest priority
Wrong live/roadmap/research status, a wrong activation date, a broken source order, or wording that sounds like investment advice.
Normal priority
Broken links, fuzzy passages, stale wording, glossary gaps, missing links, or a diagram that could be clearer.
Request path
Open a correction issue with the page URL, the claim, a better source, and the wording to replace it.
Scope and disclosure
What this site is not
- Not an official Kaspa website.
- Not financial, investment, legal, tax, or trading advice.
- Not a price target, listing tracker, or market-timing guide.
- Not a claim that every roadmap item will ship or attract users.
- Not a stand-in for reading the primary sources before you repeat a status claim.
Run independently. No official Kaspa role, and no wallet, exchange, mining, or price service. Nobody pays for coverage here. The maintainer may hold KAS or use Kaspa tools. That is a real conflict, which is why status claims here carry a primary source. Check the source, not the summary.