Researching a crypto project means identifying the exact product, network, people, permissions, and evidence behind its claims. Start with a question and a source list instead of a price chart. The crypto hub gives the vocabulary; this checklist turns it into a repeatable investigation.
1. Define the claim
Write down whether you are checking a token identity, a product feature, a reward, a launch promise, or a payment use case. A vague question creates a vague result. Separate what the project says from what the chain, documentation, or independent source can verify.
2. Verify the identifiers
Record the network, exact mint or contract, token program, decimals, official domain, and canonical social links. Compare the identifier with primary documentation and an explorer. A similar name or ticker is not sufficient because unrelated assets can share both.
3. Read permissions and economics
Check supply, mint and freeze authorities, upgrade controls, allocation wallets, unlocks, liquidity venues, and custody assumptions. Market capitalization, FDV, and liquidity answer different questions. Use market cap versus liquidity when a dashboard combines them.
4. Record uncertainty
Save the source URL, timestamp, query window, provider, and missing fields. On-chain analytics can show observable activity but cannot prove identity, intent, or complete history. A useful research note says what would change its conclusion.
A practical output
Finish with a one-page evidence table: claim, source, observation, confidence, and next check. For public-address questions, use how to check a Solana wallet and never request a private key or seed phrase.
Limits and responsible use
This process cannot prove safety, legality, future demand, or investment performance. Provider gaps, mislabeled wallets, changing documentation, and off-chain agreements remain possible. Last reviewed 2026-09-21.