A practical guide to evaluating Web3 projects

Tokenomics describes the economic design of a token: how many exist, who receives them, when they become transferable, and what role the token plays in a product.

Good tokenomics documentation answers simple questions directly. Is the supply fixed or inflationary? Who controls minting? Why does the product need a token at all?

Design choices create incentives. Large early allocations, short vesting periods, or high emissions can introduce selling pressure, while a token without a clear role may depend mostly on speculation.

Distribution describes how the total supply is divided among categories such as community, team, investors, treasury, ecosystem funds, and liquidity.

Concentration matters. When a small number of wallets control a large share of supply, their decisions can have an outsized effect on market conditions and governance.

On-chain holder data can help, but labels can be misleading: exchange wallets, contracts, and vesting escrows may hold large balances on behalf of many users or for scheduled releases.

Liquidity is the ability to buy or sell an asset without significantly moving its price. In automated market makers (AMMs), it comes from paired reserves deposited into a pool.

In a simple constant-product pool, the starting price equals the paired asset reserve divided by the token reserve. Each trade moves the price along a curve; smaller pools move more for the same trade size.

Liquidity can be withdrawn unless it is locked or otherwise restricted. Lock claims should be verified on-chain, including their duration and who controls the lock.

Circulating market capitalization multiplies the current price by the circulating supply — the tokens that are currently transferable.

Fully diluted valuation (FDV) multiplies the same price by the total or maximum supply, as if every token were already circulating.

A large gap between the two signals that many tokens are still locked or unissued. As those tokens unlock, supply grows, which can affect price if demand does not grow alongside it.

Vesting releases allocated tokens over time rather than all at once. A schedule usually combines a cliff (a period with no releases) and a linear or periodic release afterwards.

Unlock events increase circulating supply. Large or concentrated unlocks — especially for early investors or team members — are worth tracking ahead of time.

Schedules are only as reliable as their enforcement. Vesting enforced by a verified smart contract is easier to confirm than a promise in a document.

Always obtain contract addresses from official project sources, then confirm them on a reputable block explorer. Token names and symbols are not unique and are easily copied.

Verified source code lets anyone read the deployed logic. Pay attention to owner-only functions such as minting, pausing, blacklisting, fee changes, or upgradeability through proxies.

An audit reviews code at a point in time. Confirm the report directly with the auditor and check that the audited code matches what is deployed.

Some signals appear frequently in projects that later disappoint users. They are reasons to investigate further, not definitive conclusions.

Equally, the absence of these signals does not make a project safe. Research reduces uncertainty; it does not remove it.