Who is the user?
Name the actor: trader, wallet user, merchant, miner, exchange, issuer, developer, fund, or app operator.
Reality check
Test the pitch before the narrative.
Kaspa has a serious protocol story. Product claims need a different test: who uses it, what they do, where liquidity comes from, what wallet flow exists, and what evidence proves the claim.
Keyword pre-check
Paste a product idea.
This is not a verdict. It only checks whether the pitch mentions the basic product questions that a real review would need to answer.
0/8
Paste a pitch to start.Keyword scan only. It does not validate the pitch.
Next pass
Open the source-aware AI tool for a fuller red-team review. The pitch is passed through this browser session, not placed in the URL.
Prompt updates as you type.
Product reality
The eight questions.
What job do they do?
Send, swap, borrow, hedge, launch, redeem, escrow, stake, report, integrate, or verify. Vague "platform" language is weak.
Where is liquidity?
Source the first market: issuer, LP, market maker, stablecoin, treasury, buyers, or earned revenue. "Community" is not enough.
Who signs what?
Show the wallet flow, transaction shape, custody model, recovery path, and what the user sees when something fails.
What exists today?
Separate live mainnet, ecosystem tooling, testnet proof, targeted upgrade, roadmap, and research.
What evidence proves it?
Use source links, accepted transactions, code, docs, audits, release notes, working app paths, or reproducible commands.
What breaks?
Model abuse, oracle failure, liquidity exits, wallet mistakes, insider allocation, bot traffic, downtime, and legal or custody risk.
What happens on day two?
Real products need repeated behavior after launch: retention, support, integrations, revenue, routes, or measurable usage.
Field studies
Read other chains like product labs.
Solana app surface
Study wallets, swaps, mobile, stablecoins, consumer apps, DeFi, and app distribution. The April 2026 roundup is useful because it shows what Solana itself treats as active ecosystem surface.
Open Solana roundupBuilder pipeline
Colosseum turns hackathons into founder intake, cofounder matching, accelerator selection, and investor-facing demo paths.
Open Colosseum hackathonsDeveloper assumptions
Solana builders often assume wallets, devnet, examples, standards discussions, Stack Exchange answers, and app templates already exist.
Open Solana CookbookStandards and complaints
Forum and Stack Exchange questions reveal what builders find hard. That is often more useful than project marketing.
Open developer forumUse these as comparison sources, not as proof that Kaspa should copy Solana. The point is market literacy: users, liquidity, tooling, scams, and distribution.
Real versus fake
Signals to separate.
| Claim type | Real signal | Weak signal | Kaspa question |
|---|---|---|---|
| Launchpad | Issuance, wallet flow, liquidity path, visible holders, abuse controls. | A token button and a roadmap. | What can launch today, and where does liquidity come from? |
| DeFi | Risk parameters, oracle model, liquidation path, audit trail, liquidity, working transactions. | Using "DeFi" for any token page. | Is this live, testnet, future Toccata work, or only an app idea? |
| AI agent | Agent signs, pays, receives, proves work, or triggers a bounded workflow. | Chatbot copy wrapped around a token. | What action happens on Kaspa, and who can verify it? |
| Wallet | Clear signing, recovery, balances, history, KRC support, error states, and source verification. | Nice screens without transaction handling. | Does a normal user know what they are signing? |
| Institutional use | Custody, compliance, reporting, settlement, liquidity, support, and integration requirements. | One vague partnership post. | Which institution, which requirement, and what evidence? |
Translate back to Kaspa
Useful lessons, not imitation.
| Observed behavior | Why it matters | Kaspa gap | Possible experiment |
|---|---|---|---|
| Low-friction token launches | Creation, liquidity, and attention collapse into one flow. | No mature Kaspa-native launch and liquidity rail. | A restrained KRC-aware issuance tool with wallet safety, source labels, and abuse warnings. |
| Swap aggregation | Users want one route, not fragmented liquidity pages. | No mature DEX layer or routing surface. | Track early swap attempts by quote quality, liquidity source, and signing UX. |
| Hackathon funnel | Deadlines, judges, examples, and funding create repeatable builder intake. | Builder energy is less structured publicly. | Public Kaspa build sprint with source-backed judging criteria and shipped demos. |
| Wallet-first apps | Users judge the chain through signing, balances, errors, history, and support. | Consumer wallet UX is still fragmented across needs. | Map wallet tasks from new user to KRC object to accepted transaction evidence. |
| Exploit response | Real DeFi needs monitoring, audits, incident process, and recovery language. | Kaspa app risk culture is early. | Require every app pitch to publish failure modes before claiming production readiness. |