What kinds of projects are a good fit for Kaspa's Inline ZK option?

Inline ZK is well-suited to four use-case categories: privacy-preserving actions, proof-verified workflows, custom account models, and applications that want to minimize on-chain computation while letting Kaspa verify the results. The common thread is that each action produces a cryptographic proof locally on the user's device or server, and only that proof is submitted to Kaspa — the full computation never hits the chain. This matters for developers building privacy tools or complex custom logic, because it keeps sensitive data off-chain while still giving Kaspa's network the evidence it needs to confirm the action is valid.