A Vesting Schedule Is a Confession. Most Founders Won't Make It.

You can skip the whitepaper. The vesting schedule already told you whether the team believes its own pitch.

A roadmap is aspiration and a pitch deck is marketing. A vesting schedule is something else: a dated, on-chain statement of how long the people who built the thing intend to stay financially tied to it, and how much of their own upside they're willing to defer to prove it. Everything else a project publishes is what it wants you to think. The schedule is what it's actually willing to commit to.

Which is exactly why so few teams publish an honest one.

The schedule is the one part of the pitch that can't be spun

There's a rough consensus on what a serious schedule looks like. Industry guidance treats roughly four years total — a twelve-month cliff followed by a three-year linear release — as the standard for founders, with early investors on two to three years. The same guidance is blunt about the tell: insider vesting shorter than a year should make you ask what the team knows that you don't.

A vesting schedule encodes a time horizon, and a time horizon is a belief. A team that locks itself for four years is saying it expects to still be here, still building, in 2030. A team that takes a six-month cliff is saying something quieter and more honest than any of its marketing: we'd like the option to be gone by the new year.

A short cliff is a sentence with a date on it

The market has learned to read these documents as confessions, and to price them before the confession comes due. Markets routinely anticipate large unlocks and reprice a token downward ahead of the date, especially when the unlocking allocation is large relative to the float and was bought at a steep discount.

Look at the overhang sitting on real projects right now. As of May 2026, roughly 40% of SUI's supply had unlocked, with the rest scheduled out to 2030 and a multi-year insider cliff only now completing — against a fully diluted valuation north of $10 billion and a market cap around a third of that. That gap between the two numbers is the confession written in advance: most of the value is still locked, still going to land on somebody eventually. Multiply that across the market and the scale gets heavy. Binance Research has estimated something like $155 billion in token unlocks arriving between 2024 and 2030. All of it is somebody's vesting schedule coming due.

Disclosed is not the same as honest

Here's the move sophisticated teams make. They disclose everything — every allocation and every date, fully transparent — and still structure the thing to dump on you. Front-loaded releases. A chunky insider cliff three months after listing. Disclosure satisfies the letter of trust while the structure quietly violates the spirit, and a holder who only checked whether the schedule was published walks straight into it.

So transparency alone isn't the test. Enforcement is. A schedule the team can amend after the raise is a suggestion. The only version worth believing is the one deployed as code the team can't reach — which is the layer Team Finance exists to provide: vesting and locks written on-chain before the token goes live, checkable by anyone and revocable by no one. A promise you can verify and the founder can't edit is worth more than a paragraph of stated intentions.

The honest objection: time-based vesting is a blunt instrument

Argue the other side, because the critique is sharp.

Time-based schedules are crude. They release supply on a calendar regardless of whether the protocol generated any demand to absorb it, which is how you get tokens unlocking into a market that doesn't want them. Some argue the cleaner design is demand-driven emission — releasing tokens only when usage actually calls for them — so supply and the community's interests stay aligned. There's a fairness cost too: long lockups can trap good teams in illiquid positions through bad cycles, a real opportunity cost that pushes some builders toward shorter, more flexible terms. Both points land.

But notice what they're really arguing for: more discretion over how supply releases. And discretion is exactly the thing that gets abused. A blunt schedule the team can't touch beats an elegant one the team controls, because the failure mode of crypto was never that vesting was too rigid. It was that someone changed the rules once the money was already in.

Read the math before you read the mission

A team's stated mission costs nothing to write. Its vesting schedule costs it years of liquidity and optionality, which is why the schedule, not the mission, is where you find out what the team actually believes.

So next time a project walks you through its vision, nod politely, then go pull the unlock calendar. If the founders front-loaded their own exit, they already told you how the story ends. The only question left is whether you were listening when they confessed.