The claim class: a project states that a specific allocation (team, investor, treasury, or otherwise) is locked and will not unlock, in whole or in part, until a stated future date.
Claim class: a pattern of statements, not one attributed, dated quote.
Receipt to pull The receipt is the vesting or lockup contract itself, read directly on-chain: the addresses whose tokens it holds, the unlock schedule encoded in its code (cliff dates, linear release periods, or specific unlock timestamps), and confirmation that the actual tokens subject to the claim are held by that contract rather than sitting freely in a wallet with no enforced restriction at all. No single receipt is linked: this piece explains how to check this kind of claim and does not grade one specific claim.
A vesting contract confirmed to be holding tokens under a coded schedule shows that specific allocation cannot move before the coded date. It does not confirm other, undisclosed allocations are under any similar restriction, and it does not prevent the project from creating entirely new tokens through a separate minting mechanism that is unrelated to the vesting of this particular allocation.
Not financial advice. The Crypto Online is a verification desk, not an accredited fact-checker.
A token unlock chart on a project’s own site is a description of a schedule the project says it will follow. The vesting contract enforcing that schedule on-chain is the thing that actually decides when tokens become available, and the two do not always agree.
The Claim
The claim class: a project states that a specific allocation (team, investor, treasury, or otherwise) is locked and will not unlock, in whole or in part, until a stated future date.
The Receipt
The receipt is the vesting or lockup contract itself, read directly on-chain: the addresses whose tokens it holds, the unlock schedule encoded in its code (cliff dates, linear release periods, or specific unlock timestamps), and confirmation that the actual tokens subject to the claim are held by that contract rather than sitting freely in a wallet with no enforced restriction at all.
Some projects enforce vesting through a dedicated on-chain contract that nobody, including the team, can bypass before the coded schedule allows it; others rely on an informal or off-chain commitment, where tokens already sit in an ordinary wallet and the “lock” is simply a promise not to move them. These are very different strengths of claim, and the contract read is what tells them apart.
What It Doesn’t Prove
A vesting contract confirmed to be holding tokens under a coded schedule shows that specific allocation cannot move before the coded date. It does not confirm other, undisclosed allocations are under any similar restriction, and it does not prevent the project from creating entirely new tokens through a separate minting mechanism that is unrelated to the vesting of this particular allocation.
How to Check It Yourself
- Identify the specific allocation the no-unlock claim refers to (team, investor, treasury, or another category) and the address or contract the project says holds it.
- Check whether that address is an ordinary wallet or a dedicated vesting or lockup contract, since only the latter enforces the schedule in code rather than by promise.
- If it is a vesting contract, read its coded schedule directly, including any cliff date and the release pattern after that cliff, rather than trusting a chart alone.
- Confirm the actual token balance held in that contract matches the allocation size the claim describes.
- Check whether a mint function elsewhere in the token contract could introduce new supply outside the vesting schedule entirely, which the no-unlock claim would not cover.
- Where multiple allocations exist, check each one separately rather than assuming a confirmed lock on one category applies to all of them.
A Worked Example
A project states no team tokens unlock before a date roughly a year out. A reader finds the address holding the team allocation and discovers it is an ordinary wallet, not a vesting contract, with no coded restriction preventing a transfer at any time. The tokens have, in fact, not moved as of the reader’s check, which is consistent with the claim so far, but the absence of any contract enforcing that schedule means the promise rests entirely on the team’s own continued restraint.
What Supported, Contradicted, and No Receipt Look Like
Supported: The specific allocation is held in a dedicated vesting contract whose coded schedule matches the claimed unlock date, with the token balance held matching the allocation size described.
Contradicted: The tokens described as locked sit in an ordinary wallet with no enforced on-chain restriction, or a vesting contract’s actual coded schedule allows unlocks earlier than the publicly claimed date.
No receipt: No specific address or contract is disclosed for the allocation in question, leaving the no-unlock claim unconfirmed either way.
Red Flags
- A lock or vesting claim refers only to an ordinary wallet address with no dedicated contract enforcing any schedule.
- The vesting contract’s coded schedule, once read, allows an earlier unlock than the publicly stated date.
- Only one allocation’s lock is disclosed and verified while other known allocations are left unaddressed.
- A mint function elsewhere in the token contract could introduce new supply with no relationship to the vesting schedule being highlighted.
- The unlock chart shown in marketing materials cannot be reproduced from the vesting contract’s own coded parameters.
A Practical Complication to Expect
Some vesting arrangements are enforced off-chain through a traditional legal contract between the project and a token recipient, with the tokens themselves sitting in an ordinary wallet the recipient could technically move at any time, relying entirely on contractual and reputational consequences rather than code to keep the schedule honored. This is a materially different, and generally weaker, guarantee than an on-chain vesting contract, even though both might be described publicly using the same word, locked. Readers should distinguish a legal commitment to vest, which depends on the recipient’s continued compliance and the practicality of enforcing that contract, from a coded restriction that makes early movement technically impossible regardless of anyone’s intentions.
Why It Matters
Unlock schedules sit directly upstream of future sell pressure and circulating-supply changes, which makes the difference between a coded, enforced schedule and an informal promise one of the more consequential distinctions in this entire series, and one that a direct contract read settles cleanly.
See our pieces on total versus circulating supply and staking APY versus contract for related checks on future supply and returns.
FAQ
Why does it matter whether a lock is enforced by a contract versus a promise?
A contract-enforced lock cannot be bypassed by the holder regardless of intent; an informal commitment depends entirely on that party choosing to honor it, which is a meaningfully weaker guarantee for anyone relying on the claimed schedule.
What is a cliff in a vesting schedule?
A cliff is a period during which nothing unlocks at all, followed by a release that begins only after the cliff date passes; a contract’s coded cliff date is what actually determines when the first tokens become available, regardless of what a chart shows.
Can a project change a vesting contract’s schedule after the fact?
Generally no, if the contract was deployed without an upgrade or admin mechanism allowing changes; if such a mechanism exists, that itself is worth checking, since it would mean the coded schedule is not as fixed as it appears.
How does this relate to the total-versus-circulating-supply check?
They are closely linked: tokens under an enforced vesting schedule are a common reason circulating supply is lower than total supply, and reading the vesting contract is exactly how that exclusion gets confirmed rather than assumed.
If a vesting contract allows its schedule to be changed by a governance vote, does that undermine the no-unlocks-until claim?
It changes the nature of the guarantee rather than eliminating it outright: the schedule is still coded and enforced by default, but it is not as absolutely fixed as a contract with no amendment mechanism at all. Readers should check whether such a governance-change mechanism exists, who can trigger it, and what threshold it requires, since a schedule that can be altered by a small, concentrated group of holders offers a meaningfully weaker guarantee than one that cannot be changed by anyone at all.
Not financial advice. The Crypto Online is a verification desk, not an accredited fact-checker; we describe how a claim like this can be checked, never whether to buy, sell, or hold anything on the back of it.
Sources
This piece links no outside source: it explains a class of claim and the public records you would check, rather than grading one specific statement. When a specific claim is checked, every source link is listed here with its status.
Not financial advice. Human-edited; AI-assisted drafting is disclosed in our editorial guidelines. Spotted an error? See how corrections work.



