Checklist
Analyze any coin by asking who needs it and who benefits.
Do not start with the chart. Start with token necessity, supply, launch design, security, validation, liquidity, market structure, risks, and the strongest criticism.
The 20 questions
Use this before taking any coin seriously.
What problem does it solve?
Why does the token need to exist?
Could BTC, ETH, USDC, or a database do the job?
Who pays fees?
Who secures it?
Who validates it?
Who can change the rules?
How did it launch?
Who got early supply?
Are there unlocks?
What gives durable demand?
What gives security budget?
What are node requirements?
What is centralized?
What is private or public?
What would make the token unnecessary?
What can fail?
What would justify market cap?
What is the strongest criticism?
Who benefits if retail buys?
Token necessity
Classify the token before the narrative.
| Classification | What it means | Common examples |
| Necessary native asset | The chain needs it for fees, rewards, security, or the asset being tracked. | BTC, ETH, KAS, SOL in their own network contexts. |
| Useful but not strictly necessary | The token helps coordinate incentives or access, but another asset could possibly do the job. | Some app, infrastructure, and ecosystem tokens. |
| Governance-only token | Value depends on whether governance controls meaningful fees, parameters, or treasury assets. | Many DeFi protocol tokens. |
| Claim or wrapper | The asset represents something else and depends on redemption, custody, bridge, or contract trust. | Wrapped BTC, liquid staking tokens, tokenized gold or stocks. |
| Attention token | The main asset is culture, attention, and liquidity. | Meme coins. |
| Likely unnecessary | The same product could work with an existing asset or normal database. | Many weak utility tokens. |
Green and red flags
Fast risk scan.
Green flags
- Clear token purpose.
- Transparent supply and launch history.
- Active developers and public documentation.
- Independent validation is realistic.
- Deep liquidity and no obvious unlock cliff.
- Real users or a credible path to users.
- Honest discussion of tradeoffs.
Red flags
- Guaranteed yield or no-risk language.
- Huge insider allocation with thin float.
- Fake partnerships or unverifiable claims.
- No reason the token must exist.
- Opaque reserves, custody, bridges, or admin keys.
- Influencer-heavy marketing before working product.
- Buzzword stacking without mechanism.
Market table
How to read a coin-ranking page.
| Field | What it means | What can mislead |
| Price | Price of one unit. | A low unit price is not cheap without supply context. |
| Market cap | Price times circulating supply. | Not revenue, not cash invested, not sellable value. |
| Volume | Amount traded in a period. | Can be real liquidity, panic, hype, or wash trading. |
| Circulating supply | Tokens counted as available. | Insiders may still control large portions. |
| FDV | Price times total possible supply. | Shows dilution risk if many tokens are locked. |
| Social dominance | Attention share. | Attention is not adoption or durability. |
| Category labels | Market-site tags. | Often too broad, stale, promotional, or technically shallow. |
Kaspa lens
Apply the same checklist to Kaspa.
Kaspa has a clearer token-necessity argument than many app tokens because KAS is the native asset of a PoW UTXO blockDAG network: it is the thing tracked, the fee asset, and the mining reward. Its fair launch reduces official insider-allocation risk. But the checklist still asks hard questions about liquidity, security budget, mining concentration, node requirements, adoption, funding, app-layer execution, and roadmap status.
Next step
Go back to categories or forward to Kaspa.
Use the coin atlas if the market table still feels like one undifferentiated list. Use the status page before making any Kaspa shipped-feature claim.