kaspa-explained/ai-guidance.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
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
<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width,initial-scale=1">
  <title>Ask AI About Kaspa With Sources | Kaspa Explained</title>
  <meta name="description" content="Open ChatGPT, Claude, Perplexity, or Grok with a source-aware Kaspa prompt that uses Kaspa Explained, status pages, claims, and source links.">
  <meta name="robots" content="noindex,nofollow">
  <link rel="canonical" href="https://kaspaexplained.com/ai-guidance">
  <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="Ask AI About Kaspa With Sources | Kaspa Explained">
  <meta property="og:description" content="Generate a source-aware Kaspa prompt, copy it, and open your AI tool of choice.">
  <meta property="og:type" content="article">
  <meta property="og:url" content="https://kaspaexplained.com/ai-guidance">
  <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="Ask AI About Kaspa With Sources | Kaspa Explained">
  <meta name="twitter:description" content="Generate a source-aware Kaspa prompt, copy it, and open your AI tool of choice.">
  <meta name="twitter:image" content="https://kaspaexplained.com/og-kaspa-explained-20260514.png?v=20260514-logo-clearance">
  <meta name="dateModified" content="2026-06-05">
  <link rel="stylesheet" href="styles.css?v=20260606-anchor-clearance">
  <script defer src="nav.js?v=20260606-anchor-clearance"></script>
  <script defer src="ask-ai.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="/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="sources-page">
    <section class="sources-hero section">
      <p class="eyebrow">Ask AI</p>
      <h1>Ask about Kaspa with sources.</h1>
      <p class="lead">Pick a question, include the source pack, then open your AI tool with a prompt that separates live mainnet behavior, testnet evidence, targeted upgrades, roadmap work, and research.</p>
      <div class="actions">
        <a class="button primary" href="#ask-ai-tool">Build prompt</a>
        <a class="button" href="/claims-reference">Open claims reference</a>
        <a class="button" href="/status">Open status</a>
        <a class="button" href="/sources">Open sources</a>
      </div>
    </section>

    <section class="section">
      <p class="eyebrow">Writing standard</p>
      <h2>Make each sentence prove its job.</h2>
      <div class="summary-grid">
        <article><span>Useful sentence test</span><p>Keep sentences that add an actor, action, evidence, status label, constraint, consequence, distinction, or judgment.</p></article>
        <article><span>Claim boundary</span><p>Say whether the claim is live mainnet behavior, testnet evidence, targeted work, roadmap architecture, research, wrong, unsupported, or outside L1 scope.</p></article>
        <article><span>Plain verbs</span><p>Use words such as test, measure, verify, send, sign, reject, ship, delay, and activate before vague status language.</p></article>
      </div>
      <p class="fit-note">Use <a href="/claims-reference">Claims Reference</a> when a sentence needs a public status label.</p>
    </section>

    <section id="ask-ai-tool" class="section ai-ask-panel" data-ai-ask>
      <p class="eyebrow">Prompt builder</p>
      <h2>Open your AI with the right context.</h2>
      <div class="ai-ask-layout">
        <div class="ai-ask-controls">
          <label class="ai-field">
            <span>Question</span>
            <select data-ai-question>
              <option value="short">Give me the short, accurate explanation of Kaspa.</option>
              <option value="blockdag">Explain blockchain versus blockDAG visually and technically.</option>
              <option value="status">Check whether a Kaspa claim is live, targeted, roadmap, or research.</option>
              <option value="builder">Show the builder path for nodes, APIs, wallets, L1 checks, and TN12 work.</option>
              <option value="compare">Compare Kaspa to Bitcoin, Ethereum, Solana, and other fast chains without tribal framing.</option>
              <option value="design">Turn Kaspa into an app, product, or research idea with clear proof requirements.</option>
              <option value="redteam">Red-team a bullish Kaspa claim and tell me what evidence is missing.</option>
              <option value="roadmap">Separate Crescendo, Toccata, vProgs, DAGKnight, emission, and app-layer claims.</option>
              <option value="safety">Explain wallets, mining, nodes, and common safety checks.</option>
              <option value="skeptical">Give me the skeptical case and what evidence would change it.</option>
            </select>
          </label>
          <label class="ai-field">
            <span>Your angle</span>
            <textarea rows="4" data-ai-custom placeholder="Optional: paste a claim, question, txid, page URL, or topic."></textarea>
          </label>
          <fieldset class="ai-source-picker">
            <legend>Source pack</legend>
            <label><input type="checkbox" data-ai-source checked data-label="One-screen summary" value="/kaspa-in-one-screen"> One-screen summary</label>
            <label><input type="checkbox" data-ai-source checked data-label="Current status" value="/status"> Current status</label>
            <label><input type="checkbox" data-ai-source checked data-label="Claims reference" value="/claims-reference"> Claims reference</label>
            <label><input type="checkbox" data-ai-source checked data-label="Sources" value="/sources"> Sources</label>
            <label><input type="checkbox" data-ai-source checked data-label="Reality check" value="/reality-check"> Reality check</label>
            <label><input type="checkbox" data-ai-source data-label="Command line and KDP" value="/command-line"> Command line and KDP</label>
            <label><input type="checkbox" data-ai-source data-label="Builder guide" value="/builder-guide"> Builder guide</label>
            <label><input type="checkbox" data-ai-source data-label="Toccata status" value="/toccata-status"> Toccata status</label>
          </fieldset>
          <div class="ai-preset-strip" aria-label="Prompt shortcuts">
            <button type="button" data-ai-preset="status">Verify claim</button>
            <button type="button" data-ai-preset="builder">Builder path</button>
            <button type="button" data-ai-preset="redteam">Red team</button>
            <button type="button" data-ai-preset="design">Idea lab</button>
          </div>
        </div>
        <div class="ai-prompt-card">
          <div class="ai-prompt-toolbar">
            <span>Generated prompt</span>
            <button type="button" data-ai-copy>Copy</button>
          </div>
          <textarea readonly rows="16" data-ai-prompt aria-label="Generated AI prompt"></textarea>
          <div class="ai-destination-grid" aria-label="Open prompt in an AI tool">
            <a href="https://chatgpt.com/" data-ai-open="chatgpt">ChatGPT</a>
            <a href="https://claude.ai/new" data-ai-open="claude">Claude</a>
            <a href="https://www.perplexity.ai/search/new" data-ai-open="perplexity">Perplexity</a>
            <a href="https://grok.com/" data-ai-open="grok">Grok</a>
          </div>
          <p class="ai-copy-status" data-ai-status aria-live="polite">Prompt is ready. Opening a tool also copies it.</p>
        </div>
      </div>
    </section>

    <section class="section">
      <p class="eyebrow">Main rule</p>
      <h2>Name the evidence class.</h2>
      <div class="reference-grid">
        <article>
          <h3>Mainnet live</h3>
          <p>Use only for behavior available on Kaspa mainnet now. Use current code, releases, activation records, or primary protocol documentation.</p>
        </article>
        <article>
          <h3>Testnet evidence</h3>
          <p>Use for TN12 or other testnet work with accepted transactions, artifacts, and commands. Testnet evidence is useful without being a mainnet product claim.</p>
        </article>
        <article>
          <h3>Targeted or roadmap</h3>
          <p>Use for Toccata, covenant IDs, Silverscript, sequencing commitments, vProgs, or other work before mainnet activation. Say what source supports the target.</p>
        </article>
        <article>
          <h3>Research</h3>
          <p>Use for architecture, product ideas, oracle designs, coordination markets, or future app patterns that do not yet have live or testnet proof.</p>
        </article>
      </div>
    </section>

    <section class="section">
      <p class="eyebrow">Plain language</p>
      <h2>Say the real requirement.</h2>
      <div class="source-tier-grid">
        <article>
          <h3>Do not say "institutional readiness"</h3>
          <p>Say which actor needs what: an exchange needs node stability, wallet integration, liquidity, legal review, and support; a fund needs custody, reporting, audit trails, and risk controls.</p>
        </article>
        <article>
          <h3>Do not say "ecosystem maturity"</h3>
          <p>Say the missing pieces: releases, KIPs, node behavior, wallets, indexers, SDKs, docs, explorers, exchanges, liquidity, custody, or support.</p>
        </article>
        <article>
          <h3>Do not say "DeFi is live"</h3>
          <p>Say whether the claim is native Kaspa L1 DeFi, Igra/Kaskad-style L2 ecosystem activity, TN12 proof work, wallet-policy simulation, indexer state, future covenant work, or outside L1 scope.</p>
        </article>
        <article>
          <h3>Do not say "ZK proves the real world"</h3>
          <p>A ZK proof can prove computation over inputs. It does not prove that a real-world price, event, identity, reserve, or legal claim is true.</p>
        </article>
      </div>
    </section>

    <section class="section">
      <p class="eyebrow">Kaspa framing</p>
      <h2>Start from the job.</h2>
      <p>Kaspa is best explained as a mined shared record that aims to feel closer to real time without becoming one operator's database. From there, explain the job: payments, records, vault rules, assets, commitments, app-state anchors, or proof verification.</p>
      <p>Keep the split clear: Kaspa mainnet is live; Toccata-era programmability is released and scheduled but not activated; TN12 proof labs are testnet evidence; coordination markets, based apps, and advanced covenant systems need their own artifacts before becoming product claims.</p>
    </section>

    <section class="section">
      <p class="eyebrow">Implication discipline</p>
      <h2>Explain why the rule matters.</h2>
      <p>For covenant, payload, replay, or based-app examples, answer five things: what the artifact proves, what it makes possible, why Kaspa's fast UTXO model matters, why crypto is needed instead of a normal server, and what is still not proven.</p>
      <p>Do not start with the artifact taxonomy. Start with what happened, what can be clicked, what was replayed, which rule actually controls funds, and what remains missing.</p>
      <p>Keep the everyday implication close to the technical label. Start with the job: a budget that cannot drain at once, a step-by-step workflow that can recover, or an asset that only moves with its controller. Then add the technical label only when it helps a builder find the source artifact.</p>
    </section>

    <section class="section">
      <p class="eyebrow">SilverScript and app lessons</p>
      <h2>Do not build shallow demos when the target is covenants.</h2>
      <div class="source-tier-grid">
        <article>
          <h3>Covenants are constrained state transitions</h3>
          <p>A serious example should show the input rule, output rule, continuation state, and what spend path is rejected. A P2PK wrapper with one happy-path txid is only a primitive.</p>
        </article>
        <article>
          <h3>Use DECL state when state matters</h3>
          <p>For budgets, assets, or counters, use explicit state, `readInputState`, `validateOutputState`, covenant IDs, and continuation outputs where tooling supports them.</p>
        </article>
        <article>
          <h3>Split complex logic into roles</h3>
          <p>For chess-like or game-like systems, study the step-workflow pattern: a hub routes to smaller worker contracts, workers return state, and timeouts prevent stuck two-transaction flows.</p>
        </article>
        <article>
          <h3>Use controller inputs for authority</h3>
          <p>Do not assume nested contract execution. One covenant can authorize another through a sibling input, covenant ID, template hash, or signature rule.</p>
        </article>
        <article>
          <h3>Prove state before live claims</h3>
          <p>Compile the script, prove local state/output behavior, prove the signature-script path, then submit only through a route that preserves every required transaction field.</p>
        </article>
      </div>
    </section>

    <section class="section">
      <p class="eyebrow">Before publishing</p>
      <h2>Check these files.</h2>
      <div class="link-grid">
        <a href="/status"><span>Status</span><strong>Live, targeted, roadmap, research</strong></a>
        <a href="/sources"><span>Sources</span><strong>Source hierarchy</strong></a>
        <a href="/claims-reference"><span>Claims</span><strong>Status labels and evidence boundaries</strong></a>
        <a href="/sources"><span>Sources</span><strong>Primary references and context links</strong></a>
        <a href="/status"><span>Status</span><strong>Live, testnet, targeted, roadmap, and research</strong></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>