-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathclaims-reference.html
More file actions
171 lines (166 loc) · 11.7 KB
/
Copy pathclaims-reference.html
File metadata and controls
171 lines (166 loc) · 11.7 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
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>Kaspa Claims Reference | Kaspa Explained</title>
<meta name="description" content="Human-readable guide to the Kaspa Explained claims file: live claims, testnet evidence, targeted upgrades, roadmap items, research, and forbidden overclaims.">
<meta name="robots" content="index,follow,max-snippet:-1,max-image-preview:large">
<link rel="canonical" href="https://kaspaexplained.com/claims-reference">
<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 Claims Reference | Kaspa Explained">
<meta property="og:description" content="Browser-friendly guide to the claims file and its status labels.">
<meta property="og:type" content="article">
<meta property="og:url" content="https://kaspaexplained.com/claims-reference">
<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 Claims Reference | Kaspa Explained">
<meta name="twitter:description" content="Browser-friendly guide to the claims file and its status labels.">
<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 Claims Reference",
"url": "https://kaspaexplained.com/claims-reference",
"dateModified": "2026-06-28",
"description": "Human-readable guide to the Kaspa Explained claims file.",
"about": ["Kaspa", "Claims", "Sources", "Status", "Toccata", "GHOSTDAG"]
}
</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="sources-page">
<section class="sources-hero section">
<p class="eyebrow">Claims reference</p>
<h1>Claims need a status label</h1>
<p class="lead">Use this page when a claim needs a clear label: live mainnet, testnet evidence, targeted upgrade, roadmap, research, unsupported, or out of scope.</p>
<p class="fit-note"><strong>Last checked:</strong> June 28, 2026.</p>
<div class="actions">
<a class="button primary" href="/kaspa-claims-checker">Use claims checker</a>
<a class="button" href="/status">Open current status</a>
<a class="button" href="/sources">Open sources</a>
</div>
</section>
<section class="section">
<p class="eyebrow">How to use it</p>
<h2>Start with the claim, then ask what evidence it has</h2>
<div class="summary-grid">
<article><span>Live</span><p>Use for behavior available on Kaspa mainnet now: Proof of Work, UTXO ownership, GHOSTDAG ordering, Crescendo-era 10 BPS, wallets, nodes, and explorers.</p></article>
<article><span>Out of L1 scope</span><p>App and project catalog context stays outside this site's status labels unless the claim is specifically about L1 transaction data, accepted transactions, or miner fees.</p></article>
<article><span>Testnet-only</span><p>Use for TN10/TN12 activation or covenant proof work, accepted testnet transactions, rejected mutation cases, and developer-flow evidence. It does not prove mainnet activation.</p></article>
<article><span>Targeted</span><p>Use for Toccata and related near-term work when release and activation parameters exist but activation or observable post-activation behavior is still pending.</p></article>
<article><span>Roadmap</span><p>Use for <a href="/kaspa-vprogs-explained">vProgs</a>, full cross-app composition, and richer app architecture that still needs shipped software and users.</p></article>
<article><span>Research</span><p>Use for DAGKnight, 100 BPS research, partition-resilient payments, RTD-derived oracle/attestation flows, TangVM, and coordination-market systems.</p></article>
</div>
</section>
<section class="section">
<p class="eyebrow">Copy rules</p>
<h2>Status comes first</h2>
<div class="table-wrap">
<table class="reality-table">
<thead><tr><th>Topic</th><th>Safe wording</th><th>Avoid</th></tr></thead>
<tbody>
<tr><td>Finality</td><td>Fast mined inclusion and probabilistic confirmation confidence.</td><td>Instant finality or immediate irreversibility.</td></tr>
<tr><td>Polychain</td><td>Polychain belongs in the VC-funded DAGLabs prehistory. Premine and pre-sale allocation claims need separate token-allocation evidence.</td><td>Ignoring Polychain context or treating it as proof of a premine.</td></tr>
<tr><td>Fair launch</td><td>No premine, insider allocation, or pre-sales; every coin came from mining, including the post-launch DAGLabs/Polychain-related early mining estimate.</td><td>DAGLabs/Polychain premine language, flawless distribution, or no early contributor mining.</td></tr>
<tr><td>Original codebase</td><td>Original Kaspad was Golang and source-backed as an adaptation of <code>btcd</code>.</td><td>A specific Bitcoin Core version without a durable source.</td></tr>
<tr><td>App and project tooling</td><td>Out of scope unless the claim is specifically about L1 transaction data, accepted transactions, or miner fees.</td><td>App activity proves mainnet activation or native smart contracts.</td></tr>
<tr><td>TN10</td><td>Testnet-10 Toccata activation and hardening evidence, including tn10-toc2 and tn10-toc3.</td><td>TN10 test activation is mainnet activation.</td></tr>
<tr><td>TN12</td><td>Testnet evidence for covenant developer flows and opcode testing.</td><td>TN12 txids or rejections prove mainnet covenant enforcement.</td></tr>
<tr><td>Toccata</td><td>Rusty Kaspa v2.0.1 is the current Toccata release. Rusty Kaspa v2.0.0 schedules activation at DAA score 474,165,565. KIP/TN10 evidence is testnet/design evidence until mainnet reaches the activation score and post-activation behavior is observable.</td><td>Mainnet Toccata has activated just because the release exists.</td></tr>
<tr><td>Emission</td><td>Monthly step-down schedule; May 2026 is 27.5 KAS/sec, June 7 is 25.9565436 KAS/sec, and July 7 is 24.49971475 KAS/sec.</td><td>July 2026 is a one-day emission cliff.</td></tr>
<tr><td>vProgs</td><td><a href="/kaspa-vprogs-explained">Later app architecture</a> for apps that prove richer logic while sharing Kaspa ordering.</td><td>Mainnet app infrastructure has already shipped.</td></tr>
<tr><td>Argent</td><td>Experimental actor-style frontend for Silverscript covenant contracts.</td><td>Argent proves production smart contracts, audits, a stable ABI, or mainnet activation.</td></tr>
<tr><td>DAGKnight</td><td>Research and future consensus direction.</td><td>DAGKnight is current mainnet behavior.</td></tr>
<tr><td>ZK hooks</td><td>ZK can prove computation over chosen inputs; external facts still need anchors.</td><td>A proof alone proves prices, other chains, reserves, or real-world events.</td></tr>
</tbody>
</table>
</div>
</section>
<section class="section">
<p class="eyebrow">Editor rule</p>
<h2>One sentence test catches most mistakes</h2>
<blockquote>If a sentence adds no actor, action, evidence, status label, constraint, consequence, distinction, or reader judgment, delete it.</blockquote>
<p>Keep public wording tied to Status, Claims, and Sources. Use one status label, then write the point directly.</p>
</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="/kaspa-claims-checker"><span>Previous</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="/toccata-status"><span>Next</span><strong>Kaspa Toccata status</strong><p>Kaspa Toccata status page: v2.0.1 maintenance release, v2.0.0 activation target, TN10/TN12 testnet evidence, and claim boundaries.</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>