kaspa-explained/reality-check.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
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
<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width,initial-scale=1">
  <title>Reality Check for Kaspa Product Claims | Kaspa Explained</title>
  <meta name="description" content="A Kaspa product-reality checklist and pitch scanner for testing crypto app claims against users, liquidity, wallet flows, evidence, and source boundaries.">
  <meta name="robots" content="index,follow,max-snippet:-1,max-image-preview:large">
  <link rel="canonical" href="https://kaspaexplained.com/reality-check">
  <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="Reality Check for Kaspa Product Claims | Kaspa Explained">
  <meta property="og:description" content="Test crypto product claims against users, liquidity, wallet flows, evidence, and source boundaries.">
  <meta property="og:type" content="article">
  <meta property="og:url" content="https://kaspaexplained.com/reality-check">
  <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="Reality Check for Kaspa Product Claims | Kaspa Explained">
  <meta name="twitter:description" content="A pitch scanner for Kaspa product claims, source boundaries, and market reality.">
  <meta name="twitter:image" content="https://kaspaexplained.com/og-kaspa-explained-20260514.png?v=20260514-logo-clearance">
  <meta name="dateModified" content="2026-06-23">
  <link rel="stylesheet" href="styles.css?v=20260624-card-hover">
  <script defer src="nav.js?v=20260606-anchor-clearance"></script>
  <script defer src="reality-check.js?v=20260514"></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="reality-page">
    <section class="reality-hero section">
      <p class="eyebrow">Reality check</p>
      <h1>Test the pitch before the narrative.</h1>
      <p class="lead">Kaspa has a serious protocol story. Product claims need a different test: who uses it, what they do, where liquidity comes from, what wallet flow exists, and what evidence proves the claim.</p>
      <p class="fit-note"><strong>Use this for app and product claims.</strong> Use <a href="/kaspa-claims-checker">Claims Checker</a> for protocol status. Use <a href="/builder-evidence">Builder Evidence</a> when a demo or txid is being used to prove a builder claim.</p>
      <div class="actions">
        <a class="button primary" href="#pitch-checker">Test a pitch</a>
        <a class="button" href="#product-reality">Use the checklist</a>
      </div>
    </section>

    <section id="pitch-checker" class="section pitch-checker" data-pitch-checker>
      <p class="eyebrow">Keyword pre-check</p>
      <h2>Paste a product idea.</h2>
      <p class="lead">This is not a verdict. It only checks whether the pitch mentions the basic product questions that a real review would need to answer.</p>
      <div class="pitch-layout">
        <div class="pitch-input-card">
          <label class="ai-field">
            <span>Pitch or claim</span>
            <textarea rows="10" data-pitch-input placeholder="Example: We are building a Kaspa DeFi launchpad with AI agents, instant liquidity, and institutional adoption."></textarea>
          </label>
          <div class="ai-preset-strip" aria-label="Pitch examples">
            <button type="button" data-pitch-sample="launchpad">Launchpad</button>
            <button type="button" data-pitch-sample="agent">AI agent</button>
            <button type="button" data-pitch-sample="wallet">Wallet app</button>
            <button type="button" data-pitch-sample="vault">Vault</button>
          </div>
        </div>
        <div class="pitch-output-card">
          <div class="pitch-score">
            <span data-pitch-score>0/8</span>
            <strong><span data-pitch-verdict>Paste a pitch to start.</span><small>Keyword scan only. It does not validate the pitch.</small></strong>
          </div>
          <div class="pitch-check-grid" data-pitch-results aria-live="polite"></div>
          <div class="pitch-ai-card">
            <strong>Next pass</strong>
            <p>Copy the review prompt, then compare the pitch against Status, Claims, and Sources before posting.</p>
            <div class="pitch-ai-actions">
              <button type="button" data-pitch-copy>Copy review prompt</button>
            </div>
            <p class="ai-copy-status" data-pitch-copy-status aria-live="polite">Prompt updates as you type.</p>
          </div>
        </div>
      </div>
    </section>

    <section id="product-reality" class="section">
      <p class="eyebrow">Product reality</p>
      <h2>The eight questions.</h2>
      <div class="reality-grid">
        <article><span>01</span><h3>Who is the user?</h3><p>Name the actor: trader, wallet user, merchant, miner, exchange, issuer, developer, fund, or app operator.</p></article>
        <article><span>02</span><h3>What job do they do?</h3><p>Send, swap, borrow, hedge, launch, redeem, escrow, stake, report, integrate, or verify. Vague "platform" language is weak.</p></article>
        <article><span>03</span><h3>Where is liquidity?</h3><p>Source the first market: issuer, LP, market maker, stablecoin, treasury, buyers, or earned revenue. "Community" is not enough.</p></article>
        <article><span>04</span><h3>Who signs what?</h3><p>Show the wallet flow, transaction shape, custody model, recovery path, and what the user sees when something fails.</p></article>
        <article><span>05</span><h3>What exists today?</h3><p>Separate live mainnet, app tooling, testnet proof, targeted upgrade, roadmap, and research.</p></article>
        <article><span>06</span><h3>What evidence proves it?</h3><p>Use source links, accepted transactions, code, docs, audits, release notes, working app paths, or reproducible commands.</p></article>
        <article><span>07</span><h3>What breaks?</h3><p>Model abuse, oracle failure, liquidity exits, wallet mistakes, insider allocation, bot traffic, downtime, and legal or custody risk.</p></article>
        <article><span>08</span><h3>What happens on day two?</h3><p>Real products need repeated behavior after launch: retention, support, integrations, revenue, routes, or measurable usage.</p></article>
      </div>
    </section>

    <section class="section">
      <p class="eyebrow">Real versus fake</p>
      <h2>Signals to separate.</h2>
      <div class="table-wrap">
        <table class="reality-table">
          <thead>
            <tr><th>Claim type</th><th>Real signal</th><th>Weak signal</th><th>Kaspa question</th></tr>
          </thead>
          <tbody>
            <tr><td>Launchpad</td><td>Issuance, wallet flow, liquidity path, visible holders, abuse controls.</td><td>A token button and a roadmap.</td><td>What can launch today, and where does liquidity come from?</td></tr>
            <tr><td>DeFi</td><td>Risk parameters, oracle model, liquidation path, audit trail, liquidity, working transactions.</td><td>Using "DeFi" for any token page.</td><td>Is this live mainnet, TN10/TN12 testnet evidence, future Toccata work, or only an app idea?</td></tr>
            <tr><td>AI agent</td><td>Agent signs, pays, receives, proves work, or triggers a bounded workflow.</td><td>Chatbot copy wrapped around a token.</td><td>What action happens on Kaspa, and who can verify it?</td></tr>
            <tr><td>Wallet</td><td>Clear signing, recovery, balances, history, error states, and source verification.</td><td>Nice screens without transaction handling.</td><td>Does a normal user know what they are signing?</td></tr>
            <tr><td>Institutional use</td><td>Custody, compliance, reporting, settlement, liquidity, support, and integration requirements.</td><td>One vague partnership post.</td><td>Which institution, which requirement, and what evidence?</td></tr>
          </tbody>
        </table>
      </div>
    </section>

    <section class="section">
      <p class="eyebrow">Translate back to Kaspa</p>
      <h2>Useful lessons, not imitation.</h2>
      <div class="table-wrap">
        <table class="reality-table">
          <thead>
            <tr><th>Observed behavior</th><th>Why it matters</th><th>Kaspa gap</th><th>Possible experiment</th></tr>
          </thead>
          <tbody>
            <tr><td>Low-friction asset launches</td><td>Creation, liquidity, and attention collapse into one flow.</td><td>No mature Kaspa-native launch and liquidity rail.</td><td>A restrained post-Toccata asset tool with wallet safety, source labels, and abuse warnings.</td></tr>
            <tr><td>Swap aggregation</td><td>Users want one route, not fragmented liquidity pages.</td><td>No mature DEX layer or routing surface.</td><td>Track early swap attempts by quote quality, liquidity source, and signing UX.</td></tr>
            <tr><td>Hackathon funnel</td><td>Deadlines, judges, examples, and funding create repeatable builder intake.</td><td>Builder energy is less structured publicly.</td><td>Public Kaspa build sprint with source-backed judging criteria and shipped demos.</td></tr>
            <tr><td>Wallet-first apps</td><td>Users judge the chain through signing, balances, errors, history, and support.</td><td>Consumer wallet UX is still fragmented across needs.</td><td>Map wallet tasks from new user action to accepted transaction evidence.</td></tr>
            <tr><td>Exploit response</td><td>Real DeFi needs monitoring, audits, incident process, and recovery language.</td><td>Kaspa app risk culture is early.</td><td>Require every app pitch to publish failure modes before claiming production readiness.</td></tr>
          </tbody>
        </table>
      </div>
    </section>

    <section class="next-step section">
      <h2>Use it with the source tools.</h2>
      <p>Copy the review prompt, then check the live status page before repeating the claim.</p>
      <a class="button primary" href="#pitch-checker">Test a pitch</a>
      <a class="button" href="/status">Check status</a>
      <a class="button" href="/sources">Open sources</a>
    </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>