-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathstatus.html
More file actions
400 lines (393 loc) · 30.6 KB
/
Copy pathstatus.html
File metadata and controls
400 lines (393 loc) · 30.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
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
<!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="What is live, targeted, roadmap, and research on Kaspa right now, checked against mainnet, releases, and KIPs.">
<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="#000000">
<meta property="og:title" content="Kaspa Status | Kaspa Explained">
<meta property="og:description" content="What is live, targeted, roadmap, and research on Kaspa right now, checked against mainnet, releases, and KIPs.">
<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 on Kaspa right now, checked against mainnet, releases, and KIPs.">
<meta name="twitter:image" content="https://kaspaexplained.com/og-kaspa-explained-20260514.png?v=20260514-logo-clearance">
<meta name="dateModified" content="2026-07-25">
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "TechArticle",
"headline": "Kaspa Status",
"url": "https://kaspaexplained.com/status",
"dateModified": "2026-07-25",
"description": "What is live, targeted, roadmap, and research on Kaspa right now, checked against mainnet, releases, and KIPs.",
"about": ["Kaspa", "Proof of Work", "GHOSTDAG", "Crescendo", "Toccata", "vProgs", "DAGKnight"]
}
</script>
<link rel="stylesheet" href="styles.css?v=20260725-rows-j">
<script defer src="nav.js?v=20260708-dark-default"></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's <a href="/glossary#blockdag">blockDAG</a> keeps every honest block miners produce, and <a href="/glossary#ghostdag">GHOSTDAG</a> orders them into one <a href="/glossary#utxo">UTXO</a> history. This page labels what runs on mainnet today and what is still on the way.</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> July 25, 2026. Public mainnet REST checks reported <code>kaspa-mainnet</code> on a synced v2.0.1 node, virtual DAA score 495,451,121, well above the activation score, about 27.6 billion KAS from the supply endpoint, and a block reward of 2.44997148 KAS under the current emission step. <strong>Toccata:</strong> see the status table below for the release and activation record, and <a href="/toccata-status">Toccata status</a> for post-activation checks.</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-faq">FAQ</a>
</nav>
</section>
<section id="usable-now" class="section">
<p class="eyebrow">Usable today</p>
<h2>What users can do now</h2>
<div class="quick-grid grid-cards">
<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. The <a href="/solo-mining-guide">solo mining guide</a> covers miner-to-node setup; current dashboards cover mining economics and distribution.</p>
</article>
<article>
<span>Build around the live lane</span>
<p>Wallet UX, payment flows, analytics, education, and infrastructure can build on today's 10 BPS foundation.</p>
</article>
<article>
<span>Check the L1 state</span>
<p>A public REST reading is a snapshot. Cross it against a node, release notes, KIP status, and accepted mainnet behavior before treating it as a claim.</p>
</article>
</div>
</section>
<section id="status-snapshot" class="section">
<p class="eyebrow">Snapshot</p>
<h2>Status in one table</h2>
<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 runs on Proof-of-Work mining. Work and issuance never depend on a 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. That's the same model Bitcoin uses; Ethereum tracks balances instead.</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>GHOSTDAG keeps blocks that lose the race to be first instead of discarding them, then orders every kept block into one history.</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>10 blocks per second is live. Michael Sutton put the throughput gain at roughly 8-9x and the confirmation-time improvement around 30%. Neither figure is instant finality, and a flat "10x faster confirmations" claim overstates his own numbers.</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>July 25 L1 snapshot</td>
<td><span class="status-pill live">Live</span></td>
<td>Mainnet REST readout: virtual DAA 495,451,121, about 27.597 billion KAS from the supply endpoint, 2.44997148 KAS per block. The node answering was v2.0.1 and synced. These numbers move by the hour; recheck before quoting them. Skip the block and header counts from this endpoint: it load-balances across backend nodes with different pruning states, so the figure describes whichever backend node answered, and only its local store. Two reads a minute apart returned 1,488,846 and 26,573,222.</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</span></td>
<td>Emission steps down every 2,629,800 seconds by a factor of 2<sup>-1/12</sup>, about 5.61% a step, 426 steps deep in the consensus table. The steps are triggered by DAA score, which is exact, so that is what to quote: 27.5 KAS/sec at DAA 426,015,000, then 25.95654359 at 452,313,000, then 24.49971474 at 478,611,000, which is where the network sits now. The next step is 23.12465141 KAS/sec at DAA 504,909,000, roughly August 5, 2026. Calendar dates drift because they depend on how fast blocks actually land; the DAA triggers do not. No month is a cliff, and August is a routine step identical in kind to May, June, and July.</td>
<td><a href="https://github.com/kaspanet/rusty-kaspa/blob/master/consensus/src/processes/coinbase.rs">coinbase.rs subsidy table</a>; <a href="https://api.kaspa.org/info/blockreward">block reward API</a>; <a href="https://wiki.kaspa.org/en/tokenomics">Kaspa Wiki tokenomics</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 name for Kaspa's core trade: Bitcoin-style PoW security and censorship resistance, with confirmations that feel seconds-scale 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 live">Live</span></td>
<td>Hard fork 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 set mainnet activation at DAA 474,165,565.</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 a single 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 that follows Toccata-era L1 foundations. A live Kaspa-native app layer needs shipped apps and usage evidence beyond the architecture.</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 parameterless, adaptive consensus direction. It does not run mainnet today; GHOSTDAG does.</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 places 10-millisecond blocks, 100 BPS, and partition-resilient local payments in a proposed 2027 hard-fork bucket. No specification, code, release, or activation evidence exists yet.</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>Apps can build oracle, TangVM, attestation, and coordination-market systems over Kaspa primitives. The protocol does not ship any of them as 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 Kaspa confusion comes from one move: blending a live protocol fact, a test result, a public target, and a project headline into a single sentence. Before you repeat a claim, pull those apart.</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 runs roughly 2.5k to 3.4k TPS depending on transaction shape; covenant apps, ZK proofs, tokens, and vProg-style systems each need their own workload number. See <a href="/kaspa-tps-explained">Kaspa TPS Explained</a>.</td>
<td>One number turns 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 shows up, and how sure they should be it stays.</td>
</tr>
<tr>
<td>Testnet or lab numbers are mainnet guarantees.</td>
<td>Testnets and experiments signal direction. They aren't commitments, and need a current source check before they become a live public claim.</td>
<td>Future capability, engineering tests, and shipped network behavior are three different things.</td>
</tr>
<tr>
<td>Real-time means instant finality.</td>
<td>Real-time describes the fast-PoW user feel and the decentralization goal. It does not claim every transaction is instantly irreversible.</td>
<td>The pitch stays strong without overselling settlement certainty.</td>
</tr>
<tr>
<td>DAGKnight, vProgs, or native DeFi are live because code or talks exist.</td>
<td>Code, talks, branches, and demos prove work happened. Activation or production status needs stronger evidence than that.</td>
<td>Development evidence sits below release or activation evidence in the proof hierarchy.</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. Composing separately compiled covenant apps atomically in one transaction turns out to be possible on Toccata itself: Argent's Inter-Covenant Communication does exactly that, so far only in unaudited offline demos. What still separates <a href="/kaspa-vprogs-explained">vProgs</a> is shared mutable state, the case where many users mutate one app state at once.</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>Emission steps down monthly. The status table above lists the exact steps; there is no single-day July cliff.</td>
<td>The scarcity story is the monthly step-down schedule.</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 show work in progress. A mainnet label needs more: a release, an activation record, upgraded-node behavior, or observable network behavior.</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> set the mainnet activation parameters; <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 July 25 check of <a href="https://api-tn10.kaspa.org/info/blockdag">Testnet-10 REST status</a> showed virtual DAA 526,066,399, with 1,491,271 blocks.</td>
<td>Activated mainnet release evidence: release notes, activation parameters, the operator guide, TN10/TN12 testing, SDK and tooling prep. After activation, the next checks are wallets, explorers, examples, and accepted mainnet transactions.</td>
</tr>
<tr>
<td>Toccata KIPs</td>
<td>All four Toccata KIPs now read <code>Status: Active</code> in their raw files: <a href="https://github.com/kaspanet/kips/blob/master/kip-0016.md">KIP-16</a> (New Transaction Opcodes for Verifiable Computation), <a href="https://github.com/kaspanet/kips/blob/master/kip-0017.md">KIP-17</a> (Covenants and Improved Scripting Capabilities), <a href="https://github.com/kaspanet/kips/blob/master/kip-0020.md">KIP-20</a> (Covenant IDs), and <a href="https://github.com/kaspanet/kips/blob/master/kip-0021.md">KIP-21</a> (Partitioned Sequencing Commitment with O(activity) Proving). They moved together in <a href="https://github.com/kaspanet/kips/commit/e4ae2332117b">commit e4ae2332</a> on July 15, 2026. Before that they were scoped to TN10, which is what makes the change worth recording: the spec repo caught up with the mainnet activation.</td>
<td>The KIP status now matches the activation record instead of trailing it. Wallets, explorers, SDKs, and accepted mainnet transactions still carry their own separate evidence.</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/42">KIP-25</a> is open for compute budget on script execution. <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>Worth knowing where the paperwork and the code disagree. Transaction version 1 and <code>computeBudget</code> already run on mainnet and are documented in the operator guide, but the KIPs that specify them, KIP-24 and KIP-25, are still open pull requests. Cite the guide or the node for those two. No merged KIP number exists for them yet. KIP-22 is separate: future cryptography and script-design work with no implementation behind it yet.</td>
</tr>
<tr>
<td>Argent</td>
<td><a href="https://github.com/michaelsutton/argent">michaelsutton/argent</a> is an experimental actor-style frontend for Silverscript covenant contracts: actors, state, transitions, named emits, and terminal <code>become</code> dispatch. It is where most of Michael Sutton's July output went. Thirty-one commits landed between July 8 and July 24, most of the repo's history, adding Inter-Covenant Communication, actor enums, commitment-forest route planning, and a VS Code extension. Two sibling repos appeared: <a href="https://github.com/michaelsutton/argent-playground">argent-playground</a> on July 9 and <a href="https://github.com/michaelsutton/argent-template">argent-template</a> on July 24. Examples now run well past the original Stones and Tickets.</td>
<td>An active prototype. No audit, no release, no tag, no crates.io publish. Two commits in the last fortnight are labelled breaking changes, so the ABI is still moving. A runtime transaction builder does exist now, <code>argent-runtime</code>'s <code>TxBuilder</code> and <code>TxContext</code>, which the README lists under what is useful today; what is still missing is generated app-specific builder APIs. The playground demos, including the DEX one, run fully offline against hardcoded fixtures with no node or RPC connection, so none of them is a deployment.</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 now. Production Kaspa app paths and native DeFi still need their own 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. Mainnet still runs GHOSTDAG; live finality and higher-BPS claims need their own 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 that helps Python builders and integrators prepare for Toccata-era wallet, UTXO, lane-proof, and covenant workflows. Protocol-upgrade status still comes from node, KIP, and activation evidence. An SDK release does not move it.</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 that could help wallets, explorers, indexers, and large app-state workflows once merged. Until then it is an open pull request.</td>
</tr>
</tbody>
</table>
</div>
</details>
</section>
<section id="status-faq" class="section">
<p class="eyebrow">FAQ</p>
<h2>Common status questions</h2>
<div class="reference-grid grid-cards">
<article>
<h3>Is DAGKnight live?</h3>
<p>No. DAGKnight is a parameterless, adaptive consensus direction still in research. Mainnet runs GHOSTDAG.</p>
</article>
<article>
<h3>Is Toccata live?</h3>
<p>Yes. Activation and adoption are separate questions, though: check <a href="/toccata-status">Toccata status</a> before quoting wallet, explorer, or app state.</p>
</article>
<article>
<h3>Are Kaspa smart contracts live?</h3>
<p>Toccata put the L1 pieces live on mainnet: spend rules, asset rules, ZK proof checks, and sequencing commitments. A mature native app layer, with audited apps and broad tooling, is still ahead; richer programmability through vProgs is later work.</p>
</article>
</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-developments"><span>Next</span><strong>What changed in Kaspa this month</strong><p>What changed in Kaspa since Toccata activated: the new KCC conventions process, the KIP promotions of July 15, Argent, vProgs, SDK...</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>