Evaluate crypto assets: use, supply and liquidity

Begin with the exact asset

Identify the name, network and official identifier. Similar tickers can represent different assets, and wrapped forms can have additional dependencies. Read the project’s established documentation rather than relying on a price page’s logo.

Separate the project, application and token. An application can be useful without giving token holders a claim on its earnings. A company can develop technology without its shares being the same thing as a token. The asset types guide explains the basic distinctions.

Write the holder’s actual right in ordinary language. If the right is only described as future utility, record that stage and what evidence would confirm delivery. Do not invent company ownership, redemption or revenue rights from a marketing term.

Evaluate use with evidence

Ask what task the system performs and why this particular asset is needed. A native fee role, voting function and off-chain claim are different uses. Identify dependencies and whether another mechanism could perform the task.

Look for defined actual usage rather than only announcements. Metrics need a period, method and scope. Addresses are not necessarily unique people, and transaction count is not automatically business revenue.

The adoption guide separates proposed, available and used capabilities. A feature being technically possible does not establish sustained demand for the token or a particular market valuation.

Read supply definitions

Record circulating supply, total supply, any maximum rule and the source date. Providers can use different methods for classifying units, so compare definitions before combining figures. A supply estimate should not be treated as timeless.

Read whether issuance, burns, vesting or administrative powers can change the relevant amount. If future releases are part of the design, identify the documented conditions and period. Do not assume every scheduled unit will be sold immediately, but do not ignore its existence.

Check concentration and control without oversimplifying address data. One address can represent a service holding assets for many users, while one participant can control several addresses. A raw address ranking is not a complete ownership map.

Calculate valuation using consistent units

Asset A has the lower unit price and larger calculated circulating valuation in this invented example. That does not prove either is expensive or inexpensive. It shows why price per unit alone cannot rank the whole asset.

The Coinbase market-cap explanation describes the price-times-supply calculation. A fully diluted measure can use another supply assumption. Preserve the definition rather than selecting whichever number supports the preferred comparison.

Market value is not cash available for all holders to withdraw. Applying a marginal price to a supply count does not prove every unit can be sold there. A valuation table therefore needs a separate liquidity review.

Inspect executable liquidity

Identify the venue, pair, bid or ask direction and intended quantity. A top price can cover only a small amount. An order can require several levels and produce a different average execution from the first displayed quote.

Historical volume measures activity over an interval, not the current orders available. A reported high volume does not guarantee a large exit near the last price. Read the scope and unit of the volume figure as well.

The liquidity guide separates spread, depth, slippage and fees. Use an actual preview or documented snapshot for an execution question rather than relying only on a ranking page.

Review control and dependencies

Read who can modify relevant contracts, issue or pause tokens, manage reserves or control an interface. A public blockchain does not automatically remove privileged roles from every application built on it. Record the powers and their documented limits.

An asset connected to off-chain reserves adds questions about custody and redemption. A bridged representation can add a bridge dependency. A decentralised-sounding name does not explain those arrangements.

Separate asset risk from the service holding it. A well-understood token can still be lost through exposed keys, a mistaken network or an unreliable custodian. The risk framework helps keep those categories visible.

Compare an adverse scenario

Write what happens if use grows more slowly, a feature is delayed, supply assumptions change or liquidity weakens. Do not make the entire conclusion depend on one favourable announcement. Include the amount exposed and realistic costs.

A lower unit price after a decline does not alone prove better value. The underlying assumptions may also have changed. Adding another purchase can lower average cost while increasing the total money at risk.

Keep a scenario separate from a prediction. A calculator can show a hypothetical result, but cannot establish the probability of its price inputs. Label the numbers as illustrative and preserve the assumptions.

Build a dated evaluation sheet

Use columns for asset identity, function, holder rights, supply, valuation method, liquidity, control, custody and evidence dates. Mark unresolved points explicitly. Add primary documentation rather than a long list of promotional summaries.

Record commercial interests around the claim, including referral incentives or holdings where disclosed. An interest does not automatically invalidate a fact, but it matters to how the story is framed. The recommendation review provides further questions.

Finish with what the evidence supports and what could change the view. This approach can clarify a project without naming a guaranteed winner or treating a large market value, low unit price or popular narrative as proof of future returns.

Check the date of every input

A supply count, price and usage statistic can come from different periods. Combining them without labels can produce a coherent-looking table that describes no actual point in time. Preserve each date and explain any lag. If an updated figure replaces an older one, keep the original record so the change can be inspected. A research worksheet should reveal timing limitations rather than hide them behind extra precision.

Continue reading