Token Vesting Schedule Explained: Cliffs, Streams, Unlocks

A token vesting schedule is a timetable that releases tokens gradually instead of all at once. Contracts enforce it, so the team or treasury cannot sell everything on day one. The key questions are how long, how fast, who controls the contract and what happens when tokens unlock.

Why vesting exists

Without vesting, an insider with a large allocation could sell immediately after launch. Schedules align incentives by tying access to time. They also let outside buyers estimate how much supply can reach the market in a given period. That estimate is only as good as the contract: a schedule that an owner can pause, shorten or redirect is a promise, not a rule.

The common shapes

Shape	How it releases	Typical use
Cliff	Nothing until a date, then a lump	Team and advisors
Linear stream	Equal amounts per block, day, week or month	Treasury, rewards
Cliff then linear	Wait, then stream	Team allocations
Immediate	All at launch	Presale buyers
Milestone-based	Unlock on events	Grants, ecosystem funds

Reading BC1’s schedule

The Bitcoin.one whitepaper uses three of these.

Presale (40%): immediate. Everything is claimable at the token generation event. See the presale explained.

Treasury (30%, 6.3 billion BC1): linear and weekly. A WeeklyVesting contract has 52 unlocks of about 121.15 million BC1 starting at TGE. The paper says the start time, number of weeks and total are immutable, with no owner, pause or redirect, and that only the beneficiary can change the beneficiary address.

Ecosystem (15%, 3.15 billion BC1): streamed over 36 months, about 87.5 million per month, for staking, cashback and referrals.

Liquidity (15%): not vested but locked. The LP position is locked for 12 months.

Check the maths: 6.3 billion divided by 52 is about 121.15 million, and 3.15 billion divided by 36 is 87.5 million, so the paper’s figures reconcile. For all four buckets together, see BC1 tokenomics.

What “no admin functions” does and does not mean

Removing owner controls from a vesting contract is good design: nobody can accelerate or cancel the schedule. But it covers only that contract. It says nothing about what the beneficiary does after receiving tokens. The paper does not state who the beneficiary is or what the treasury will do with unlocked BC1, so you cannot tell from the schedule alone whether unlocked tokens will be held, spent on operations or sold.

Key takeaway: a trustless unlock tells you when tokens become movable. It never tells you what the holder will do next, so model both cases.

Stacking the schedules

Vesting matters most when schedules overlap. Combine presale claims at TGE with the first treasury unlock, the first ecosystem stream and newly paired liquidity, and the number of tokens that can move in week one is much larger than in later weeks. The paper gives no circulating-supply number at launch, so you have to build your own scenario from the buckets. A simple method:

1. List each bucket and its release rule.
2. Compute the maximum tokens movable at week 1, month 1, month 6 and month 12.
3. Compare each total with plausible demand, using conservative assumptions.
4. Repeat with the assumption that unlocked tokens are sold.

Checking a vesting contract yourself

• Find the contract address in the official documentation and confirm it on a block explorer.
• Verify the source code is published and matches.
• Look for functions such as pause, revoke, setBeneficiary and upgrade.
• Confirm the start time and total are fixed, not variable.
• Check whether the contract holds the tokens, or only promises to.

Our whitepaper reading method explains how to cross-check such claims. The paper also notes treasury keys sit on hardware wallets and that owners of admin contracts use a two-step ownership transfer, which are operational controls worth confirming rather than assuming.

Risks to keep in view

Concentration is the obvious one: the paper’s own risk section lists the 30% treasury and team-held owner keys. Another is timing: schedules begin at TGE, which the paper targets for Q1 2027, and targets can slip. Finally, the project’s risk disclosure states that buybacks are not a price floor and that you may lose everything you spend.

Vesting is a tool for transparency, not a guarantee. Nothing here is investment advice.

Worked example: what the first year looks like

Use the paper’s numbers to see what vesting does to supply over twelve months. These are arithmetic illustrations, not forecasts.

Time after TGE	Treasury unlocked (approx.)	Ecosystem streamed (approx.)	Presale
Week 1	121M	about 20M	8.4B claimable
Month 1 (about 4 weeks)	485M	87.5M	8.4B
Month 6	about 3.15B	525M	8.4B
Month 12	6.3B (fully unlocked after 52 weeks)	1.05B	8.4B

Notice that the treasury is fully unlocked in about a year, while the ecosystem stream is only a third complete. Also notice how little the weekly numbers change the picture relative to the 8.4 billion presale, which is available from day one. The liquidity lock expires at 12 months, which means the LP position becomes movable at the same time as the treasury finishes unlocking. Those coincident dates are worth marking on a calendar.

Practical reading tips

• Read the vesting contract’s constructor parameters, not just the documentation.
• Check whether time is measured in blocks or timestamps.
• Check who the beneficiary is and whether it is a multisig or a single key.
• Look for a public dashboard of unlocks, so you do not need to compute them manually.

For how these buckets fit the full supply picture, see BC1 tokenomics, and for the project’s own statement on concentration, see its risk disclosure, which lists the 30% treasury and team-held owner keys. A third document, the whitepaper, gives the contract-level description.

Vesting versus locking: a distinction that gets blurred

People often use “locked” and “vested” interchangeably, but they protect against different things. Vesting releases a holder’s own allocation over time. Locking removes the ability to withdraw liquidity from a pool for a period. BC1’s liquidity is locked for 12 months, which stops the pool being drained early, but it does not restrict anyone’s tokens from being sold into the pool. The treasury, by contrast, is vested: the tokens exist in a contract and flow out on a schedule, yet once released they can be sold into the same pool.

The two protections cover different failure modes. A liquidity lock addresses a “rug pull” where the pool is emptied. Vesting addresses a dump from an insider allocation. Neither addresses a slow, steady sale from released tokens, which is why the treasury’s intentions matter. Ask whether the project publishes a treasury policy, and whether releases are reported publicly. The paper does not describe either.

A reader’s checklist for vesting claims

1. Is the schedule enforced by a contract, or only described in a document?
2. Are the parameters immutable, as the paper says for WeeklyVesting?
3. Who is the beneficiary, and can that address change?
4. Is there a published dashboard of unlocked and claimed amounts?
5. Do other schedules, such as presale claims and ecosystem streams, overlap?
6. When do locks, such as the 12-month liquidity lock, expire relative to unlocks?

Answering these gives you a calendar rather than a slogan, and a calendar is something you can plan around.