"What schedule should we use?" is the first question every team asks after deciding to vest — and the answer buyers expect is more standardized than most founders realize. Here are the norms, the data behind them, and the schedules that read as red flags.
What vesting schedule do most crypto projects use?
The most common structure for team allocations is a one-year cliff followed by two to three years of linear release — a pattern inherited from startup equity and now the default expectation across crypto. Industry practice puts team allocations at roughly 20% of supply, and Team Finance's own analysis of lockup data found team lockup periods averaging a little over two years (source, as of August 2026). Independent data agrees: Sablier's analysis of 500,000+ on-chain vesting streams found cliffs and multi-year linear schedules dominating serious deployments. Deviating from the norm isn't forbidden — but you should expect to explain the deviation, because informed buyers benchmark you against exactly these numbers.
How should you set the cliff?
Set the cliff to match the commitment question, not the calendar: for team members, one year answers "will you still be here?"; for advisors, three to six months matches the useful life of most advisory relationships. The cliff is the schedule's filter — nothing releases until it passes, so it protects the project from paying out to people who leave early. A cliff shorter than three months barely filters anything; a cliff longer than eighteen months starts reading as either exceptional conviction or a retention problem waiting to happen. On Base, cliffs deploy as part of the standard vesting setup — one parameter per recipient.
How long should total vesting run?
Three to four years total for founders and core team, two to three for early employees, one to two for advisors, and whatever the term sheet says for investors — typically one to two years with a shorter cliff. The principle underneath the numbers: vesting duration should roughly match the period over which each person's contribution is supposed to compound. Founders build for years, so they vest for years; an advisor's network introduction pays off in months. Schedules dramatically shorter than these bands are the red flag buyers actually check for — a team "vesting" over six months has scheduled its own exit, and Base's screener-literate market prices that immediately.
What release cadence should you pick?
Monthly release is the standard and the right default; daily or per-block release suits payroll-style contributor compensation; quarterly suits investors and treasuries. Cadence changes the texture of sell pressure more than its total: monthly unlocks create thirty-six small non-events across a three-year schedule, while quarterly unlocks create twelve visible ones that traders can front-run on chart platforms that track unlock calendars. Team Finance supports per-block, daily, weekly, monthly, and quarterly cadences on Base — and different recipients can run different cadences in the same deployment.
Which schedules read as red flags?
Buyers red-flag no cliff, sub-year totals, founder self-exemptions, and revocable investor contracts. Specifically: no cliff on team tokens means selling can start on day one. Total vesting under a year for founders signals a planned exit, not a project. The founder exception — everyone vests except one wallet — gets found on-chain every time, because on Base the vesting contract is public and the unvested wallets are visible next to it. Investors on terminable contracts reads as a lever to erase obligations. The common thread: the schedule is public information on Base, so design it as if it will be read — because it will. Pair the schedule with a hard lock on the founding allocation if you want the strongest combined signal.
FAQ
What's a reasonable schedule for a small Base team with no investors? A one-year cliff with two years of monthly linear release for founders, and six-month cliff with eighteen months linear for early contributors, covers the standard expectations without over-engineering.
Should investor and team schedules match? No — they answer different questions. Investors typically accept shorter totals with earlier liquidity; teams signal commitment with longer ones. What must match is disclosure: publish both.
Do unlock schedules affect price? Large scheduled unlocks are widely tracked and often front-run; monthly cadences and staggered tranches smooth this out. That's a market-behavior observation, not investment advice.
Can I benchmark against real data instead of taking your word? Yes, and you should: Team Finance's lockup analysis is linked above, and Sablier's 500k-stream dataset is public. The norms in this guide are those two sources plus standard practice as of August 2026 — re-check them before you finalize; norms drift.
Next steps: set up vesting on Base · team token locks · back to the Base hub
Base is developed by Coinbase. TrustSwap is not affiliated with, endorsed by, or sponsored by Coinbase, Inc. All product and company names are trademarks of their respective holders; their use here is for identification purposes only.
This article is for informational purposes only and is not financial advice. Facts current as of August 2026.