Start with the exact claim
Copy the source's wording and identify what it describes: an announced allocation, a contractual entitlement, an amount currently claimable or an observed transfer. Record the token contract, chain, schedule version, beneficiary category, time zone and evidence date. If a field is unknown, keep it unknown.
Do not convert “scheduled for release” into “sold today.” To support a claim about an actual sale you would need evidence of that sale, not merely a calendar entry or movement between addresses. This distinction is a standard of evidence, not an assertion about any real project.
Evidence:
A schedule is not the same as a release transaction
OpenZeppelin's VestingWallet documentation provides a concrete software example: it distinguishes amounts vested, releasable and released, and supports customizable schedules. Its documented implementation can make later deposits partly releasable when vesting has already begun. That is a reason to inspect implementation and funding history rather than infer behavior from a chart label. Contract documentation.
This example is not a claim that every token uses that contract. No live deployment, beneficiary, upgrade path or transaction was inspected for this guide. A project's actual mechanism might differ; matching a familiar function name does not establish an audited implementation.
Evidence: OpenZeppelin VestingWallet documentation
Read the provider's circulating-supply definition
CoinGecko's methodology describes circulating supply as an estimate and excludes certain project-held or restricted balances. In particular, technical unlocking does not by itself mean a foundation or treasury allocation enters its circulating figure. Supply methodology.
Consequently, compare a dashboard observation with its methodology and timestamp. Do not expect an announced unlock size to equal the next change in a provider's displayed supply. This is a provider-specific example; the CryptoTrades Markets page uses a different source and does not inherit CoinGecko's classifications. No reconciliation of a real token's supply has been performed here.
Evidence: CoinGecko supply methodology
Worked example: one release, several denominators
All inputs below are invented. Suppose a fictional token has 1,000 million existing tokens, a provider-classified circulating balance of 400 million and an upcoming release of 20 million. Assume the release comes from already-existing supply, with no mint or burn.
The starting unchanged-price illustration is $800 million. The $24 million difference comes entirely from the assumed classification change and fixed hypothetical price. It is not measured capital inflow or a price prediction. The remaining eight million are excluded only by this invented classification assumption; no real provider decision is implied.
A headline saying “a 5% unlock” is incomplete without its denominator. Existing supply, circulating supply and an allocation's remaining balance can produce different percentages. Record the numerator, denominator and units beside the figure.
| Question | Calculation | Result |
|---|---|---|
| Release as share of existing supply | 20 / 1,000 × 100 | 2% |
| Release as share of starting circulating balance | 20 / 400 × 100 | 5% |
| If provider classifies only 12 million as newly circulating | 400 + 12 | 412 million |
| Classified circulating increase | 12 / 400 × 100 | 3% |
| Unchanged-price valuation illustration at $2 | 412 million × $2 | $824 million |
Evidence:
Use a reconciliation worksheet
Use separate rows for assertions and observations. If a project's schedule and dashboard disagree, write both statements with their dates. Do not silently choose the larger figure or substitute an unrelated chain's supply.
| Field | Evidence to save | What remains unanswered |
|---|---|---|
| Schedule | Original dated document and time zone | Amendments or conditions |
| Mechanism | Relevant contract and implementation | Actual entitlement and control |
| Release | Public transaction or verified record | Beneficiary's later actions |
| Supply estimate | Provider definition and observation time | Classification changes |
| Market observation | Venue, pair and timestamp | Executable liquidity and future prices |
Evidence:
Put the data in context
The Markets page is a sourced snapshot, not an unlock monitor. It cannot determine which tokens become claimable or calculate sell pressure. No automatic supply reconciliation or token-unlock input exists in the current planning tools.
Read supply and FDV for the broader definitions and market-data literacy for timestamp context. This article's narrower task is tracing a release claim through evidence and classification.
Evidence:
Limits and next steps
Before using a real unlock figure, identify its original source, schedule conditions and observation window. Check whether totals cover the same chain and token representation. An apparently precise calendar should not hide uncertainty about classification or beneficiary behavior.
This guide uses public documentation and fictional arithmetic only. It supplies no current unlock calendar, tested contract or trading recommendation. Sources were read November 18; undated documentation has a retrieval date, not an invented publication date. Report a correction using public evidence rather than private account records.
Evidence:
Sources & method
- OpenZeppelin VestingWallet documentation
Documented schedule, releasable/released distinction and late-deposit caveat. No live contract inspected or audited. Checked 2026-11-18.
- CoinGecko supply methodology
Provider-specific supply estimates and project-wallet exclusions. Does not describe the CoinMarketCap source used by CryptoTrades Markets. Checked 2026-11-18.
Continue learning
Found an error? Contact the editorial team with the page and supporting source. Never send private account information.