Projects publish vesting schedules, and whether those schedules are actually enforced depends on the contracts behind them.
The claim and the mechanism
A schedule stated in a document is an intention.
A vesting contract holding tokens and releasing them on a schedule is enforcement.
Which are very different, and the difference is verifiable on chain.
What to check
Whether tokens are actually held in a contract, what the release schedule is, and whether anyone can withdraw early.
Which is readable from the contract code.
Many published schedules correspond to no contract at all, with tokens simply held in a wallet.
Revocability
Some vesting contracts allow an administrator to revoke or accelerate.
Which serves legitimate purposes such as departing team members.
It also means the schedule is not binding, and this is checkable.
Cliff and linear release
A period with no release followed by gradual vesting.
Which concentrates a supply increase at the cliff date.
Cliff dates are known in advance and are tracked publicly by several services.
Borrowing against locked tokens
Holders can sometimes obtain liquidity against locked positions.
Which economically transfers exposure without transferring tokens.
The lock-up's purpose is partially defeated, and it is generally not visible on chain.
Over-the-counter sales of vested claims
Selling the right to future tokens privately.
Which has the same effect and is invisible to holders relying on the published schedule.
Disclosure of such arrangements is rare.
Post-vesting behaviour
Whether released tokens are sold is observable on chain.
Which is a more informative signal than any statement about long-term commitment.
Several analytics services track known team and investor addresses.
How to verify
Find the vesting contract address, read the schedule from the contract, check for administrative functions, and watch the destination addresses after release.
This is methodology rather than a recommendation regarding any asset.
Standard implementations
Well-known vesting contract libraries are audited and widely used.
Which is preferable to bespoke implementations for obvious reasons.
Custom vesting code with administrative backdoors has appeared in practice.
Multi-signature holding
Tokens held in a multisignature wallet with a stated policy rather than an enforcing contract.
Which is a commitment rather than a constraint.
The distinction is worth making explicitly when assessing a project.
Third-party escrow
Independent parties holding tokens under contractual terms.
Which provides legal rather than technical enforcement.
This is more common for institutional investors than for team allocations.
Unlock impact
Scheduled unlocks are public information and their effects are anticipated by markets.
Which means the effect is generally not concentrated on the date itself.
Analytical services publish upcoming unlock calendars.
What good practice looks like
Enforcing contracts, published addresses, no administrative acceleration and disclosure of any side arrangements.
Investor terms
Private sale agreements frequently include vesting terms enforced contractually rather than on chain.
Which are not publicly verifiable.
Discrepancies between published schedules and actual movement have exposed such arrangements.
Team departure
What happens to unvested allocations when someone leaves.
Which requires a mechanism and is frequently unaddressed.
Disputes over this have become public in several projects.
Tax timing
Vesting events may create tax liability at the point tokens become available.
Which can arise before any sale occurs.
This has caused genuine difficulty for recipients in falling markets.
Monitoring tools
Services track vesting contracts and known allocation addresses.
Which makes verification straightforward.
The verification habit
Check the contract rather than the document, and watch the addresses rather than the statements.
This is methodology and not advice about any asset.
Why this matters
Supply schedules affect every holder, and whether they are enforced determines whether the schedule means anything.
Which takes minutes to verify and is verified by very few people.
The information is public precisely so that it can be checked.
A short verification routine
Locate the vesting contract, read the release schedule, check for revoke or accelerate functions, and note the destination addresses.
Which is four steps on a block explorer and takes under ten minutes.
Projects that make this easy are generally the ones with nothing to hide, and the ones that make it difficult are informative in themselves.
Investor behaviour after unlock
Whether allocations are held or sold is observable on chain.
Which provides evidence about alignment that statements do not.
Several projects have seen concentrated selling immediately following cliff dates, and several have not.
Why documents alone are insufficient
A published schedule with no enforcing contract is a promise, and promises are not what the technology was meant to replace.
A last note
The whole point of putting an arrangement on a public ledger is that it can be checked. A schedule described in a document and enforced by nothing has given up that advantage entirely.
Summary
A schedule is a claim; a contract is enforcement. The difference is publicly verifiable in minutes.
Projects that put the arrangement in code have made a choice, and so have the ones that did not.