For me, adoption and tokenomics need to be evaluated together.

Product adoption shows whether the network or application is solving a real problem. Active users, recurring transaction volume, developer growth and real demand are all positive signals. But none of that automatically guarantees that the token itself captures value from the ecosystem.

That is where tokenomics become important.

If the token has aggressive emissions, large insider allocations or major unlocks scheduled over the next few years, growing usage may not be enough to offset persistent selling pressure. A project can succeed operationally while the token still underperforms.

I also pay attention to utility. If users can access the product without ever needing the token, then the connection between ecosystem growth and token demand may be weak. On the other hand, if the token is required for staking, transaction fees, governance or access to core protocol functions, the relationship can be much stronger.

Fully diluted valuation is another area that matters. A token may appear reasonably valued based on circulating market capitalization while a large percentage of supply has not yet entered the market. That can create a very different long-term risk profile.

At the same time, tokenomics cannot rescue a product nobody uses. Scarcity, burns and limited supply may support the narrative, but without real demand there is no sustainable foundation behind the token.

For me, the strongest projects are those where real product adoption and token economics reinforce each other. Users create demand for the product, and the structure of the token allows part of that growth to translate into long-term value.

When researching a new crypto project, what matters more to you: product adoption or tokenomics?

Would you invest in a project with excellent user growth but weak token value capture?

And which tokenomics metric do you consider most important — circulating supply, unlock schedule, emissions, insider allocation, token utility or fully diluted valuation?

Developer growth is one of the first things I watch. A network with active builders, improving tooling and regular application launches has a much stronger foundation than one driven mainly by token incentives. Developers create the products that eventually attract users and capital.

Liquidity matters just as much. A promising ecosystem needs more than a few applications. It needs stablecoins, decentralized exchanges, lending markets, bridges, wallets and infrastructure that allow capital to move efficiently across the network.

User activity can be useful, but raw transaction counts are not enough. Bots, airdrop farming and short-term incentives can inflate activity. I would rather see repeat users, sustained DEX volume, growing stablecoin balances and applications that continue to be used after rewards decline.

Infrastructure quality is another important factor. Reliable RPC services, indexing tools, developer SDKs and wallet integrations can determine whether teams actually want to build on a network. An ecosystem can have excellent technology and still struggle if the developer experience is poor.

I also look at how differentiated the network is. If a new blockchain offers almost exactly the same features as several established competitors, it needs a very strong reason to attract users and developers away from existing ecosystems.

Token economics should not be ignored either. Large unlocks, aggressive emissions or heavily concentrated allocations can create selling pressure even when ecosystem activity is growing. A strong network does not automatically mean a strong token investment.

For me, the most promising ecosystems are the ones combining real developer momentum, deepening liquidity, useful applications, sustainable user activity and a clear technical or economic advantage.

Which new crypto ecosystems are you watching most closely in 2026?

What matters most to you — developer growth, TVL, stablecoin liquidity, active users, application revenue, infrastructure or tokenomics?

A professional website, active social media channels and a detailed roadmap can make almost any project look credible. For me, the difference starts with whether there is a real product problem being solved and whether the team is building something users would still want even if the token price disappeared from the conversation.

The product itself is usually the strongest signal. A real startup should have something tangible: a working application, protocol, testnet, developer tools, infrastructure or at least a product that can be tested. If everything depends on future promises, token listings and marketing campaigns, the project is much harder to evaluate.

User behavior matters as well. I want to know whether people are using the product because it is useful or because they expect an airdrop, token reward or speculative return. Incentive-driven activity can make a project look much larger than it really is.

Developer activity is another important signal. Regular code updates, technical documentation, integrations and visible engineering progress usually tell more than announcements. A startup that is consistently shipping has a different profile from one that mainly publishes partnership graphics and price-related content.

Token design is where hype often becomes easier to spot. If the token does not have a clear role in the product, or if most of the conversation focuses on price potential rather than utility, governance or network economics, I become much more cautious.

Funding and allocation also matter. Large insider allocations, aggressive unlock schedules or extremely high fully diluted valuations can create a situation where early investors have very different incentives from ordinary users.

I also look at how the team communicates. Real builders usually talk about product limitations, technical trade-offs and execution challenges. Hype-driven projects tend to focus more heavily on vague claims like “revolutionary,” “next generation” or “mass adoption” without showing measurable evidence.

Another important signal is whether the project would still make sense without its token. If the product has no reason to exist unless token demand keeps increasing, that tells me the token may be the product rather than the technology.

How do you distinguish a real Web3 startup from a project built mainly around token hype?

What matters most to you — working product, user retention, developer activity, token utility, team history, funding structure or measurable adoption?

And what is the biggest warning sign that tells you a new crypto project is more marketing than substance?

The first thing I usually check is the problem the project claims to solve. If the use case is vague, already handled better by existing protocols or only exists to justify launching a token, that is an immediate concern. A strong project should have a clear reason to exist beyond price appreciation.

Then I look at the product itself. Is there a working network, application, protocol or test environment? Are people actually using it? A polished website and roadmap are easy to create, but a functioning product gives much stronger evidence that the team can execute.

Developer activity matters as well. Public repositories, regular updates, documentation and visible technical progress can reveal whether development is active or mostly marketing. I would rather see consistent engineering work than constant announcements with little substance behind them.

Tokenomics are another major area. I want to understand circulating supply, total supply, unlock schedules, insider allocations and how the token is supposed to capture value. A strong product can still be a poor investment if future dilution is too aggressive.

Team and funding structure also deserve attention. Anonymous teams are not automatically bad in crypto, but I want to know whether the people behind the project have relevant experience, whether previous projects can be verified and how much influence early investors or insiders may have.

Liquidity is another practical factor. A token can have an impressive valuation while still having weak market depth. Thin liquidity can make both entry and exit much more difficult than the market cap suggests.

I also check security. For DeFi or smart contract-based projects, audits, bug bounties, admin controls and contract upgrade permissions matter. For infrastructure projects, I want to understand how decentralized and resilient the system actually is.

Finally, I compare the narrative with the data. If a project claims massive adoption but has little real activity, weak developer growth or limited liquidity, that gap matters more to me than social media engagement.

What do you check first when researching a new crypto project?

Do you start with the product, team, tokenomics, developer activity, security, liquidity or actual user adoption?

And what single red flag is enough for you to stop researching a project completely?