New tokens: supply, unlocks and dilution assumptions

Start with the exact token and network

Identify the official asset and contract or other relevant identifier. A ticker can be reused by another project, and a wrapped representation can add dependencies. Do not analyse a supply chart before establishing which asset it describes.

Read the project’s issuance and administrative rules. Who can create units, change the schedule or exercise relevant permissions? An attractive fixed-supply headline should be checked against the actual design. A maximum claim and a current circulating estimate are different pieces of information.

Keep a dated source record. If a project migrates tokens or changes an implementation, earlier supply information may need reconciliation. Do not silently combine figures from different versions.

Distinguish circulating, total and maximum measures

Circulating supply is a provider-defined estimate of units counted as available in circulation. Total supply and maximum supply can answer different questions under the source’s definitions. Do not assume every provider classifies locked, treasury or bridged units identically.

A market-cap figure commonly multiplies a price by a circulating measure. A fully diluted figure can use another supply assumption. Neither is meaningful without the definition and timestamp. The evaluation guide separates those measures from liquidity and asset quality.

If a source does not explain a count, mark it uncertain. Extra decimal places do not compensate for an unclear classification. A comparison should preserve a supply disagreement rather than hide it in an average.

Read allocations and beneficiaries

An allocation describes who is intended to receive units under the project’s arrangements. Categories such as team, investors, community or treasury can have different rights and conditions. Read the underlying documentation instead of assuming the category name explains control.

An address-level view is not a complete ownership map. One address can be a service holding assets for many users, and one participant can use multiple addresses. A concentration claim needs a method and limits.

Ask whether allocated units already exist, will be issued later or are represented through another claim. Those structures can affect how a schedule should be interpreted. Do not count the same units twice merely because they appear in both an allocation table and a contract balance.

Vesting and unlocks need actual rules

Vesting can define when units become available to a beneficiary. A cliff can introduce a condition before release begins, while another design can release gradually. The actual implementation and terms determine the rule.

OpenZeppelin’s finance documentation provides an example of a vesting contract with a configurable schedule. It demonstrates why the contract’s parameters matter; it does not certify any project claiming to use vesting.

Read whether a schedule is time-based, milestone-based or subject to other conditions, and whether relevant powers can change it. A published chart is a summary to verify against the project’s actual documentation, not a guarantee that every unit will move at the plotted time.

Calculate the scale of a release

The release equals 20% of the earlier circulating count and about 16.67% of the assumed later count. Both percentages can be correct because the denominators differ. State which one you use instead of presenting an unexplained unlock percentage.

If the price is hypothetically 1 dollar and remains unchanged, the calculated circulating valuation rises from 10 million to 12 million dollars. That arithmetic does not prove 2 million dollars of new cash entered or that the price will remain unchanged. It simply applies one price assumption to two supply counts.

Do not turn availability into guaranteed selling

Units becoming transferable do not necessarily mean every beneficiary sells immediately. Intentions, constraints and actual market conditions matter. Conversely, a statement that nobody plans to sell is not a permanent enforceable market commitment unless supported by the relevant arrangement.

Inspect actual transfers and disclosures carefully, while recognising their limits. A transfer to a venue can have several purposes and does not by itself reveal a completed sale. Public records show actions under the network’s data model, not every private intention.

The transaction guide explains why addresses, transactions and ownership conclusions should remain separate. Avoid filling gaps in the evidence with a confident price story.

Compare release size with executable liquidity

A supply count and historical volume are not the same as current order-book depth. A large release relative to a stated volume can raise a question, but it does not mechanically predict a percentage price change.

Read the venue, pair, time and available quantity for an execution scenario. The liquidity guide explains spread, depth and average fills. A headline market value cannot guarantee an exit for a particular holding.

Also consider fees, custody and withdrawal support. A token can be listed while the route you need is unavailable. A supply analysis does not replace a review of the service holding or exchanging it.

Build a schedule record and adverse case

Record asset identity, supply definitions, allocation source, release rule, relevant dates, beneficiary categories and change powers. Add a source and review date for each item. Mark the difference between a planned event and a completed one.

Use scenarios rather than a single automatic conclusion: the schedule occurs as documented, it changes, or liquidity is weaker than assumed. Calculate the consequence for a stated exposure without claiming a probability unsupported by evidence.

Newness and low unit price are not independent reasons to expect a gain. A useful supply review clarifies what units exist, who can control them and which assumptions remain. It does not select a token or promise that an unlock creates a predictable trading result.

Reconcile the schedule after the event

When a scheduled date passes, check what actually became available and what the relevant records show. Keep the planned schedule and observed outcome separately dated. Do not infer a completed release from a calendar reminder alone.

Continue reading