-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathstatus.html
More file actions
534 lines (524 loc) · 38.5 KB
/
Copy pathstatus.html
File metadata and controls
534 lines (524 loc) · 38.5 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
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>Kaspa Status | Kaspa Explained</title>
<meta name="description" content="A compact status page for Kaspa: what is live, what is targeted, what is roadmap, what remains research, and which common claims need context.">
<meta name="robots" content="index,follow,max-snippet:-1,max-image-preview:large">
<link rel="canonical" href="https://kaspaexplained.com/status">
<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 Status | Kaspa Explained">
<meta property="og:description" content="What is live, targeted, roadmap, and research in Kaspa without mixing shipped features with future architecture.">
<meta property="og:type" content="article">
<meta property="og:url" content="https://kaspaexplained.com/status">
<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 Status | Kaspa Explained">
<meta name="twitter:description" content="What is live, targeted, roadmap, and research in Kaspa without mixing shipped features with future architecture.">
<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": "TechArticle",
"headline": "Kaspa Status",
"url": "https://kaspaexplained.com/status",
"dateModified": "2026-06-28",
"description": "A compact status page for what is live, targeted, roadmap, research, and commonly misunderstood in Kaspa.",
"about": ["Kaspa", "Proof of Work", "GHOSTDAG", "Crescendo", "Toccata", "vProgs", "DAGKnight"]
}
</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">Current status</p>
<h1>Kaspa current status</h1>
<p class="lead">Kaspa is live as a mined <a href="/glossary#utxo">UTXO</a> network where a <a href="/glossary#blockdag">blockDAG</a> and <a href="/glossary#ghostdag">GHOSTDAG</a> order parallel blocks. This page is scoped to L1 protocol status: live mainnet behavior, Toccata readiness, emissions, and roadmap boundaries.</p>
<div class="status-legend" aria-label="Status legend">
<span class="legend-label">Legend</span>
<span class="status-pill live">Live</span>
<span class="status-pill target">Targeted</span>
<span class="status-pill roadmap">Roadmap</span>
<span class="status-pill research">Research</span>
<span class="status-pill not-live">Not live</span>
</div>
<p class="fit-note"><strong>Checked:</strong> June 28, 2026 at 17:56 UTC. A public mainnet REST snapshot reported <code>kaspa-mainnet</code>, virtual DAA score 472,496,562, 1,457,413 blocks, about 27.540 billion KAS from the supply endpoint, and a 2.59565436 KAS block reward. <strong>Toccata:</strong> Rusty Kaspa v2.0.1 is the current Toccata release; v2.0.0 set the mainnet activation target at DAA score 474,165,565, roughly June 30, 2026 at 16:15 UTC. Activation remains scheduled.</p>
<nav class="jump-list" aria-label="Status page shortcuts">
<a href="#usable-now">Usable now</a>
<a href="#status-snapshot">Status table</a>
<a href="#common-misconceptions">Misconceptions</a>
<a href="/kaspa-claims-checker">Claims checker</a>
<a href="/toccata-status">Toccata</a>
<a href="#implementation-evidence">Implementation evidence</a>
<a href="#status-changelog">Changelog</a>
<a href="#status-faq">FAQ</a>
</nav>
</section>
<section class="section">
<p class="eyebrow">Freshness triggers</p>
<h2>What would change this page</h2>
<div class="summary-grid">
<article><span>Toccata activation</span><p>Rusty Kaspa v2.0.1 is the current Toccata release. The activation target still comes from v2.0.0. Post-activation node behavior and mainnet observations would move claims out of the pending lane.</p></article>
<article><span>Mainnet behavior</span><p>Observable accepted mainnet transactions using the new rules carry better evidence than testnet examples or roadmap posts.</p></article>
<article><span>L1 source drift</span><p>Mainnet API readings, Rusty Kaspa releases, KIP states, and emission-schedule checkpoints should be refreshed before quoting exact values.</p></article>
</div>
<p class="fit-note">Use the <a href="/kaspa-status-updates">Status Updates</a> page for dated snapshots. Use this page for the current public wording standard.</p>
</section>
<section id="usable-now" class="section">
<p class="eyebrow">Usable today</p>
<h2>What users can do now</h2>
<div class="quick-grid">
<article>
<span>Hold and transfer</span>
<p>Send, receive, and self-custody KAS on the live Proof-of-Work UTXO blockDAG.</p>
</article>
<article>
<span>Verify and observe</span>
<p>Run or study nodes, explorers, visualizers, pruning behavior, and GHOSTDAG ordering.</p>
</article>
<article>
<span>Mine or study mining</span>
<p>Kaspa is ASIC-mined today; mining economics and distribution should be checked with current dashboards.</p>
</article>
<article>
<span>Build around the live lane</span>
<p>Wallet UX, payment flows, analytics, education, and infrastructure can use today's 10 BPS foundation.</p>
</article>
<article>
<span>Check the L1 state</span>
<p>Compare public REST readings with a node, release notes, KIP status, and accepted mainnet behavior before turning a snapshot into a claim.</p>
</article>
</div>
</section>
<section id="status-snapshot" class="section">
<p class="eyebrow">Snapshot</p>
<h2>Status in one table</h2>
<p>If you only remember one rule, remember the split: live mainnet behavior, testnet evidence, targeted upgrade work, roadmap architecture, and research are different statements.</p>
<div class="summary-grid">
<article>
<span>Live network</span>
<p>PoW, UTXO, GHOSTDAG, Crescendo 10 BPS, and base real-time PoW framing.</p>
</article>
<article>
<span>June 28 L1 check</span>
<p>Mainnet API readings showed virtual DAA score 472,496,562, 1,457,413 blocks, about 27.540 billion KAS, and 2.59565436 KAS per block.</p>
</article>
<article>
<span>Emission path</span>
<p>Emission steps down monthly. May 2026 is 27.5 KAS/sec; June 7 shifts to 25.9565436 KAS/sec. This is not a one-day July cliff.</p>
</article>
</div>
<div class="table-wrap">
<table class="reality-table status-snapshot">
<thead>
<tr>
<th>Feature / idea</th>
<th>Status</th>
<th>Plain meaning</th>
<th>Anchor source</th>
</tr>
</thead>
<tbody>
<tr>
<td>Proof of Work</td>
<td><span class="status-pill live">Live</span></td>
<td>Kaspa is mined. Work and issuance are external to any validator identity set.</td>
<td><a href="https://github.com/kaspanet/rusty-kaspa">rusty-kaspa</a></td>
</tr>
<tr>
<td>UTXO model</td>
<td><span class="status-pill live">Live</span></td>
<td>Kaspa tracks spendable outputs; Ethereum tracks global account balances.</td>
<td><a href="https://github.com/kaspanet/rusty-kaspa">rusty-kaspa</a></td>
</tr>
<tr>
<td>GHOSTDAG</td>
<td><span class="status-pill live">Live</span></td>
<td>The live ordering rule that lets parallel blocks contribute to consensus.</td>
<td><a href="https://research.kas.pa/">Kaspa Research</a></td>
</tr>
<tr>
<td>Crescendo 10 BPS</td>
<td><span class="status-pill live">Live</span></td>
<td>The 10 blocks-per-second era is live. Michael Sutton framed throughput as roughly 8-9x higher and confirmation-time improvement around 30%. Instant-finality claims and exact 10x confirmation-improvement claims overstate that source.</td>
<td><a href="https://github.com/kaspanet/rusty-kaspa/releases">rusty-kaspa releases</a>; <a href="https://medium.com/@michaelsuttonil/unveiling-the-crescendo-hard-fork-roadmap-10bps-and-more-6072329e177f">Crescendo roadmap note</a>; <a href="https://kaspa.org/lore">Kaspa.org lore</a></td>
</tr>
<tr>
<td>June 28 L1 snapshot</td>
<td><span class="status-pill live">Live snapshot</span></td>
<td>Public mainnet REST readout at 17:56 UTC: virtual DAA 472,496,562; 1,457,413 blocks; about 27.540 billion KAS from the supply endpoint; 2.59565436 KAS per block. Recheck before quoting exact numbers.</td>
<td><a href="https://api.kaspa.org/info/blockdag">mainnet blockDAG API</a>; <a href="https://api.kaspa.org/info/coinsupply">supply API</a>; <a href="https://api.kaspa.org/info/blockreward">block reward API</a></td>
</tr>
<tr>
<td>Emission schedule</td>
<td><span class="status-pill live">Live design</span></td>
<td>The official schedule steps down monthly: 27.5 KAS/sec from May 8, 2026, 25.9565436 KAS/sec from June 7, and 24.49971475 KAS/sec from July 7. Avoid "July emission cliff" wording.</td>
<td><a href="https://wiki.kaspa.org/en/tokenomics">Kaspa Wiki tokenomics</a>; <a href="https://api.kaspa.org/info/blockreward">block reward API</a></td>
</tr>
<tr>
<td>Base RTD framing</td>
<td><span class="status-pill live">Live</span></td>
<td>Real-time decentralization is Hashdag's framing for Kaspa's core edge: Bitcoin-style PoW security and censorship-resistance goals with seconds-scale confirmation feel under normal network conditions.</td>
<td><a href="https://kaspa.org/lore">Kaspa.org lore</a>; <a href="https://hashd.ag/raw">hashd.ag/raw</a></td>
</tr>
<tr>
<td>Toccata</td>
<td><span class="status-pill target">Targeted</span></td>
<td>Hard-fork track for L1 spend rules, asset rules, Silverscript, ZK proof checks, sequencing commitments, standalone based-zk applications, and vProgs groundwork. Rusty Kaspa v2.0.1 is the current Toccata release; v2.0.0 schedules mainnet activation at DAA 474,165,565; the June 28 mainnet DAA readout remains below that activation score.</td>
<td><a href="https://github.com/kaspanet/rusty-kaspa/releases/tag/v2.0.1">v2.0.1 release</a>; <a href="https://github.com/kaspanet/rusty-kaspa/releases/tag/v2.0.0">v2.0.0 activation release</a>; <a href="https://github.com/kaspanet/rusty-kaspa/blob/master/docs/toccata-guide.md">Toccata guide</a>; <a href="https://github.com/kaspanet/rusty-kaspa/releases/tag/tn10-toc3">tn10-toc3 release</a>; <a href="https://github.com/kaspanet/kips">Kaspa KIPs</a></td>
</tr>
<tr>
<td>vProgs</td>
<td><span class="status-pill roadmap">Roadmap</span></td>
<td><a href="/kaspa-vprogs-explained">Apps that prove richer logic</a> while sharing Kaspa ordering, without turning L1 into one global execution VM.</td>
<td><a href="https://github.com/kaspanet/vprogs">vProgs repo</a>; <a href="https://docs.kaspa.org/programmability">programmability docs</a></td>
</tr>
<tr>
<td>Native DeFi</td>
<td><span class="status-pill roadmap">Roadmap</span></td>
<td>A design target after Toccata-era L1 foundations. Mature live Kaspa-native app-layer claims need shipped app and usage evidence.</td>
<td><a href="/why-kaspa-matters">Design case</a></td>
</tr>
<tr>
<td>DAGKnight</td>
<td><span class="status-pill research">Research</span></td>
<td>A major parameterless/adaptive consensus direction. It is not current mainnet behavior.</td>
<td><a href="https://kaspa.org/lore">Kaspa.org lore</a>; <a href="https://hashd.ag/">hashd.ag</a></td>
</tr>
<tr>
<td>100 BPS / partition-resilient payments</td>
<td><span class="status-pill research">Research</span></td>
<td>Kaspa.org now places 10 millisecond blocks, 100 BPS work, and partition-resilient local payment flows in a proposed 2027 hard-fork bucket. Treat this as roadmap/research until specifications, code, releases, and activation evidence exist.</td>
<td><a href="https://kaspa.org/lore">Kaspa.org lore</a></td>
</tr>
<tr>
<td>RTD-derived oracle / TangVM flows</td>
<td><span class="status-pill research">Research</span></td>
<td>Oracle, TangVM, attestation, and coordination-market systems can be built by apps over Kaspa primitives, but they are not protocol-prescribed products.</td>
<td><a href="https://hashd.ag/raw">hashd.ag/raw</a></td>
</tr>
</tbody>
</table>
</div>
</section>
<section id="common-misconceptions" class="section">
<p class="eyebrow">Common misconceptions</p>
<h2>Statements that need context or measurement</h2>
<p class="lead">Most confusion comes from mixing live protocol facts, test results, public targets, app headlines, project headlines, and research into one claim. Use these checks before repeating a Kaspa claim.</p>
<div class="table-wrap">
<table class="reality-table">
<thead>
<tr>
<th>Claim people repeat</th>
<th>Measured version</th>
<th>Consequence</th>
</tr>
</thead>
<tbody>
<tr>
<td>Mainnet speed means a fixed huge TPS number.</td>
<td>10 BPS is live. Simple-payment capacity is roughly 2.5k to 3.4k TPS under transaction-shape assumptions, while covenant apps, ZK proofs, tokens, and vProg-style systems need their own workload labels. See <a href="/kaspa-tps-explained">Kaspa TPS Explained</a>.</td>
<td>A single number can turn a real technical edge into a brittle marketing claim.</td>
</tr>
<tr>
<td>Block rate alone gives an exact finality multiplier.</td>
<td>Faster blocks improve inclusion and capacity. Confirmation confidence is a separate probabilistic question.</td>
<td>Users care about both when a payment appears and how confident they should be that it will not reverse.</td>
</tr>
<tr>
<td>Testnet or lab numbers are mainnet guarantees.</td>
<td>Testnets and experiments are signals. They need current source context before being used as live public claims.</td>
<td>Future capability, engineering tests, and shipped network behavior should not be flattened.</td>
</tr>
<tr>
<td>Real-time means instant finality.</td>
<td>Real-time is the fast-PoW user-feel and decentralization frame. It is not a claim that every transaction is instantly irreversible.</td>
<td>This keeps the pitch strong without overselling settlement certainty.</td>
</tr>
<tr>
<td>DAGKnight, Toccata, vProgs, or native DeFi are live because code or talks exist.</td>
<td>Code, talks, branches, and demos are evidence of work. Activation or production status needs stronger primary evidence.</td>
<td>Development evidence belongs below release or activation evidence.</td>
</tr>
<tr>
<td>Toccata means one atomic action can already span several independent apps.</td>
<td>Toccata is the foundation for covenant rules, ZK proof checks, sequencing commitments, and based-zk applications. Full cross-app atomic composition belongs to later vProgs.</td>
<td>Fast L1 coordination and same-operation app composability are different claims.</td>
</tr>
<tr>
<td>July 2026 is a sudden emission cliff.</td>
<td>Kaspa emission steps down monthly. The official schedule shows 27.5 KAS/sec from May 8, 25.9565436 from June 7, and 24.49971475 from July 7.</td>
<td>The scarcity story should use the actual schedule instead of a dramatic one-day cliff claim.</td>
</tr>
<tr>
<td>Open KIPs or branches prove an upgrade is activated.</td>
<td>Open KIPs, branches, and pre-releases are development evidence. Activation needs release artifacts, activation parameters, upgraded node behavior, and observable mainnet behavior.</td>
<td>This keeps the upgrade story grounded in primary L1 evidence instead of roadmap momentum.</td>
</tr>
</tbody>
</table>
</div>
</section>
<section id="implementation-evidence" class="section">
<p class="eyebrow">Implementation evidence</p>
<h2>Code evidence</h2>
<p>Code and pull requests are not activation records. They show what is being tested, polished, or prototyped before a public status label changes.</p>
<details class="source-more">
<summary>Open code and implementation evidence</summary>
<div class="table-wrap">
<table class="reality-table">
<thead>
<tr>
<th>Track</th>
<th>Recent public evidence</th>
<th>How to read it</th>
</tr>
</thead>
<tbody>
<tr>
<td>Toccata / Silverscript</td>
<td><a href="https://github.com/kaspanet/silverscript/commit/627c175ed808c46471ee3c4b2907661e24aec9b2">TN12 dependency sync</a>, <a href="https://github.com/kaspanet/silverscript/commit/38ff79864d7a4dd47890d11e62c3da0e0c2108bc">KCC20 bootstrap fixes</a>, and <a href="https://github.com/kaspanet/silverscript/commit/06928a76e68b3bbd82968643670d99b07fc471db">book/build fixes</a> landed May 4-5, 2026. <a href="https://github.com/kaspanet/rusty-kaspa/issues/983">TN12 field testing</a> surfaced developer-ergonomics issues around covenant and ZK opcode use. The <a href="https://github.com/kaspanet/rusty-kaspa/releases/tag/v1.3.0-toc.5">v1.3.0-toc.5 pre-release</a> sanity-tested mainnet pre-activation compatibility. The <a href="https://github.com/kaspanet/rusty-kaspa/releases/tag/v2.0.0">v2.0.0 release</a> schedules mainnet activation at DAA score 474,165,565; <a href="https://github.com/kaspanet/rusty-kaspa/releases/tag/v2.0.1">v2.0.1</a> is the current Toccata release. The <a href="https://github.com/kaspanet/rusty-kaspa/blob/master/docs/toccata-guide.md">Toccata node setup guide</a> adds operator guidance for upgrades, fee policy, API field changes, and Testnet-10 checks. The merged <a href="https://github.com/kaspanet/rusty-kaspa/pull/953">Rusty Kaspa ZK SDK PR</a> adds an <code>R0ScriptBuilder</code> wrapper for turning RISC Zero receipts into Kaspa scripts. The <a href="https://github.com/kaspanet/rusty-kaspa/releases/tag/tn10-toc3">tn10-toc3 pre-release</a> scheduled final TN10 hardening; a June 28 check of <a href="https://api-tn10.kaspa.org/info/blockdag">Testnet-10 REST status</a> showed virtual DAA 503,106,976.</td>
<td>Released and scheduled. Toccata is not live until mainnet reaches the activation score and post-activation behavior is observable. Current evidence includes release notes, activation parameters, the operator guide, TN10/TN12 testing, and SDK/tooling preparation.</td>
</tr>
<tr>
<td>Toccata KIPs</td>
<td><a href="https://kaspa.org/build#developments">Kaspa.org Build</a> lists sequencing commitments in the Toccata bundle and labels it live on TN12 ahead of mainnet activation. Raw KIP checks on June 28 showed <a href="https://github.com/kaspanet/kips/blob/master/kip-0016.md">KIP-16</a> and <a href="https://github.com/kaspanet/kips/blob/master/kip-0020.md">KIP-20</a> as proposed plus implemented and activated in TN10, and <a href="https://github.com/kaspanet/kips/blob/master/kip-0017.md">KIP-17</a> and <a href="https://github.com/kaspanet/kips/blob/master/kip-0021.md">KIP-21</a> as implemented and activated in TN10. Open KIP PRs add important future context: <a href="https://github.com/kaspanet/kips/pull/41">KIP-24</a> specifies transaction version 1 fields and hashing for compute budgets, covenant bindings, user lanes, and ZK-friendly payload/rest txids; <a href="https://github.com/kaspanet/kips/pull/37">KIP-22</a> proposes P2MR ScriptPublicKey work for quantum-resistance and MAST-style scripts.</td>
<td>Targeted design and testnet implementation evidence. TN10 KIP status does not make Toccata live on mainnet; mainnet wording still waits for activation and observable post-activation behavior.</td>
</tr>
<tr>
<td>Open KIP PRs</td>
<td><a href="https://github.com/kaspanet/kips/pull/41">KIP-24</a> is open for transaction version 1 fields and hashing; its draft text says v1 transactions add per-input compute budgets, optional output covenant bindings, user-lane subnetworks, and a BLAKE3 payload/rest txid split for ZK and based-executor workflows. <a href="https://github.com/kaspanet/kips/pull/37">KIP-22</a> is open for P2MR ScriptPublicKey, described as a Merkle-root pay-to-script form meant to hide public keys until spend time and support quantum-resistance and MAST-style conditional scripts.</td>
<td>Design and implementation evidence. Merged-KIP and mainnet activation claims need separate evidence. KIP-24 is closer to Toccata transaction plumbing; KIP-22 is future cryptography/script-design work.</td>
</tr>
<tr>
<td>Argent</td>
<td><a href="https://github.com/michaelsutton/argent">michaelsutton/argent</a> is a June 2026 experimental actor-style frontend for Silverscript covenant contracts. Its README describes actors, state, transitions, named emits, terminal <code>become</code> dispatch, and generated Silverscript for examples such as Stones and Tickets.</td>
<td>Fresh research/tooling evidence. It is explicit prototype work. Audit, production readiness, stable ABI, generated transaction builder, launch-proof tooling, and mainnet activation evidence remain absent.</td>
</tr>
<tr>
<td>vProgs</td>
<td>The <a href="https://github.com/kaspanet/vprogs">kaspanet/vprogs</a> README describes an early-development Rust framework for based computation on Kaspa, with core, storage, state, scheduling, transaction-runtime, and node layers. A June 18 merge, <a href="https://github.com/kaspanet/vprogs/pull/36">Feat: Settlement into Covenants</a>, gathered settlement-covenant work, transaction/batch/aggregation provers, SMT support, L1 bridge plumbing, and RISC Zero backend work into master.</td>
<td>Roadmap implementation progress. Builders can study and experiment with the framework. Production Kaspa app paths and native DeFi need separate shipped evidence. See <a href="/kaspa-vprogs-explained">vProgs Explained</a>.</td>
</tr>
<tr>
<td>DAGKnight</td>
<td>The public <a href="https://github.com/kaspanet/rusty-kaspa/tree/dagknight">rusty-kaspa dagknight branch</a> shows March 22, 2026 commits for free-search support, ranking/search refinements, conflict-zone work, tie-breaking placeholder, and UMC majority-coverage movement.</td>
<td>Research and prototype evidence. Current mainnet behavior remains GHOSTDAG; live finality and higher-BPS claims need separate activation evidence.</td>
</tr>
<tr>
<td>Builder tooling</td>
<td><a href="https://github.com/kaspanet/kaspa-python-sdk">kaspanet/kaspa-python-sdk</a> is now a standalone public SDK repo. The <a href="https://github.com/kaspanet/kaspa-python-sdk/releases/tag/v2.0.0">v2.0.0 release</a> added Toccata-aligned support and the full Rusty Kaspa managed-wallet API for Python. The <a href="https://github.com/kaspanet/kaspa-python-sdk/releases/tag/v2.0.1">v2.0.1 release</a> adds <code>get_seq_commit_lane_proof</code>, SMT sync progress events, covenant-binding fixes, and a Rusty Kaspa v2.0.1 dependency bump.</td>
<td>Developer-tooling progress. Protocol-upgrade status still comes from node, KIP, and activation evidence. It helps Python builders and integrators prepare for Toccata-era wallet, UTXO, lane-proof, and covenant workflows.</td>
</tr>
<tr>
<td>Infrastructure indexes</td>
<td><a href="https://github.com/kaspanet/rusty-kaspa/pull/860">rusty-kaspa PR #860</a> is open for review. It proposes an optional <code>--txindex</code>, a GetTransaction RPC path, inclusion and acceptance metadata, live updates from consensus notifications, resync from scratch, and pruning tied to retention-root changes.</td>
<td>Builder and infrastructure work. It could help wallets, explorers, indexers, and large app-state workflows. It remains an open pull request until merged and released.</td>
</tr>
</tbody>
</table>
</div>
</details>
<p class="fit-note"><strong>Builder note:</strong> early tests and open PRs are signals for developers. They stay below release or activation evidence until a primary artifact changes the status.</p>
</section>
<section id="status-changelog" class="section">
<p class="eyebrow">Changelog</p>
<h2>Status-sensitive updates</h2>
<details class="source-more">
<summary>Open status changelog</summary>
<div class="reference-grid">
<article>
<h3>May 4, 2026</h3>
<p>Separated base RTD framing from downstream oracle, TangVM, and coordination-market ideas. Base RTD is treated as Hashdag's real-time PoW framing for Kaspa; RTD-derived app systems remain app-level research or architecture work.</p>
</article>
<article>
<h3>May 4, 2026</h3>
<p>Marked Toccata as targeted with the then-current mid-June public window. This was later superseded by the June 5 v2.0.0 release, which schedules activation at DAA score 474,165,565.</p>
</article>
<article>
<h3>May 5, 2026</h3>
<p>Added the Crescendo nuance: 10 BPS is separate from confirmation improvement. Public summaries should distinguish roughly 8-9x throughput improvement from faster, still probabilistic, confirmation dynamics.</p>
</article>
<article>
<h3>May 5, 2026</h3>
<p>Clarified why Toccata moved from the older May 5 target: sequencing commitments needed to be finalized before zk systems and runtimes depend on them. The current release source is now v2.0.0.</p>
</article>
<article>
<h3>May 6, 2026</h3>
<p>Added code-grounded implementation evidence for the Toccata/Silverscript, vProgs, and DAGKnight tracks. These notes describe current development; activation status still comes from release and network evidence.</p>
</article>
<article>
<h3>May 6, 2026</h3>
<p>Added Python SDK and TxIndex as builder/infrastructure evidence. These help developers and indexers while leaving protocol status unchanged.</p>
</article>
<article>
<h3>May 15, 2026</h3>
<p>Added the redesigned Kaspa.org source frame: real-time decentralization as the official north star, Toccata next, DAGKnight after Toccata, and 2027 work around 100 BPS plus partition-resilient payment flows. Kept 100 BPS and partition-resilience in the research/roadmap lane.</p>
</article>
<article>
<h3>May 15, 2026</h3>
<p>Added KIP-21 and infrastructure notes from the current source list. Sequencing commitments are targeted/TN12 evidence, while production API/indexer choices remain builder-infrastructure decisions.</p>
</article>
<article>
<h3>May 18, 2026</h3>
<p>Updated TN10 wording after checking the Testnet-10 REST API. TN10 had passed the tn10-toc2 activation score, which is testnet evidence and still not mainnet activation evidence.</p>
</article>
<article>
<h3>May 20, 2026</h3>
<p>Refreshed the page as an L1-only status check. Added mainnet API readings, block reward, supply, smooth emission-schedule wording, TN10/Toccata status, and open KIP guardrails; removed app and project tooling from the main status table.</p>
</article>
<article>
<h3>June 2, 2026</h3>
<p>Refreshed mainnet API readings and Toccata guardrails. Added tn10-toc3 final TN10 hardening evidence and TN10 KIP status while keeping mainnet activation in the pending lane.</p>
</article>
<article>
<h3>June 5, 2026</h3>
<p>Updated the Toccata boundary after Rusty Kaspa v2.0.0 was released. The release schedules mainnet activation at DAA score 474,165,565, roughly June 30, 2026 at 16:15 UTC. Current mainnet DAA is still below that score, so activation remains scheduled.</p>
</article>
<article>
<h3>June 15, 2026</h3>
<p>Refreshed the mainnet REST snapshot to virtual DAA 461,207,885, 1,403,205 blocks, about 27.511 billion KAS, and 2.59565436 KAS per block. Added a dedicated vProgs explainer and updated the vProgs evidence boundary from a commit-burst note to the current public README architecture.</p>
</article>
<article>
<h3>June 20, 2026</h3>
<p>Refreshed the mainnet snapshot to virtual DAA 465,403,885, 1,277,659 blocks, about 27.522 billion KAS, and 2.59565436 KAS per block. Updated Toccata wording for Rusty Kaspa v2.0.1 while keeping v2.0.0 as the activation-parameter source. Added Argent as early Silverscript research/tooling evidence.</p>
</article>
<article>
<h3>June 21, 2026</h3>
<p>Refreshed the mainnet snapshot to virtual DAA 466,400,699, 1,410,360 blocks, about 27.524 billion KAS, and 2.59565436 KAS per block. Added the Rusty Kaspa Toccata node setup guide as operator and integrator evidence for upgrades, fee policy, API field changes, pools, miners, exchanges, wallets, explorers, and Testnet-10 checks.</p>
</article>
<article>
<h3>June 23, 2026</h3>
<p>Refreshed the mainnet snapshot to virtual DAA 467,931,952, 1,213,420 blocks, about 27.528 billion KAS, and 2.59565436 KAS per block. Rechecked the Rusty Kaspa release API, Toccata guide, KIP-16/17/20/21 raw files, Testnet-10 REST status, vProgs README, and Argent README.</p>
</article>
<article>
<h3>June 25, 2026</h3>
<p>Refreshed the mainnet snapshot to virtual DAA 469,680,863, 1,234,055 blocks, about 27.533 billion KAS, and 2.59565436 KAS per block. Added Python SDK v2.0.0/v2.0.1, merged Rusty Kaspa ZK SDK PR #953, vProgs settlement-into-covenants PR #36, open KIP-24 transaction-v1/ZK-prover context, open KIP-22 P2MR quantum-resistance context, and the Toccata Explained route.</p>
</article>
<article>
<h3>June 28, 2026</h3>
<p>Refreshed the mainnet snapshot to virtual DAA 472,496,562, 1,457,413 blocks, about 27.540 billion KAS, and 2.59565436 KAS per block. Rechecked Rusty Kaspa v2.0.1/v2.0.0, the Toccata guide, Testnet-10 REST status, KIP-16/17/20/21 raw files, vProgs README, Argent README, and kaspa-python-sdk releases; no mainnet activation status change. After activation, scheduled wording should change only where the DAA target and post-activation behavior support it.</p>
</article>
<article>
<h3>June 26, 2026</h3>
<p>Refreshed the mainnet snapshot to virtual DAA 470,805,556, 1,494,605 blocks, about 27.536 billion KAS, and 2.59565436 KAS per block. Rechecked Rusty Kaspa v2.0.1, Testnet-10 REST status, KIP-16/17/20/21 raw files, KIP-24, and KIP-22; no mainnet activation status change.</p>
</article>
</div>
</details>
</section>
<section id="status-faq" class="section">
<p class="eyebrow">FAQ</p>
<h2>Common status questions</h2>
<div class="reference-grid">
<article>
<h3>Is DAGKnight live?</h3>
<p>No. DAGKnight is a parameterless/adaptive consensus upgrade direction. Current mainnet behavior uses GHOSTDAG.</p>
</article>
<article>
<h3>Is Toccata live?</h3>
<p>No. Rusty Kaspa v2.0.1 is the current Toccata release, and 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>
<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>
<h3>Are cross-app actions live?</h3>
<p>Not as full atomic app-to-app composition. Toccata can improve fast, verifiable coordination through L1 foundations; later vProgs target richer actions across app boundaries.</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>After checking shipped status, use the compact thesis for sharing, or the adoption page to evaluate progress without relying on price.</p>
<div class="actions">
<a class="button primary" href="/kaspa-in-one-screen">Kaspa in one screen</a>
<a class="button" href="/adoption-metrics">Adoption metrics</a>
<a class="button" href="/start-here">Start from zero</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="/what-crypto-is-good-for"><span>Previous</span><strong>What crypto is good for</strong><p>A tempered guide to where crypto is useful, where it is weak, and where shared records without one operator fit.</p></a>
<a href="/kaspa-claims-checker"><span>Next</span><strong>Kaspa claims checker</strong><p>Kaspa claims checker for common public claims: smart contracts, Toccata, DAGKnight, 10 BPS, finality, emissions, DeFi, covenants, and vProgs.</p></a>
<a href="/sources"><span>Sources</span><strong>Sources for Kaspa Explained</strong><p>Source hierarchy, public reference map, and credited external learning resources used by Kaspa Explained.</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>