-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathstart-here.html
More file actions
293 lines (285 loc) · 16.1 KB
/
Copy pathstart-here.html
File metadata and controls
293 lines (285 loc) · 16.1 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
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>Start Here | Kaspa Explained</title>
<meta name="description" content="A beginner-first start page for Kaspa Explained: learn crypto from zero, then understand coins, market value, tradeoffs, and where Kaspa fits.">
<meta name="robots" content="index,follow,max-snippet:-1,max-image-preview:large">
<link rel="canonical" href="https://kaspaexplained.com/start-here">
<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="Start Here | Kaspa Explained">
<meta property="og:description" content="Start from zero: records, keys, transactions, blocks, consensus, tokens, market value, tradeoffs, and Kaspa.">
<meta property="og:type" content="article">
<meta property="og:url" content="https://kaspaexplained.com/start-here">
<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="Start Here | Kaspa Explained">
<meta name="twitter:description" content="Start from zero: records, keys, transactions, blocks, consensus, tokens, market value, tradeoffs, and Kaspa.">
<meta name="twitter:image" content="https://kaspaexplained.com/og-kaspa-explained-20260514.png?v=20260514-logo-clearance">
<meta name="dateModified" content="2026-06-25">
<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="knowledge-page">
<section class="knowledge-hero section app-mechanics-hero">
<div>
<p class="eyebrow">Start here</p>
<h1>Start with the problem</h1>
<p class="lead">Crypto is easier when every mechanism answers one question: what breaks if one trusted operator is removed? This path starts with records, then moves to keys, transactions, blocks, consensus, incentives, markets, coin categories, tradeoffs, and finally Kaspa.</p>
</div>
<div class="network-mechanics-map" aria-label="Kaspa blockDAG mechanics map">
<div class="mechanics-dag" aria-hidden="true">
<i style="--x:10%;--y:60%"></i>
<i style="--x:24%;--y:35%"></i>
<i class="selected" style="--x:38%;--y:52%"></i>
<i style="--x:51%;--y:28%"></i>
<i class="tx" style="--x:64%;--y:46%"></i>
<i style="--x:78%;--y:64%"></i>
<i style="--x:88%;--y:38%"></i>
</div>
<div class="mechanics-readout">
<span>Kaspa mental model</span>
<strong>parallel blocks, one spend history</strong>
<p>Picture mined blocks that can appear in parallel and still be ordered into shared history. A normal slow line is the wrong mental model.</p>
</div>
</div>
</section>
<section class="section" aria-labelledby="kaspa-syllabus">
<p class="eyebrow">Content plan</p>
<h2 id="kaspa-syllabus">What this guide teaches</h2>
<p>Use this as the beginner syllabus. It starts with plain mental models, then separates live mainnet behavior from testnet evidence, roadmap work, and claims Kaspa is not making yet.</p>
<div class="overview-grid">
<article>
<span>One sentence</span>
<p><a href="/what-is-kaspa">Kaspa is a mined Proof-of-Work blockDAG where GHOSTDAG orders parallel blocks into one shared payment history.</a></p>
</article>
<article>
<span>The normal tradeoff</span>
<p><a href="/tradeoff-map">Most chains choose between slower global ordering, more centralization pressure, or more complex execution and network assumptions.</a></p>
</article>
<article>
<span>blockDAG analogy</span>
<p><a href="/ghostdag-explained">Instead of forcing honest blocks into one slow line, Kaspa keeps parallel work visible in a graph, then orders it.</a></p>
</article>
<article>
<span>GHOSTDAG ordering</span>
<p><a href="/ghostdag-explained">GHOSTDAG is the ordering rule that lets nodes agree which parallel blocks belong to the selected history.</a></p>
</article>
<article>
<span>Confirmations</span>
<p><a href="/kaspa-confirmations-finality">Fast inclusion is not instant finality. Confirmations describe growing confidence that a transaction remains in the accepted history.</a></p>
</article>
<article>
<span>BPS</span>
<p><a href="/status">BPS means blocks per second. Crescendo-era 10 BPS is live, while throughput, TPS, and confirmation behavior need careful wording.</a></p>
</article>
<article>
<span>Crescendo, Toccata, KIPs</span>
<p><a href="/toccata-status">Crescendo is the live 10 BPS era. Toccata, KIPs, covenants, and sequencing commitments must stay status-bounded.</a></p>
</article>
<article>
<span>Live versus future</span>
<p><a href="/status">The guide labels mainnet, testnet evidence, targeted hard-fork work, roadmap architecture, and research as different claim types.</a></p>
</article>
<article>
<span>Use cases</span>
<p><a href="/where-kaspa-fits">High-throughput mined ordering can help payment, receipt, wallet, proof, custody, and later rule-based app workflows.</a></p>
</article>
<article>
<span>Not claiming yet</span>
<p><a href="/skeptical-case">Kaspa is not claiming live native DeFi, live DAGKnight, live vProgs, instant finality, or automatic adoption just because the architecture is technically distinct.</a></p>
</article>
</div>
</section>
<section class="path-grid" aria-label="Choose a learning route">
<a href="/kaspa-in-one-screen">
<span>1 · Problem</span>
<strong>What is Kaspa trying to solve?</strong>
<p>Start with the compressed thesis: fast mined ordering without turning into one operator's database.</p>
</a>
<a href="/status">
<span>2 · Live status</span>
<strong>What is live?</strong>
<p>Separate mainnet behavior from testnet proofs, roadmap, research, and app claims outside L1 scope.</p>
</a>
<a href="/skeptical-case">
<span>3 · Risk</span>
<strong>What could go wrong?</strong>
<p>Read the strongest objections: node pressure, security budget, liquidity, mining concentration, tooling fragility, and roadmap execution.</p>
</a>
<a href="/crypto-from-zero">
<span>I know nothing</span>
<strong>Crypto from zero.</strong>
<p>Begin with digital records, keys, transactions, blocks, consensus, tokens, and tradeoffs.</p>
</a>
<a href="/why-are-there-so-many-coins">
<span>I see hundreds of coins</span>
<strong>Why so many coins exist.</strong>
<p>Separate Bitcoin-like money, smart-contract platforms, stablecoins, exchange tokens, privacy coins, memes, DeFi, and infrastructure.</p>
</a>
<a href="/why-crypto-has-value">
<span>I want value explained</span>
<strong>Why crypto has prices.</strong>
<p>Learn token need, market cap, liquidity, security budget, speculation, launch design, and why price is not proof.</p>
</a>
<a href="/tradeoff-map">
<span>I want the constraints</span>
<strong>The tradeoff map.</strong>
<p>See why speed, privacy, decentralization, security, funding, open markets, and node requirements pull against each other.</p>
</a>
<a href="/coin-atlas">
<span>I want examples</span>
<strong>Coin atlas.</strong>
<p>Understand BTC, ETH, SOL, XRP, BNB, stablecoins, LTC, BCH, XMR, DOGE, LINK, and KAS by category.</p>
</a>
<a href="/analyze-any-coin">
<span>I want a checklist</span>
<strong>Analyze any coin.</strong>
<p>Ask whether the token needs to exist, who got supply first, who secures it, what can fail, and who benefits.</p>
</a>
</section>
<section class="section">
<p class="eyebrow">The beginner promise</p>
<h2>What each page is for</h2>
<div class="lane-grid">
<article>
<h3>Problem</h3>
<p>What breaks in a normal digital system? Copying, double-spending, operator control, spam, censorship, privacy leakage, or coordination failure.</p>
</article>
<article>
<h3>Mechanism</h3>
<p>What tool answers the problem? Keys, signatures, transactions, blocks, consensus, mining, staking, fees, tokens, or markets.</p>
</article>
<article>
<h3>Tradeoff</h3>
<p>What cost appears? Hardware, latency, complexity, user responsibility, public data, volatility, centralization pressure, or funding problems.</p>
</article>
<article>
<h3>Kaspa</h3>
<p>Only after the general mechanism is clear, ask where Kaspa fits: PoW, UTXO, blockDAG, GHOSTDAG, fair launch, and the app work still being built.</p>
</article>
</div>
</section>
<section class="section">
<p class="eyebrow">Best route</p>
<h2>Beginner reading order</h2>
<ol class="learning-steps">
<li><strong>Digital ownership is hard.</strong> <span>Digital information copies easily, so a scarce digital asset needs rules for uniqueness and spending.</span></li>
<li><strong>Records need an accepted authority.</strong> <span>A bank, platform, exchange, or public network must decide which updates count.</span></li>
<li><strong>Crypto removes the easy operator.</strong> <span>That creates new problems: keys, validation, ordering, spam, incentives, security, privacy, scaling, and governance.</span></li>
<li><strong>Consensus is the shared-history problem.</strong> <span>Independent computers need one accepted state even when messages arrive in different orders.</span></li>
<li><strong>Tokens are part of the incentive system.</strong> <span>They can track value, pay fees, reward miners or validators, fund security, and attract speculation.</span></li>
<li><strong>Coins differ because problems differ.</strong> <span>Bitcoin, Ethereum, stablecoins, Solana, BNB, XRP, Monero, Dogecoin, Chainlink, and Kaspa are not the same kind of thing.</span></li>
<li><strong>Kaspa is the destination here.</strong> <span>Kaspa is one answer to the question: can a mined shared record feel closer to real time without becoming a normal centralized database?</span></li>
</ol>
</section>
<section class="section">
<p class="eyebrow">Quick corrections</p>
<h2>Common beginner mistakes</h2>
<div class="reference-grid">
<article>
<h3>A coin is not automatically cheap because the unit price is low</h3>
<p>Supply changes the comparison. Market cap, float, liquidity, access, adoption, and demand carry more signal than the price of one unit.</p>
</article>
<article>
<h3>Fast is not the same as final</h3>
<p>Inclusion, confirmation, finality, throughput, and wallet UX are different layers of speed.</p>
</article>
<article>
<h3>Decentralized does not mean no one has influence</h3>
<p>Mining, staking, nodes, developers, exchanges, wallets, foundations, RPC providers, and market makers can each create concentration points.</p>
</article>
<article>
<h3>Crypto is not one market</h3>
<p>Stablecoins, smart-contract platforms, exchange tokens, privacy coins, meme coins, governance tokens, and PoW money assets are different instruments.</p>
</article>
</div>
</section>
<section class="next-step section" aria-label="Suggested next step">
<p class="eyebrow">Next step</p>
<h2>Start the path</h2>
<p>Begin with digital records and why a public network needs cryptography, consensus, incentives, and tradeoffs before Kaspa appears.</p>
<a class="button primary" href="/crypto-from-zero">Open Crypto From Zero</a>
</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="/"><span>Previous</span><strong>What is Kaspa?</strong><p>Kaspa explained in plain English: what KAS is, how the proof-of-work blockDAG and GHOSTDAG work, and what is live now versus roadmap work.</p></a>
<a href="/what-is-kaspa"><span>Next</span><strong>What is Kaspa?</strong><p>What is Kaspa? A plain guide to KAS, Proof of Work, blockDAGs, GHOSTDAG, 10 BPS, and what is live now versus roadmap work.</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>