Receipt wallet mode
Show payment state, accepted evidence, fallback explorer links, and a support-friendly receipt.
Kaspa app sparks
What becomes possible when apps need fewer middlemen?
Start with products where the money rule matters: vaults, escrow, refunds, assets, receipts, safer payouts, and group commitments. Kaspa is interesting when the network can help order and validate the rule instead of leaving everything to a company server.
Timing note: payments and receipts can start today. Toccata expands the rule surface after activation.
Kaspa app ideas that can start now.
Founder proof page
One app page records user action, txid, source, status label, and current blocker.
Exchange withdrawal helper
Help users separate exchange delay from native Kaspa network behavior.
Node and API monitor
Compare public APIs, own node reads, accepted transactions, and stale provider failures.
Ideas that need Toccata.
Vault policies
Spend caps, delayed withdrawal, recovery key, and team treasury controls.
Assurance funding
Funds release when enough participants commit by a deadline, otherwise refunds follow.
Controlled assets
Tickets, memberships, access passes, game objects, or redeemable claims with transfer rules.
Escrow state machines
Release, refund, dispute, timeout, or cancel flows with visible state transitions.
Idea score.
| Score area | What to write | Why it matters |
|---|---|---|
| User | Name the person or team and the repeated action. | Ideas need demand before protocol design. |
| Kaspa reason | Name self-custody, fast mined ordering, public evidence, or spend rules. | This avoids forced blockchain use. |
| Evidence | Link code, txid, app demo, accepted transaction, or source. | Submissions need reviewable proof. |
| Status | Live, testnet, targeted, roadmap, or research. | Public posts should not mix lanes. |