Receipt wallet mode
Payment state, accepted evidence, fallback explorer links, and a support-friendly receipt, all on one screen.
What to build
App ideas where the money rule changes the product
The ideas worth building rest on a rule the user can read before their money moves: a vault that cannot be drained at once, an escrow that refunds itself when the deadline passes. Kaspa earns its place only when network ordering or validation changes what the user has to trust.
Status: payments and receipts can start today. Toccata widened what a mainnet spend rule can enforce; product claims still need receipts, tooling, wallets, and users.
Reality check: run product demand, liquidity, wallet flow, and failure modes through Reality Check before treating an app idea as a product claim.
Kaspa app ideas that can start now
Founder proof page
One page: user action, txid, source, status label, current blocker. Nothing gets held back for a deck.
Exchange withdrawal helper
Separates exchange processing delay from Kaspa network behavior, which most support tickets conflate.
Node and API monitor
Diffs public APIs against your own node's reads and flags stale-provider failures before users notice.
Toccata-era ideas
Vault policies
Spend caps, delayed withdrawal, recovery key, and team treasury controls enforced by the spend script itself.
Assurance funding
Funds release only once enough participants commit by a deadline; miss the deadline and refunds trigger automatically.
Controlled assets
Tickets, memberships, access passes, game objects, or redeemable claims, each carrying its own transfer rule.
Escrow state machines
Release, refund, dispute, timeout, or cancel: every transition stays visible on-chain.
Idea score
| Score area | What to write | Consequence |
|---|---|---|
| User | Name the person or team and the action they repeat often enough to care about. | Demand comes before protocol design. |
| Kaspa reason | Name self-custody, fast mined ordering, public evidence, or spend rules: the actual, specific reason. | This is what keeps blockchain use from being forced onto a product that didn't need it. |
| Evidence | Link code, txid, app demo, accepted transaction, or source. | A submission without reviewable proof doesn't get reviewed. |
| Status | Live, testnet, targeted, roadmap, or research: one label. | Mixing lanes in a public post is how a testnet demo becomes a mainnet rumor. |