-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathtradeoff-map.html
More file actions
211 lines (202 loc) · 12.8 KB
/
tradeoff-map.html
File metadata and controls
211 lines (202 loc) · 12.8 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
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width,initial-scale=1">
<title>Crypto Tradeoff Map | Kaspa Explained</title>
<meta name="description" content="A beginner crypto tradeoff map: speed, security, decentralization, privacy, scaling, nodes, ASICs, staking, token launches, fees, markets, and Kaspa.">
<meta name="robots" content="index,follow,max-snippet:-1,max-image-preview:large">
<link rel="canonical" href="https://kaspaexplained.com/tradeoff-map">
<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="Crypto Tradeoff Map | Kaspa Explained">
<meta property="og:description" content="Every crypto design moves pressure somewhere: speed, privacy, security, node burden, market risk, funding, or centralization.">
<meta property="og:type" content="article">
<meta property="og:url" content="https://kaspaexplained.com/tradeoff-map">
<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="Crypto Tradeoff Map | Kaspa Explained">
<meta name="twitter:description" content="Every crypto design moves pressure somewhere: speed, privacy, security, node burden, market risk, funding, or centralization.">
<meta name="twitter:image" content="https://kaspaexplained.com/og-kaspa-explained-20260514.png?v=20260514-logo-clearance">
<meta name="dateModified" content="2026-05-16">
<link rel="stylesheet" href="styles.css?v=20260606-anchor-clearance">
<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="/start-here">Start</a>
<a href="/what-is-kaspa">Kaspa 101</a>
<a href="/status">Status</a>
<a href="/kaspa-claims-checker">Claims</a>
<a href="/toccata-status">Toccata</a>
<a href="/build-on-kaspa">Build</a>
<a href="/kaspa-app-ideas">Ideas</a>
<a href="/search">Search</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">Tradeoff map</p>
<h1>Crypto design has tradeoffs.</h1>
<p class="lead">Every answer moves cost somewhere: hardware, bandwidth, latency, privacy, regulation, market volatility, funding, governance, or centralization pressure. This page is the beginner map of those constraints.</p>
<div class="concept-diagram tradeoff-diagram" role="img" aria-label="Crypto designs balance speed, security, decentralization, privacy, and usability">
<div class="pressure-map" aria-hidden="true">
<div class="pressure-node speed"><strong>Speed</strong><span>feedback</span></div>
<div class="pressure-node security"><strong>Security</strong><span>cost</span></div>
<div class="pressure-node decentralization"><strong>Many verifiers</strong><span>decentralization</span></div>
<div class="pressure-node privacy"><strong>Privacy</strong><span>hidden data</span></div>
<div class="pressure-node usability"><strong>Usability</strong><span>recovery</span></div>
<p>A design can improve one corner, but the pressure moves somewhere else.</p>
</div>
<p><strong>Tradeoff intuition:</strong> the hard question is not whether a feature is good. It is where the cost moves when the feature is added.</p>
</div>
</section>
<section class="section">
<p class="eyebrow">Master map</p>
<h2>What people want and what it costs.</h2>
<div class="table-wrap">
<table class="reality-table">
<thead><tr><th>Goal</th><th>Why people want it</th><th>What it costs</th></tr></thead>
<tbody>
<tr><td>Decentralization</td><td>No easy single control point.</td><td>Harder upgrades, worse UX, slower coordination, more user responsibility.</td></tr>
<tr><td>Security</td><td>Hard-to-fake history and valid supply.</td><td>Fees, energy, staked capital, complexity, and security-budget pressure.</td></tr>
<tr><td>Speed</td><td>Fast inclusion and better user feedback.</td><td>Propagation pressure, node requirements, weaker verification, or centralization risk.</td></tr>
<tr><td>Privacy</td><td>Less surveillance and better fungibility.</td><td>More cryptography, heavier data, harder auditability, lower exchange access.</td></tr>
<tr><td>Self-custody</td><td>Direct control without a platform account.</td><td>No simple password reset, chargeback, or customer-service recovery.</td></tr>
<tr><td>Open access</td><td>Anyone can join, transact, build, mine, validate, or exit.</td><td>Spam, scams, hostile actors, bots, and manipulation.</td></tr>
<tr><td>Fair launch</td><td>Lower official insider-allocation risk.</td><td>Harder funding, slower business development, early-miner advantage.</td></tr>
<tr><td>Funded launch</td><td>More money for development, audits, grants, legal work, and integrations.</td><td>Insider allocation, unlocks, sell pressure, and governance capture.</td></tr>
</tbody>
</table>
</div>
</section>
<section class="section">
<p class="eyebrow">Visa question</p>
<h2>Why crypto differs from Visa.</h2>
<p>Visa-like systems use trusted institutions, legal agreements, centralized infrastructure, account controls, fraud teams, and permissioned settlement relationships. A public blockchain asks many independent participants to verify the same rules without trusting one operator. That replicated verification is the bottleneck.</p>
<div class="fit-grid">
<article class="section">
<h3>Normal app or payment network</h3>
<p>Runs on controlled infrastructure. The operator can optimize speed, reverse errors, block users, and change rules internally.</p>
</article>
<article class="section">
<h3>Public crypto base layer</h3>
<p>Lets independent nodes reject invalid history. The cost is that data, execution, and ordering must remain verifiable by people outside one company.</p>
</article>
</div>
<p class="fit-note"><strong>Beginner line:</strong> crypto can become Visa-like at the app or custody layer, but a decentralized base layer cannot simply be Visa without inheriting Visa-like trust assumptions.</p>
</section>
<section class="section">
<p class="eyebrow">Scaling</p>
<h2>Bigger or faster has costs.</h2>
<div class="table-wrap">
<table class="reality-table">
<thead><tr><th>Scaling method</th><th>What it improves</th><th>What it risks</th></tr></thead>
<tbody>
<tr><td>Bigger blocks</td><td>More transactions per block.</td><td>Heavier bandwidth, storage, and node requirements.</td></tr>
<tr><td>Faster blocks</td><td>Faster inclusion and better UX.</td><td>More propagation conflict and consensus complexity.</td></tr>
<tr><td>Parallel execution</td><td>More app throughput.</td><td>More complex state management and developer assumptions.</td></tr>
<tr><td>Rollups</td><td>More execution away from L1.</td><td>Sequencer, bridge, proof, and data-availability complexity.</td></tr>
<tr><td>Payment channels</td><td>Fast cheap repeated payments.</td><td>Liquidity management and routing complexity.</td></tr>
<tr><td>Centralized custody</td><td>Best speed and recovery UX.</td><td>Trust the operator again.</td></tr>
</tbody>
</table>
</div>
</section>
<section class="section">
<p class="eyebrow">Privacy</p>
<h2>Privacy and public verification conflict.</h2>
<p>Public chains expose data because independent participants need enough information to verify rules. Privacy tools hide sender, receiver, amount, graph structure, or app state, but that moves cost into cryptography, data size, verification burden, liquidity, and regulation.</p>
<div class="reference-grid">
<article><h3>Transparent ledgers</h3><p>Easier to audit supply and verify rules. Worse for user privacy and business confidentiality.</p></article>
<article><h3>Privacy-first systems</h3><p>Better fungibility and less surveillance. Harder exchange access, heavier data, and more regulatory pressure.</p></article>
<article><h3>Shielding has limits</h3><p>It can be valuable. Scaling, compliance, UX, and verification cost still remain.</p></article>
</div>
</section>
<section class="section">
<p class="eyebrow">Hardware</p>
<h2>ASICs and staking are different concentration pressures.</h2>
<div class="fit-grid">
<article class="section">
<h3>ASIC mining</h3>
<p>Specialized machines can secure PoW efficiently, but mining can concentrate around capital, cheap energy, manufacturers, firmware, and pools.</p>
</article>
<article class="section">
<h3>Staking</h3>
<p>PoS avoids industrial mining hardware, but concentration can move into large holders, staking providers, exchanges, liquid staking, and governance.</p>
</article>
</div>
</section>
<section class="section">
<p class="eyebrow">Kaspa relevance</p>
<h2>Kaspa's tradeoff is fast PoW.</h2>
<p>Kaspa should be explained as a specific tradeoff: keep PoW and UTXO instincts while using a blockDAG and GHOSTDAG to include parallel honest blocks and improve confirmation feel. That does not remove node economics, mining economics, app-layer challenges, privacy tradeoffs, market volatility, or roadmap execution risk.</p>
</section>
<section class="next-step section" aria-label="Suggested next step">
<p class="eyebrow">Next step</p>
<h2>Apply the tradeoffs.</h2>
<p>The coin atlas shows how different assets choose different constraints. The Kaspa comparison page shows where fast PoW fits.</p>
<div class="actions">
<a class="button primary" href="/coin-atlas">Open coin atlas</a>
<a class="button" href="/where-kaspa-fits">Compare Kaspa</a>
</div>
</section>
</main>
<footer class="footer">
<div class="footer-grid">
<p><strong>Independent resource.</strong> Kaspa-positive research guide, 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>