kaspa-explained/kaspa-hackathon-challenges.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
<!doctype html>
<html lang="en">
<head>
  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width,initial-scale=1">
  <title>Kaspa Hackathon Ideas for AI Agents, Wallets, and Receipts | Kaspa Explained</title>
  <meta name="description" content="Kaspa hackathon ideas for AI agents, wallets, payment receipts, accepted transaction evidence, vault policies, founder fit scoring, and post-event review.">
  <meta name="robots" content="index,follow,max-snippet:-1,max-image-preview:large">
  <link rel="canonical" href="https://kaspaexplained.com/kaspa-hackathon-challenges">
  <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="Kaspa Hackathon Ideas for AI Agents, Wallets, and Receipts">
  <meta property="og:description" content="Kaspa hackathon ideas for AI agents, wallets, payment receipts, accepted transaction evidence, vault policies, founder fit scoring, and post-event review.">
  <meta property="og:type" content="article">
  <meta property="og:url" content="https://kaspaexplained.com/kaspa-hackathon-challenges">
  <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="Kaspa Hackathon Ideas for AI Agents, Wallets, and Receipts">
  <meta name="twitter:description" content="Kaspa hackathon ideas for AI agents, wallets, payment receipts, accepted transaction evidence, vault policies, founder fit scoring, and post-event review.">
  <meta name="twitter:image" content="https://kaspaexplained.com/og-kaspa-explained-20260514.png?v=20260514-logo-clearance">
  <meta name="dateModified" content="2026-06-25">
  <script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "TechArticle",
    "headline": "Kaspa Hackathon Ideas for AI Agents, Wallets, and Receipts",
    "url": "https://kaspaexplained.com/kaspa-hackathon-challenges",
    "dateModified": "2026-06-25",
    "description": "Kaspa hackathon ideas for AI agents, wallets, payment receipts, accepted transaction evidence, vault policies, founder fit scoring, and post-event review.",
    "about": ["Kaspa", "Proof of Work", "blockDAG", "GHOSTDAG", "Toccata"]
  }
  </script>
  <script type="application/ld+json">
  {
    "@context": "https://schema.org",
    "@type": "FAQPage",
    "mainEntity": [
      {
        "@type": "Question",
        "name": "What are good Kaspa hackathon ideas?",
        "acceptedAnswer": {"@type": "Answer", "text": "Good Kaspa hackathon ideas include AI-agent escrow, receipt wallets, founder-fit scanners, vault policy UX, node/API comparison tools, and assurance bounties. Each team should leave with a working artifact, source list, and status label."}
      },
      {
        "@type": "Question",
        "name": "How should Kaspa hackathon projects be judged?",
        "acceptedAnswer": {"@type": "Answer", "text": "Judge the user need, Kaspa fit, working artifact, source list, status honesty, and next blocker. Avoid demos that only add a token label without a reason to use Kaspa."}
      }
    ]
  }
  </script>
  <link rel="stylesheet" href="styles.css?v=20260704-visual-refresh-4">
  <script defer src="nav.js?v=20260701-no-global-toccata"></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="status-page app-page">
    <section class="sources-hero section">
      <p class="eyebrow">Builder challenge</p>
      <h1>Kaspa hackathon ideas</h1>
      <p class="lead">A hackathon demo is worthless the moment the room empties unless it leaves evidence behind: a working artifact, a source list, a status label, a result a reviewer can inspect cold.</p>
      <p class="fit-note"><strong>Status:</strong> payments are live today. Toccata app-layer rules need wallet support, tooling support, and app receipts.</p>
    </section>

    <section class="section">
      <h2>Hackathon tracks</h2>
      <div class="reference-grid">
        <article><h3>AI-agent escrow</h3><p>Agent posts a task, worker submits proof, wallet releases or refunds against a rule the reader can inspect, not agent logic hidden in a backend.</p></article>
        <article><h3>Receipt wallet</h3><p>A receipt page with txid, accepted state, source, amount, and a fallback verification path when the primary one fails.</p></article>
        <article><h3>Founder fit scanner</h3><p>Turns a product pitch into six fields: user, job, evidence, status, risk, next action. No pitch survives that unchanged.</p></article>
        <article><h3>Vault policy UX</h3><p>Shows a spend cap, delay, recovery path, and a rejected spend side by side, in language a non-engineer can read.</p></article>
        <article><h3>Node/API comparison</h3><p>Runs one transaction against a hosted API, a public node, an explorer, and a local node, then shows where they disagree.</p></article>
        <article><h3>Assurance bounty</h3><p>Commits funds to a project only after enough participants join by a deadline. Miss it, and the funds never move.</p></article>
      </div>
    </section>

    <section class="section">
      <h2>Judging rubric</h2>
      <div class="table-wrap">
        <table class="reality-table">
          <thead><tr><th>Score area</th><th>What judges check</th><th>Evidence</th></tr></thead>
          <tbody>
            <tr><td>User need</td><td>The demo solves one repeated action, not a hypothetical one.</td><td>User story and workflow</td></tr>
            <tr><td>Kaspa fit</td><td>Fast PoW ordering, self-custody, receipts, UTXO rules, or proof checks actually change the product, not decoration on top of a normal app.</td><td>Written fit statement</td></tr>
            <tr><td>Working path</td><td>The demo runs, or the artifact can be inspected directly. "It would work" doesn't count.</td><td>Code, page, txid, or replay</td></tr>
            <tr><td>Status honesty</td><td>Live, testnet, targeted, roadmap, and research claims stay in separate sentences, never blended into one.</td><td>Status section</td></tr>
            <tr><td>Next step</td><td>The team names the first blocker after the hackathon ends, not "more polish."</td><td>Issue list or build note</td></tr>
          </tbody>
        </table>
      </div>
    </section>

    <section class="section">
      <h2>Post-event output</h2>
      <p>Every team leaves with a working artifact, a source list, a status label, and a next action, or the project didn't ship.</p>
    </section>

    <section class="next-step section">
      <h2>Use the builder path</h2>
      <div class="actions">
        <a class="button primary" href="/builder-guide">Builder guide</a>
        <a class="button" href="/kaspa-app-ideas">App ideas</a>
        <a class="button" href="/builder-evidence">Builder evidence</a>
        <a class="button" href="/reality-check">Reality check</a>
      </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>Kaspa coordination markets</strong><p>Kaspa coordination markets explained: conditional commitments, assurance funding, auctions, event markets, oracle assumptions, and Toccata...</p></a>
        <a href="/kaspa-founder-investor-matching"><span>Next</span><strong>Kaspa builder review queue</strong><p>Kaspa founder and investor review queue for opt-in idea cards, fit scoring, capital interest, technical review, privacy rules, and daily...</p></a>
        <a href="/status"><span>Status</span><strong>Kaspa current status</strong><p>Kaspa status in plain buckets: live, targeted, roadmap, research, and claims that need caveats.</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>