AI-agent escrow
Agent posts task, worker submits proof, wallet releases or refunds through a visible rule.
Kaspa builder funnel
Kaspa hackathon ideas.
Kaspa hackathon ideas should produce a working artifact, a source list, and a status label. The goal is builder learning and useful evidence, not a generic token demo.
Timing note: payments are live today. New app-layer rules need Toccata activation and supporting wallets or tools.
Kaspa hackathon ideas challenge tracks.
Receipt wallet
Generate a receipt page with txid, accepted state, source, amount, and fallback verification.
Founder fit scanner
Turn a product pitch into user, job, evidence, status, risk, and next action.
Vault policy UX
Show a spend cap, delay, recovery path, and rejected spend in a user-readable flow.
Node/API comparison
Compare hosted API, public node, explorer, and local node status for one transaction.
Assurance bounty
Commit funds to a project only after enough participants join under a deadline.
Judging rubric.
| Score area | What judges check | Evidence |
|---|---|---|
| User need | The demo solves one repeated action. | User story and workflow |
| Kaspa fit | Fast PoW ordering, self-custody, receipts, UTXO rules, or proof checks matter. | Written fit statement |
| Working path | The demo runs or the artifact can be inspected. | Code, page, txid, or replay |
| Status honesty | Live, testnet, targeted, roadmap, and research claims stay separate. | Status section |
| Next step | The team knows the first blocker after the hackathon. | Issue list or build note |
Post-event output.
Every team should leave with a working artifact, a source list, a status label, and a next action.