-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathfaq.html
More file actions
274 lines (266 loc) · 19.6 KB
/
Copy pathfaq.html
File metadata and controls
274 lines (266 loc) · 19.6 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>Kaspa FAQ | Kaspa Explained</title>
<meta name="description" content="Direct answers to common Kaspa questions and misconceptions: Toccata, DAGKnight, smart contracts, TPS, 10 BPS, GHOSTDAG, blockDAG, vProgs, and RTD.">
<meta name="robots" content="index,follow,max-snippet:-1,max-image-preview:large">
<link rel="canonical" href="https://kaspaexplained.com/faq">
<link rel="icon" href="kaspa-favicon.svg?v=20260512-real-k" type="image/svg+xml">
<link rel="icon" href="favicon.svg?v=20260512-k4" type="image/svg+xml">
<link rel="icon" href="favicon.ico" sizes="any">
<link rel="icon" href="favicon.png" type="image/png">
<link rel="apple-touch-icon" href="apple-touch-icon.png">
<link rel="manifest" href="site.webmanifest">
<meta name="application-name" content="Kaspa Explained">
<meta name="apple-mobile-web-app-title" content="Kaspa Explained">
<meta name="theme-color" content="#09090b">
<meta property="og:title" content="Kaspa FAQ | Kaspa Explained">
<meta property="og:description" content="Direct answers to common Kaspa questions, with current-use and future-work claims separated.">
<meta property="og:type" content="article">
<meta property="og:url" content="https://kaspaexplained.com/faq">
<meta property="og:image" content="https://kaspaexplained.com/og-kaspa-explained-20260514.png?v=20260514-logo-clearance">
<meta property="og:image:type" content="image/png">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Kaspa Explained - proof-of-work blockDAG guide">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Kaspa FAQ | Kaspa Explained">
<meta name="twitter:description" content="Direct answers to common Kaspa questions, with current-use and future-work claims separated.">
<meta name="twitter:image" content="https://kaspaexplained.com/og-kaspa-explained-20260514.png?v=20260514-logo-clearance">
<meta name="dateModified" content="2026-06-28">
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Is Toccata live on Kaspa?",
"acceptedAnswer": {"@type": "Answer", "text": "No. As of June 28, 2026, Rusty Kaspa v2.0.1 is the current Toccata release, while v2.0.0 provides the activation parameters: DAA score 474,165,565, roughly June 30, 2026 at 16:15 UTC. Activation remains scheduled."}
},
{
"@type": "Question",
"name": "Is DAGKnight live on Kaspa?",
"acceptedAnswer": {"@type": "Answer", "text": "No. DAGKnight is a parameterless/adaptive consensus research and upgrade direction. Current Kaspa mainnet behavior uses GHOSTDAG."}
},
{
"@type": "Question",
"name": "Are Kaspa smart contracts live?",
"acceptedAnswer": {"@type": "Answer", "text": "No mature Kaspa-native programmability on mainnet yet. Kaspa's near-term build route runs through Toccata, spend rules, asset rules, ZK proof checks, sequencing commitments, and later vProgs."}
},
{
"@type": "Question",
"name": "Does Toccata allow one action across multiple apps?",
"acceptedAnswer": {"@type": "Answer", "text": "Not fully. Toccata is the foundation for richer Kaspa app rules, based-zk applications, and proof-based coordination. Full atomic app-to-app composition belongs to the later vProgs roadmap."}
},
{
"@type": "Question",
"name": "Does Kaspa need a based rollup for the first Toccata apps?",
"acceptedAnswer": {"@type": "Answer", "text": "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."}
},
{
"@type": "Question",
"name": "What does 10 BPS mean on Kaspa?",
"acceptedAnswer": {"@type": "Answer", "text": "10 BPS means roughly ten blocks per second in the Crescendo-era network. Throughput and finality still have protocol limits."}
},
{
"@type": "Question",
"name": "Does 10 BPS prove a fixed TPS number?",
"acceptedAnswer": {"@type": "Answer", "text": "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."}
},
{
"@type": "Question",
"name": "Does real-time mean instant finality?",
"acceptedAnswer": {"@type": "Answer", "text": "Real-time means fast mined inclusion and user feel. Finality confidence is still probabilistic."}
},
{
"@type": "Question",
"name": "Does Kaspa require super-fast internet?",
"acceptedAnswer": {"@type": "Answer", "text": "Current GHOSTDAG, like other synchronous consensus systems, has latency assumptions. DAGKnight is the research direction intended to remove a fixed protocol latency parameter, but it is not live today."}
},
{
"@type": "Question",
"name": "Does pruning make Kaspa private?",
"acceptedAnswer": {"@type": "Answer", "text": "No. Pruning and missing spent-transaction history in explorers are not privacy guarantees. UTXO state remains the consensus object, and broadcast transactions can still be observed."}
},
{
"@type": "Question",
"name": "What does Solana-like mean for Kaspa apps?",
"acceptedAnswer": {"@type": "Answer", "text": "It means an intended cohesive developer and user experience, with Rust-friendly app development and verifiable-program architecture. Kaspa L1 keeps its own execution model."}
}
]
}
</script>
<link rel="stylesheet" href="styles.css?v=20260627-next-card-fix">
<script defer src="nav.js?v=20260606-anchor-clearance"></script>
</head>
<body>
<a class="skip-link" href="#top">Skip to content</a>
<header class="site-header">
<nav class="nav" aria-label="Primary">
<a class="brand" href="/" aria-label="Kaspa Explained home">
<span class="brand-mark" aria-hidden="true"></span>
Kaspa Explained
</a>
<button class="nav-menu-button" type="button" aria-expanded="false" aria-controls="primary-links">Menu</button>
<div id="primary-links" class="nav-links">
<a href="/what-is-kaspa">What is Kaspa</a>
<a href="/status">Live now</a>
<a href="/kaspa-claims-checker">Check claims</a>
<a href="/skeptical-case">Risks</a>
<a href="/build-on-kaspa">Build</a>
<a href="/sources">Sources</a>
</div>
<button class="theme-toggle" type="button" aria-label="Switch theme">Light</button>
<a class="nav-cta" href="/toccata-status">Toccata status</a>
</nav>
</header>
<main id="top" tabindex="-1" class="status-page">
<section class="status-hero section">
<p class="eyebrow">FAQ</p>
<h1>Direct answers to common Kaspa questions</h1>
<p class="lead">Short careful answers first. Status, glossary, and sources carry the details.</p>
</section>
<section class="path-grid" aria-label="Common Kaspa searches">
<a href="#toccata-live">
<span>Common search</span>
<strong>Is Toccata live?</strong>
<p>No. v2.0.1 is the current Toccata release; v2.0.0 schedules activation for DAA 474,165,565, roughly June 30, 2026 at 16:15 UTC.</p>
</a>
<a href="#dagknight-live">
<span>Common search</span>
<strong>Is DAGKnight live?</strong>
<p>No. DAGKnight is a research and upgrade direction. Current mainnet behavior uses GHOSTDAG.</p>
</a>
<a href="#smart-contracts-live">
<span>Common search</span>
<strong>Does Kaspa have smart contracts?</strong>
<p>No mature Kaspa-native programmability on mainnet yet. The near-term path runs through Toccata and later vProgs.</p>
</a>
<a href="#ghostdag">
<span>Common search</span>
<strong>What is GHOSTDAG?</strong>
<p>Kaspa's live rule for ordering a blockDAG so parallel honest blocks can contribute to consensus.</p>
</a>
<a href="#kaspa-bitcoin-valuation">
<span>Common search</span>
<strong>Why is KAS cheaper than BTC?</strong>
<p>Unit price is the wrong comparison. Market cap, adoption, liquidity, and certainty carry more signal.</p>
</a>
<a href="#common-misconceptions">
<span>Common mistakes</span>
<strong>What needs context?</strong>
<p>Speed, TPS, finality, testnets, apps, and adoption are different topics.</p>
</a>
</section>
<section class="section">
<p class="eyebrow">Live network</p>
<h2>What is live now?</h2>
<div class="reference-grid">
<article><h3>Is Kaspa Proof of Work?</h3><p>Yes. Kaspa is mined Proof of Work. It is not Proof of Stake.</p></article>
<article id="ghostdag"><h3>What is GHOSTDAG?</h3><p>GHOSTDAG is Kaspa's live consensus rule for ordering a blockDAG so parallel honest blocks can contribute to consensus.</p></article>
<article><h3>What does 10 BPS mean?</h3><p>It means roughly ten blocks per second in the Crescendo-era network. Throughput and finality still have protocol limits.</p></article>
</div>
</section>
<section id="common-misconceptions" class="section">
<p class="eyebrow">Common misconceptions</p>
<h2>Short corrections for claims that spread fast</h2>
<div class="reference-grid">
<article id="tps-number"><h3>Does 10 BPS prove a fixed TPS number?</h3><p>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 <a href="/kaspa-tps-explained">Kaspa TPS Explained</a>.</p></article>
<article><h3>Does 10 BPS mean 10x finality?</h3><p>No. Faster blocks can improve inclusion and capacity. Confirmation confidence is separate and still probabilistic.</p></article>
<article><h3>Does real-time mean instant finality?</h3><p>Real-time means fast mined inclusion and user feel. Finality confidence is still probabilistic.</p></article>
<article><h3>Do testnet numbers count as mainnet?</h3><p>Testnets and experiments are development evidence. Mainnet guarantees need mainnet evidence.</p></article>
<article><h3>Does code activity mean activation?</h3><p>No. Branches, pull requests, demos, and talks can show progress. Activation needs primary release, KIP, node, or network evidence.</p></article>
<article><h3>Does low fee usage prove adoption?</h3><p>Not by itself. Low fees make experiments cheap; adoption needs durable wallets, integrations, liquidity, apps, recurring users, and fee-paying demand.</p></article>
<article id="kaspa-bitcoin-valuation"><h3>Why is one KAS so much cheaper than one BTC?</h3><p>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.</p></article>
<article><h3>Could that mean Kaspa is underpriced?</h3><p>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.</p></article>
<article><h3>Does a roadmap idea belong in the headline?</h3><p>Usually not. Lead with what works now, then say plainly what depends on future upgrades.</p></article>
</div>
</section>
<section class="section">
<p class="eyebrow">Roadmap and research</p>
<h2>Still pending</h2>
<div class="reference-grid">
<article id="toccata-live"><h3>Is Toccata live?</h3><p>No. As of June 28, 2026, Rusty Kaspa v2.0.1 is the current Toccata release; v2.0.0 schedules activation at DAA score 474,165,565, roughly June 30, 2026 at 16:15 UTC. Current mainnet DAA is still below that score. Activation remains scheduled.</p></article>
<article id="smart-contracts-live"><h3>Are Kaspa smart contracts live?</h3><p>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.</p></article>
<article id="cross-app-composition"><h3>Does Toccata allow one action across multiple apps?</h3><p>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.</p></article>
<article><h3>Can a ZK proof prove what happened on another chain?</h3><p>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.</p></article>
<article><h3>Does Kaspa need a based rollup for the first Toccata apps?</h3><p>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.</p></article>
<article id="dagknight-live"><h3>Is DAGKnight live?</h3><p>No. DAGKnight is a parameterless/adaptive consensus upgrade direction. Current mainnet behavior uses GHOSTDAG.</p></article>
<article><h3>Are vProgs live?</h3><p>No. <a href="/kaspa-vprogs-explained">vProgs are roadmap architecture</a> for apps that prove richer rules while sharing Kaspa ordering. Live app infrastructure needs activation and product evidence.</p></article>
<article><h3>Does Toccata mean external L2s are required?</h3><p>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.</p></article>
<article><h3>Is native Kaspa DeFi live?</h3><p>No. Native DeFi remains roadmap/application architecture, dependent on future foundations and tooling.</p></article>
<article><h3>Are RTD-derived oracle or TangVM flows live?</h3><p>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.</p></article>
<article><h3>Does DAGKnight use observed latency?</h3><p>The research framing uses adversarial or worst-case latency assumptions, including conditions rougher than smooth latency visible during normal network operation.</p></article>
<article><h3>What does Solana-like mean?</h3><p>It means a cohesive, Rust-friendly developer and user experience. Kaspa L1 keeps its own execution model.</p></article>
</div>
</section>
<section class="section">
<p class="eyebrow">Comparison</p>
<h2>How should Kaspa be described?</h2>
<div class="reference-grid">
<article><h3>Is Kaspa just Bitcoin but faster?</h3><p>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.</p></article>
<article><h3>Does Kaspa solve every scaling problem?</h3><p>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.</p></article>
<article><h3>Does Kaspa require super-fast internet?</h3><p>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.</p></article>
<article><h3>Does pruning make Kaspa private?</h3><p>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.</p></article>
</div>
</section>
<section class="next-step section" aria-label="Suggested next step">
<p class="eyebrow">Next step</p>
<h2>Next reading path</h2>
<p>If the words in this FAQ are unfamiliar, start from zero. If you only need shipped-vs-roadmap status, use the status table.</p>
<div class="actions">
<a class="button primary" href="/start-here">Start from zero</a>
<a class="button" href="/status">Open status</a>
</div>
</section>
<!-- related-links:start -->
<section class="section site-related" aria-labelledby="related-links-title">
<p class="eyebrow">Keep reading</p>
<h2 id="related-links-title">Next pages</h2>
<div class="site-related-grid">
<a href="/ghostdag-explained"><span>Previous</span><strong>GHOSTDAG explained</strong><p>GHOSTDAG explained in plain English: how Kaspa orders parallel proof-of-work blocks in a blockDAG without claiming instant finality.</p></a>
<a href="/why-kaspa-matters"><span>Next</span><strong>Kaspa's design case</strong><p>How Kaspa's design maps to neutral money, self-custody, fast payment feel, and public rules people can inspect.</p></a>
<a href="/status"><span>Status</span><strong>Kaspa current status</strong><p>A compact status page for Kaspa: what is live, what is targeted, what is roadmap, what remains research, and which common claims need context.</p></a>
</div>
</section>
<!-- related-links:end -->
</main>
<footer class="footer">
<div class="footer-grid">
<p><strong>Independent Kaspa explainer.</strong> Claims are labeled live, targeted, roadmap, research, unsupported, or wrong. Not investment advice.</p>
<nav class="footer-nav-groups" aria-label="Footer">
<div class="footer-link-group" aria-label="Learn">
<span>Learn</span>
<a href="/start-here">Start here</a>
<a href="/what-is-kaspa">Kaspa 101</a>
<a href="/overview">90-second overview</a>
<a href="/glossary">Glossary</a>
</div>
<div class="footer-link-group" aria-label="Verify">
<span>Verify</span>
<a href="/status">Status</a>
<a href="/kaspa-claims-checker">Claims checker</a>
<a href="/toccata-status">Toccata status</a>
<a href="/skeptical-case">Skeptical case</a>
<a href="/sources">Sources</a>
</div>
<div class="footer-link-group" aria-label="Build">
<span>Build</span>
<a href="/build-on-kaspa">Build on Kaspa</a>
<a href="/builder-guide">Builder guide</a>
<a href="/kaspa-app-ideas">App ideas</a>
</div>
<div class="footer-link-group" aria-label="Site">
<span>Site</span>
<a href="/search">Search</a>
<a href="/about">About</a>
<a href="/about#corrections">Corrections</a>
</div>
</nav>
</div>
</footer>
</body>
</html>