kaspa-explained/crypto-history.html at main · parker2017code/kaspa-explained · GitHub

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
<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width,initial-scale=1">
  <title>Crypto History as Problems | Kaspa Explained</title>
  <meta name="description" content="Crypto history explained as a sequence of problems: digital cash, Bitcoin, mining, ASICs, Ethereum, ICOs, scaling wars, DeFi, stablecoins, rollups, and Kaspa.">
  <meta name="robots" content="index,follow,max-snippet:-1,max-image-preview:large">
  <link rel="canonical" href="https://kaspaexplained.com/crypto-history">
  <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 History as Problems | Kaspa Explained">
  <meta property="og:description" content="A problem-first map of crypto history from Bitcoin to stablecoins, DeFi, rollups, and Kaspa.">
  <meta property="og:type" content="article">
  <meta property="og:url" content="https://kaspaexplained.com/crypto-history">
  <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 History as Problems | Kaspa Explained">
  <meta name="twitter:description" content="A problem-first map of crypto history from Bitcoin to stablecoins, DeFi, rollups, and Kaspa.">
  <meta name="twitter:image" content="https://kaspaexplained.com/og-kaspa-explained-20260514.png?v=20260514-logo-clearance">
  <meta name="dateModified" content="2026-05-18">
  <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="knowledge-page">
    <section class="knowledge-hero section">
      <p class="eyebrow">History</p>
      <h1>Crypto history as problem solving.</h1>
      <p class="lead">Learn crypto history as a map of constraints: digital scarcity, double-spending, mining, liquidity, app rules, scaling, privacy, stablecoins, custody failures, rollups, and faster payment designs.</p>
    </section>

    <section class="section">
      <p class="eyebrow">Problem timeline</p>
      <h2>Problems by era.</h2>
      <div class="timeline">
        <article><span>Before Bitcoin</span><h3>Digital cash</h3><p>How can digital value be scarce when digital data copies easily?</p></article>
        <article><span>Bitcoin</span><h3>Double-spending</h3><p>PoW made a shared payment history expensive to rewrite without a financial institution.</p></article>
        <article><span>Early mining</span><h3>Security market</h3><p>Mining moved from hobby CPUs to competitive hardware, pools, and industrial operations.</p></article>
        <article><span>Litecoin and forks</span><h3>Parameter experiments</h3><p>Communities changed block times, mining algorithms, or scaling philosophy.</p></article>
        <article><span>Ethereum</span><h3>Programmability</h3><p>What if the ledger could host applications and shared programmable state?</p></article>
        <article><span>2017</span><h3>ICOs and scaling war</h3><p>Fundraising exploded while Bitcoin communities split over scaling and rule-change philosophy.</p></article>
        <article><span>DeFi and stablecoins</span><h3>On-chain finance</h3><p>Dollar tokens, exchanges, lending, collateral, and automated markets became core usage.</p></article>
        <article><span>Rollups and fast L1s</span><h3>Scale and UX</h3><p>Projects moved execution to L2s, high-performance chains, appchains, and alternative consensus designs.</p></article>
      </div>
    </section>

    <section class="section">
      <p class="eyebrow">Why forks matter</p>
      <h2>Software plus social agreement.</h2>
      <p>In normal software, a company can ship an update. In crypto, users, miners or validators, exchanges, wallets, and businesses must accept the rule set. A fork is what happens when participants no longer converge on the same rules or history.</p>
      <div class="fit-grid">
        <article class="section">
          <h3>Soft-fork style change</h3>
          <p>Usually tightens rules so upgraded participants enforce new restrictions while older software may still see blocks as valid.</p>
        </article>
        <article class="section">
          <h3>Hard-fork style change</h3>
          <p>Changes rules in a way that older software does not accept. This can be planned, contentious, or community-splitting.</p>
        </article>
      </div>
    </section>

    <section class="section">
      <p class="eyebrow">Why Bitcoin dominance matters</p>
      <h2>Bitcoin as the reference point.</h2>
      <p>Bitcoin's value narrative comes from several sources: fixed-supply culture, PoW security, liquidity, exchange support, long survival, conservative upgrades, simple monetary story, and strong social consensus. It also gave up fast L1 retail UX, expressive smart contracts, and easy experimentation.</p>
    </section>

    <section class="section">
      <p class="eyebrow">Why other chains exist</p>
      <h2>Different projects, different pressures.</h2>
      <div class="reference-grid">
        <article><h3>Bitcoin Cash</h3><p>Chose a bigger-block payment philosophy after Bitcoin's scaling conflict.</p></article>
        <article><h3>Ethereum</h3><p>Chose smart contracts and programmable app records.</p></article>
        <article><h3>Solana-style chains</h3><p>Chose high-performance execution and consumer-app speed.</p></article>
        <article><h3>Monero and Zcash</h3><p>Chose stronger privacy tradeoffs than transparent chains.</p></article>
        <article><h3>Stablecoins</h3><p>Chose dollar-denominated value on crypto networks, with issuer or collateral trust.</p></article>
        <article><h3>Kaspa</h3><p>Chose fast Proof-of-Work blockDAG ordering while keeping UTXO and PoW instincts.</p></article>
      </div>
    </section>

    <section class="section">
      <p class="eyebrow">Kaspa origin</p>
      <h2>Kaspa's launch belongs in the history map.</h2>
      <p>Kaspa's fair launch came after research, DAGLabs, an April 2021 testnet, and failed hardware, presale, and business-model paths. The origin page separates the sourced history from the dramatic shorthand.</p>
      <a class="button" href="/kaspa-origin-story">Read Kaspa origin story</a>
    </section>

    <section class="next-step section" aria-label="Suggested next step">
      <p class="eyebrow">Next step</p>
      <h2>Use history to read current coins.</h2>
      <p>After the problem timeline, the coin atlas explains how current major assets fit into these old and new design branches.</p>
      <a class="button primary" href="/coin-atlas">Open coin atlas</a>
    </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>