-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathreality-check.html
More file actions
187 lines (182 loc) · 11.9 KB
/
Copy pathreality-check.html
File metadata and controls
187 lines (182 loc) · 11.9 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
<!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="Paste a Kaspa pitch and test it against users, liquidity, wallet flows, and evidence before you repeat the claim.">
<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="#000000">
<meta property="og:title" content="Reality Check for Kaspa Product Claims | Kaspa Explained">
<meta property="og:description" content="Paste a Kaspa pitch and test it against users, liquidity, wallet flows, and evidence before you repeat the claim.">
<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="Paste a Kaspa pitch and test it against users, liquidity, wallet flows, and evidence before you repeat the claim.">
<meta name="twitter:image" content="https://kaspaexplained.com/og-kaspa-explained-20260514.png?v=20260514-logo-clearance">
<meta name="dateModified" content="2026-07-08">
<link rel="stylesheet" href="styles.css?v=20260711-table-wrap-fix">
<script defer src="nav.js?v=20260708-dark-default"></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">A protocol activating on schedule doesn't tell you whether an app built on it works. Product claims need a different test: who uses it, where the liquidity comes from, who signs what, and what evidence backs it up.</p>
<p class="fit-note"><strong>Use this for app and product claims.</strong> For protocol status, use the <a href="/kaspa-claims-checker">claims checker</a>. When a demo or txid is being used to prove a builder claim, use <a href="/builder-evidence">builder evidence</a>.</p>
</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">Paste the pitch and get a quick keyword scan: does it even touch the questions a real review would ask?</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. Validation needs review.</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 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, a liquidity path, visible holders, abuse controls.</td><td>A token button and a roadmap.</td><td>What can launch today, and where does the liquidity actually come from?</td></tr>
<tr><td>DeFi</td><td>Risk parameters, an oracle model, a liquidation path, an audit trail, liquidity, working transactions.</td><td>The word "DeFi" stapled to any token page.</td><td>Is this live mainnet, TN10/TN12 testnet evidence, or just an app idea riding on Toccata's name?</td></tr>
<tr><td>AI agent</td><td>The agent signs, pays, receives, proves work, or triggers a bounded workflow on-chain.</td><td>Chatbot copy wrapped around a token.</td><td>What action actually happens on Kaspa, and who can verify it?</td></tr>
<tr><td>Wallet</td><td>Clear signing, recovery, balances, history, error states, source verification.</td><td>Nice screens with no real transaction handling underneath.</td><td>Does a normal user know what they're signing?</td></tr>
<tr><td>Institutional use</td><td>Custody, compliance, reporting, settlement, liquidity, support, integration requirements.</td><td>One vague partnership post.</td><td>Which institution, which requirement, and what's the evidence?</td></tr>
</tbody>
</table>
</div>
</section>
<section class="section">
<p class="eyebrow">Translate back to Kaspa</p>
<h2>What other chains' product history says</h2>
<div class="table-wrap">
<table class="reality-table">
<thead>
<tr><th>Observed behavior</th><th>Consequence</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 Kaspa-native launch-and-liquidity rail exists yet.</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 across liquidity sources instead of five tabs.</td><td>No native DEX layer or routing surface yet.</td><td>Track early swap attempts by quote quality, liquidity source, and signing UX.</td></tr>
<tr><td>Hackathon intake</td><td>Deadlines, judges, examples, and funding produce repeatable builder submissions.</td><td>Builder activity here is less structured in public.</td><td>A public Kaspa build sprint with source-backed judging criteria and shipped demos.</td></tr>
<tr><td>Wallet-first apps</td><td>Users judge a chain by signing, balances, errors, history, and support rather than by whitepapers.</td><td>Consumer wallet UX is still fragmented across needs.</td><td>Map wallet tasks from first user action to accepted transaction evidence.</td></tr>
<tr><td>Exploit response</td><td>Real DeFi needs monitoring, audits, an incident process, and recovery language before launch.</td><td>Kaspa's app risk culture is still early.</td><td>Require every app pitch to publish its failure modes before claiming production readiness.</td></tr>
</tbody>
</table>
</div>
</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-coordination-markets"><span>Previous</span><strong>Coordination markets</strong><p>How Kaspa coordination markets would work: conditional commitments, assurance funding, auctions, event markets, oracle assumptions, and...</p></a>
<a href="/builder-guide"><span>Next</span><strong>Kaspa builder guide</strong><p>A builder guide for choosing the simplest Kaspa route: money movement, covenant spend rules, based apps, inline ZK, or later app programs.</p></a>
<a href="/status"><span>Status</span><strong>Kaspa current status</strong><p>What is live, targeted, roadmap, and research on Kaspa right now, checked against mainnet, releases, and KIPs.</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>