How to evaluate a crypto project: a practical checklist

You can evaluate a crypto project the way a careful journalist would: find out what problem it solves, check whether people actually use it, and see who is accountable when things go wrong. This checklist walks you through each step and the red flags to watch for.

Before you start

Write down, in one sentence, what the project claims to do. If you cannot, after reading its homepage and documentation, that is already useful information.

Next, gather primary sources: the official website, the documentation or whitepaper, the code repository, and the token's contract address on a block explorer. Bookmark them, so you are not relying on links shared in chats.

1. The problem and the users

Ask who has the problem and why a blockchain helps. Good answers name a specific group, such as traders who want to swap tokens without an intermediary, or developers who need price data inside a smart contract.

Weak answers are vague: "revolutionizing finance," "the future of the internet." Also ask what people used before. If a normal database would do the job better and cheaper, the blockchain may be there for fundraising rather than function.

2. Real usage you can verify

This is the step most people skip, and it matters most. Usage leaves public traces.

• Fees and revenue. People pay fees when they value a service. DefiLlama's fee rankings let you compare what users pay across many protocols and chains.
• Total value locked. For DeFi apps, this shows how much capital users have deposited. It moves with token prices, so read it alongside fees.
• Active addresses and transactions. Block explorers and chain dashboards show these. One person can control many addresses, and bots can inflate counts, so look for steady trends rather than spikes.
• Developer activity. Public code commits and reports such as Electric Capital's developer report show whether people are still building.

Watch for usage that only exists because of rewards. If activity collapses the moment incentives end, the demand was rented rather than real.

3. Team and accountability

Find out who builds and runs the project. Named founders with a public track record are easier to hold accountable. Some respected projects have pseudonymous builders, so anonymity is not proof of fraud, but it shifts more weight onto code, audits and transparent governance.

Check for a legal entity, a foundation or a company, and where it is based. Look at how the team communicates during problems. Clear incident reports and honest updates are good signs; deleted posts and blame are not.

4. What the token actually does

Many products could work fine without their token. Ask whether the token is required to use the network, for example to pay gas fees or to stake and secure it, or whether it mainly offers voting rights or discounts.

A governance token can matter, but only if votes are meaningful and not dominated by a few wallets. If the token has no functional role at all, any value rests on speculation and promises.

5. Tokenomics

Look at the full supply picture, not just the price. Compare market cap with fully diluted valuation, find the emission rate, and read the unlock schedule for team and investor tokens. Check how concentrated holdings are.

Our lesson on market cap and tokenomics covers each of these with a worked example.

6. Security audits and incident history

Search for smart contract audits by recognized security firms, and read the findings, not just the badge. Check whether serious issues were fixed and whether the audited code is the code actually deployed.

• Is there a public bug bounty?
• Has the project, or a bridge it depends on, been hacked? How did the team respond, and were users repaid?
• Who holds admin keys that can upgrade contracts or pause funds, and is that power protected by a multisig or timelock?

7. Decentralization

Decentralization is a spectrum. Look at how many independent validators or miners secure the network, whether anyone can join, who controls upgrades and treasury funds, and whether a single company or issuer can freeze or change things.

Centralized control is not always wrong, and many stablecoins depend on it. What matters is that the project is honest about it and that you understand who you are trusting.

8. Regulation and legal status

In the US, the SEC, CFTC, FinCEN and state regulators all have a say over parts of crypto. Search for enforcement actions or lawsuits involving the project or its founders, and note any countries where the product is blocked.

The SEC's investor alert on crypto assets is a useful reminder that offerings may not be registered and may lack the disclosures you would get with a stock. For current rules, see our laws and regulations hub.

9. Community versus hype

A healthy community argues about technical choices, files bug reports and builds tools. A hype community talks mostly about price and attacks anyone who asks questions.

Notice who is promoting the project. Paid influencers must disclose sponsorships, but many do not. Countdown timers, "last chance" language and price targets are marketing, not research.

A simple research worksheet

Copy this table into a note and fill it in for each project. Leave a cell blank if you cannot find a reliable answer; blanks are findings too.

How to weigh the answers

No project scores perfectly. A young network will have a short track record; a payment stablecoin will be centralized by design. What matters is whether the weaknesses are disclosed and whether they fit what the project claims to be.

Give the most weight to things that are hard to fake: fees paid by real users, code that has run for years without major losses, and supply rules enforced by smart contracts. Give the least weight to things that are easy to fake: follower counts, partnership logos and roadmaps.

If a single answer is a serious red flag, such as hidden admin control over user funds, one strong area elsewhere does not cancel it out.

Red flags

• Promises of guaranteed or fixed high returns.
• No working product, only a roadmap and a token sale.
• Team or insiders holding a large share with short or no vesting.
• Unaudited contracts, or admin keys held by a single person.
• Pressure to buy quickly, or to move the conversation to private messages.
• Claims of partnerships or endorsements that the named company has not confirmed.
• Withdrawals that are delayed, limited or require extra "fees."

How The Crypto Guide applies this checklist

Every coin profile in our coin directory condenses this research into the Utility Lens. It rates four things: real usage, token necessity, decentralization and track record. Each rating comes with a one-sentence reason and sources you can check.

The Lens is not a price rating or a buy signal. It is a quick way to see what a token does and where the weak spots are, so you can decide what to dig into next.

Where to go next

1. The Utility Lens: the exact definitions behind our ratings.
2. Crypto risk management: turn research into sensible limits.
3. ISO 20022 explained: the summit lesson, testing a popular claim against the facts.

Missed the previous lesson? Start with market cap and tokenomics.

Updated October 4, 2026 by The Crypto Guide editorial team. Educational content, not financial, legal or tax advice. Spot an error? Request a correction.