-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathbuilder-evidence.html
More file actions
322 lines (312 loc) · 17.3 KB
/
Copy pathbuilder-evidence.html
File metadata and controls
322 lines (312 loc) · 17.3 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
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>How to Prove a Kaspa Builder Claim | Kaspa Explained</title>
<meta name="description" content="How to prove a Kaspa builder claim: status label, source, artifact, user-visible result, and remaining blocker.">
<meta name="robots" content="index,follow,max-snippet:-1,max-image-preview:large">
<link rel="canonical" href="https://kaspaexplained.com/builder-evidence">
<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="How to Prove a Kaspa Builder Claim | Kaspa Explained">
<meta property="og:description" content="Status lane, source, artifact, user-visible result, and remaining blocker for Kaspa builder claims.">
<meta property="og:type" content="article">
<meta property="og:url" content="https://kaspaexplained.com/builder-evidence">
<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="How to Prove a Kaspa Builder Claim | Kaspa Explained">
<meta name="twitter:description" content="How builders can prove a Kaspa claim without mixing mainnet, testnet, and roadmap evidence.">
<meta name="twitter:image" content="https://kaspaexplained.com/og-kaspa-explained-20260514.png?v=20260514-logo-clearance">
<meta name="dateModified" content="2026-06-25">
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "TechArticle",
"headline": "How to Prove a Kaspa Builder Claim",
"url": "https://kaspaexplained.com/builder-evidence",
"dateModified": "2026-06-25",
"description": "How builders can prove a Kaspa claim without mixing mainnet, testnet, and roadmap evidence.",
"about": ["Kaspa", "Proof", "Evidence", "Verification", "Sources", "Status"]
}
</script>
<link rel="stylesheet" href="styles.css?v=20260624-card-hover">
<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="builder-page">
<section class="section">
<p class="eyebrow">Builder evidence</p>
<h1>How to prove a Kaspa builder claim.</h1>
<p class="lead">A builder claim needs a status label, a source, an artifact, a user-visible result, and a blocker list before it becomes product copy.</p>
<p class="fit-note"><strong>Use this for demo proof.</strong> Use <a href="/kaspa-claims-checker">Claims Checker</a> for protocol status. Use <a href="/reality-check">Reality Check</a> for app or product pitches before they become public claims.</p>
</section>
<section class="section">
<h2>Proof ladder.</h2>
<div class="summary-grid">
<article><span>Claim</span><p>Write the exact sentence a reader will believe or repeat.</p></article>
<article><span>Status lane</span><p>Label it live, testnet-only, targeted, roadmap, research, wrong, or unsupported.</p></article>
<article><span>Source</span><p>Point to the strongest available source for that lane.</p></article>
<article><span>Artifact</span><p>Name the txid, branch, release, KIP, demo, indexer result, or command output.</p></article>
<article><span>User-visible result</span><p>Say what a wallet user, builder, miner, or operator can actually observe.</p></article>
<article><span>Remaining blocker</span><p>List what still prevents a broader public claim.</p></article>
</div>
</section>
<section class="section">
<h2>Evidence lanes.</h2>
<p>Kaspa claims split into <strong>mainnet features, near-term upgrades, and early design work</strong>. Each lane needs a different proof level.</p>
<ul style="margin-left: 1.5rem; margin-top: 1rem;">
<li><strong>Live:</strong> code merged, activated on mainnet, available to builders now</li>
<li><strong>Targeted:</strong> scheduled for near-term release or being implemented</li>
<li><strong>Roadmap:</strong> architecture approved or research-backed, not yet scheduled</li>
<li><strong>Research:</strong> in exploration, no timeline or approval yet</li>
</ul>
<p style="margin-top: 1rem;">Keep builder tooling, open code, and mainnet activation separate. They are three different states.</p>
<details class="source-more">
<summary>Advanced state-transition proof note</summary>
<p>For state-transition proof models, the pattern is selected-parent root plus current root plus leaf write witnesses. That keeps validation local to the transition instead of forcing clients to maintain the whole incremental SMT.</p>
</details>
</section>
<section class="section">
<h2>Start here for verification.</h2>
<div class="reference-grid">
<article>
<h3><a href="/status">Status page</a></h3>
<p>Compact shipped-vs-roadmap status with a code-grounded implementation evidence section. Covers covenants, Toccata, vProgs, Crescendo, DAGKnight, and common misconceptions.</p>
</article>
<article>
<h3><a href="/sources">Sources & Reference Map</a></h3>
<p>Public source hierarchy: protocol sources, core technical contributors, Kaspa.com Learn Kaspa, KIPs, research papers, and supporting site files for claim verification.</p>
</article>
<article>
<h3><a href="/claims-reference">Claims reference</a></h3>
<p>Browser-readable status labels for live mainnet behavior, testnet evidence, targeted upgrades, roadmap work, and research.</p>
</article>
<article>
<h3><a href="/kaspa-claims-checker">Claims checker</a></h3>
<p>Fast route for checking whether a public Kaspa claim is live, testnet-only, targeted, roadmap, research, unsupported, or outside L1 scope.</p>
</article>
</div>
</section>
<section class="section">
<h2>Builder categories and their evidence sources.</h2>
<details class="source-more">
<summary>Show verification links</summary>
<div class="table-wrap">
<table class="reality-table">
<thead>
<tr>
<th>Feature / Claim</th>
<th>Status</th>
<th>Where to verify</th>
<th>Evidence type</th>
</tr>
</thead>
<tbody>
<tr>
<td>Fast Proof-of-Work ordering (10 BPS)</td>
<td>Live</td>
<td><a href="/status">Status</a>, live mainnet, wallets, block explorer</td>
<td>Live activation, transactions, mining history</td>
</tr>
<tr>
<td>UTXO model, self-custody</td>
<td>Live</td>
<td><a href="/status">Status</a>, <a href="https://docs.kaspa.org">docs.kaspa.org</a>, SDKs</td>
<td>Protocol specification, SDK implementation</td>
</tr>
<tr>
<td>Receipt and transfer paths</td>
<td>Live</td>
<td><a href="/status">Status</a>, block explorer, wallet indexers</td>
<td>Live protocol, working wallets, indexer code</td>
</tr>
<tr>
<td>Transaction payload receipts</td>
<td>Live</td>
<td><a href="https://docs.kaspa.org/integrate/transaction-payload">Transaction payload docs</a>, accepted-transaction evidence</td>
<td>Documented payload behavior, txid, accepting block context</td>
</tr>
<tr>
<td>Covenants (after Toccata)</td>
<td>Targeted</td>
<td><a href="/status">Status</a>, <a href="https://github.com/kaspanet/rusty-kaspa">rusty-kaspa</a>, Toccata PR/release timeline</td>
<td>Code in branches, release schedule, KIPs</td>
</tr>
<tr>
<td>Vault rules, escrow, spend limits</td>
<td>Targeted (Toccata)</td>
<td><a href="/builder-guide">Builder Guide</a>, Toccata covenant documentation</td>
<td>Covenant design docs, examples in progress</td>
</tr>
<tr>
<td>Proof verification hooks</td>
<td>Targeted (Toccata)</td>
<td><a href="/status">Status</a>, Toccata specification</td>
<td>Protocol specification, proof design documents</td>
</tr>
<tr>
<td>TN12 covenant proof lab</td>
<td>Testnet only</td>
<td><a href="https://github.com/parker2017code/tn12-covenant-vault-demo">TN12 covenant vault demo</a>, <a href="https://parker2017code.github.io/tn12-covenant-vault-demo/results.html">results explorer</a>, <a href="https://parker2017code.github.io/tn12-covenant-vault-demo/playground.html">playground</a></td>
<td>Accepted TN12 records show testnet money movement, app receipts, replayed balances, blocked actions, and explicit mainnet blockers. Use the linked lab for exact txids, payload counts, and reducer artifacts.</td>
</tr>
<tr>
<td>Inline ZK verification</td>
<td>Targeted</td>
<td><a href="/builder-guide">Builder Guide</a>, <a href="/status">Status</a></td>
<td>Protocol specification, research papers</td>
</tr>
<tr>
<td>Full vProgs (app-specific execution)</td>
<td>Roadmap</td>
<td><a href="/kaspa-vprogs-explained">vProgs Explained</a>, <a href="/status">Status</a>, <a href="https://github.com/kaspanet/vprogs">kaspanet/vprogs</a>, technical talks</td>
<td>Prototype repo, architecture documents, talks</td>
</tr>
<tr>
<td>Scaling beyond Crescendo 10 BPS</td>
<td>Roadmap / research-dependent</td>
<td><a href="/status">Status</a>, research materials, talks</td>
<td>Research documents, protocol vision</td>
</tr>
<tr>
<td>DAGKnight (ordering improvement)</td>
<td>Research</td>
<td><a href="/status">Status</a>, academic papers, protocol research</td>
<td>Research papers, proof-of-concept implementations</td>
</tr>
<tr>
<td>Coordination markets, oracle flows</td>
<td>Research</td>
<td><a href="/application-layer">Application Layer</a>, <a href="/status">Status</a></td>
<td>Design documents, research directions</td>
</tr>
</tbody>
</table>
</div>
</details>
</section>
<section class="section">
<h2>Public builder paths.</h2>
<p>These are the concrete Kaspa capabilities builders can rely on for product decisions:</p>
<div class="reference-grid">
<article>
<h3>Vault and escrow</h3>
<p>After Toccata, covenant rules let you build vaults and escrow that enforce spending limits or unlock conditions without trusting a server.</p>
</article>
<article>
<h3>Receipts and proof of payment</h3>
<p>Fast inclusion and ordered history mean receipts settle quickly and can be verified on-chain. Indexers and APIs let you query proof of a payment.</p>
</article>
<article>
<h3>Assurance contracts</h3>
<p>After Toccata, simple contracts can enforce group commitments: "if N people agree, do X; otherwise, refund everyone."</p>
</article>
<article>
<h3>Coordination markets</h3>
<p><a href="/kaspa-vprogs-explained">Future vProgs</a> and oracle flows support markets where strangers agree on rules before trusting each other, for prediction, funding, or work.</p>
</article>
</div>
</section>
<section class="section">
<h2>How to check a claim.</h2>
<ol style="margin-left: 1.5rem; margin-top: 1rem;">
<li>Find the claim in <a href="/claims-reference">Claims Reference</a> or read its context in <a href="/status">Status</a>.</li>
<li>Check whether it is mainnet, testnet, future upgrade work, research, unsupported, or outside L1 scope.</li>
<li>Follow the source link to primary material: code, releases, KIPs, papers, or core contributor posts.</li>
<li>For builder tooling vs. mainnet status: check <a href="https://github.com/kaspanet/rusty-kaspa">rusty-kaspa releases</a> for code availability and <a href="https://docs.kaspa.org">docs.kaspa.org</a> for official builder guidance.</li>
<li>For roadmap claims: look for architecture documents or research direction, not announcement posts alone.</li>
</ol>
</section>
<section class="section">
<h2>Related pages.</h2>
<div class="reference-grid">
<article>
<h3><a href="/builder-guide">Builder Guide</a></h3>
<p>Programmability choices: covenants, based apps, inline ZK, vProgs, SDKs, and infrastructure evidence.</p>
</article>
<article>
<h3><a href="/application-layer">Application Layer</a></h3>
<p>Status-labeled map of what builders can use now and what Toccata, vProgs, and research support later.</p>
</article>
<article>
<h3><a href="/status">Status</a></h3>
<p>Shipped-vs-roadmap status with implementation evidence for features, activation dates, and common misconceptions.</p>
</article>
<article>
<h3><a href="/sources">Sources & Reference Map</a></h3>
<p>Full source hierarchy and external reference map for protocol sources and builder resources.</p>
</article>
</div>
</section>
<section class="section">
<p style="font-size: 0.9rem; color: var(--text-secondary); line-height: 1.6;">This page does not make Kaspa claims authoritative. It points you to places where claims are sourced. For protocol authority, check code, releases, and primary sources in <a href="/sources">Sources</a>. For builder tooling status, check <a href="https://docs.kaspa.org">docs.kaspa.org</a> and <a href="https://github.com/kaspanet/rusty-kaspa">rusty-kaspa</a>.</p>
</section>
</main>
<footer class="footer">
<div class="footer-grid">
<p><strong>Independent Kaspa-positive research guide.</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>