HostNexFlow › Guides › Vesting schedules on-chain
Vesting schedules on-chain
'Locked for two years' is either a smart contract or a sentence — and only one of those is enforceable. Here's how to find the real vesting schedule and read what it does to your exit.
Token teams promise lockups constantly — "team tokens vested over 24 months," "investors locked for a year" — and every one of those claims lands in one of two places: a verifiable vesting contract that enforces the schedule with code, or a sentence in a deck that enforces it with trust. The difference isn't pedantry. A cliff date on-chain is a sell-pressure calendar you can read months ahead; a promise is a vibe. Diligence here is mechanical: find the contract, read the dates, map the amounts, and know exactly when the float multiplies.
What a vesting contract actually is
A vesting contract is a custody program that holds tokens and releases them on a schedule — either in tranches at fixed dates (cliff vesting) or continuously (linear streaming, the Solana-streamflow style). The tokens are visible in the contract's custody the whole time; what the contract prevents is withdrawal before the date. The recipient can't accelerate it, the team can't claw it back early to sell, and the schedule is public — which is the entire point: enforced, auditable lockup, not a handshake.
The standard instruments: dedicated vesting/streaming protocols (Streamflow and kin on Solana; Sablier, Hedgey, and custom lock contracts on EVM), multisig-held timelocks, and bespoke contracts from the launch stack. What unites them is that the lockup lives in code a stranger can audit — the "locked" claim becomes an address you can inspect.
Reading the schedule that matters
Find the vesting contract addresses
Honest projects publish them (docs, tokenomics page). Otherwise: trace the supply — find the largest token-holding accounts that aren't team wallets or pools, and check whether they're program-owned custody accounts. A giant balance sitting in a known vesting program's account is a lock; the same balance in a plain wallet is a promise.
Extract the dates and amounts
Vesting accounts expose their parameters — start, cliff, duration, amount. Translate the schedule into a calendar: which dates release how much supply into circulation. The cliff date is the violent one — months of zero unlocks, then a chunk that can dwarf the daily volume.
Measure the unlock against liquidity
An unlock is only as dangerous as the market that must absorb it. A 20% cliff into deep, multi-million liquidity is a headline; the same cliff into a shallow pool is a price event. Unlock size ÷ typical daily volume is the ratio that tells you how many days of sell-pressure a cliff represents.
Hunt the bypass wallets
The schedule only covers what's inside it. Check the deployer's wallets, early snipers, and "advisory" allocations for large unlocked balances that sit outside the vesting story — a clean contract beside a fat unlocked insider wallet is theater. The distribution read →
The red flags that fool the checkbox
"Locked" in a team wallet. Tokens held by the deployer with a promise not to sell aren't locked — they're inventory. The promise is revocable at the holder's discretion, which is to say it isn't one.
Vesting that started months before listing. A "24-month vest" whose clock started before you heard of the token may expire inside your holding period — read the start date, not the duration.
Linear streams presented as locks. A stream that's 80% complete is 80% unlocked — the remaining "vest" is a sliver of the original commitment.
The gap between float and circulating. Even an honest schedule doesn't save a thin float — the supply-shape read is the complement to this one, and the launch pattern built on it is where vesting literacy pays for itself.
The one-line discipline: never accept "locked" as an adjective — demand it as an address. A real lockup is a contract you can inspect, with dates you can put on a calendar. Everything else is the same sentence with better typography.
The schedule is one input — the posture is the whole read
Holder concentration, authorities, liquidity depth — the scan reads the token's whole posture so the vesting calendar lands in context.
Frequently asked
Verify a vesting schedule on-chain?
Find the vesting contract addresses (docs or traced from top non-pool holders), read start/cliff/duration/amount — a real lockup is inspectable; a promise isn't.
What is a vesting cliff?
A date when a large tranche unlocks at once after zero-release months — the dated sell-pressure events to calendar, especially into thin liquidity.
'Locked in the team wallet' — real?
No — deployer-held tokens with a promise are inventory, not vesting. Code-enforced vs trust-enforced are different things.
What are bypass wallets?
Large unlocked balances outside the vesting story — deployer, snipers, 'advisory.' A clean contract beside fat unlocked insiders is theater.
Do linear unlocks count as locked?
Partially — streams release continuously, so read progress and remaining flow, not the original duration headline.