If a project's whitepaper says “the team holds 20% and it will be released linearly over 2 years,” how credible is that? In Web3, such promises carry almost no real constraint. True token locking must be enforced by smart contracts.
What is a Vesting Contract?
A standard token vesting contract (Vesting Vault) is quite simple. It only needs to define four things:
- →Beneficiary: Who receives the tokens — e.g., a team wallet or investor address.
- →Start (TGE): When the vesting clock begins — usually the Token Generation Event date.
- →Cliff: A lock-up period during which nothing can be claimed. Before the cliff ends, the claimable amount is always zero.
- →Duration: Total time from start until the tokens are fully vested. After this point, 100% is claimable.
Once deployed, tokens are transferred into the contract. The beneficiary can only call release() according to the contract rules. No one — including the project team — can move the funds early.
Example Timeline
From August 31 onward, tokens unlock continuously — every second a small portion becomes claimable — until everything is fully released by January 28. This entire process is calculated automatically by the contract, with zero human intervention.
Why Does This Matter?
From an investor's perspective, on-chain vesting means:
- ✓The rules are transparent and verifiable on-chain — no need to trust anyone.
- ✓You can calculate exactly when team tokens will enter the market, and model the sell pressure accordingly.
- ✓A project with verifiable on-chain vesting is objectively more credible than one with only a whitepaper promise.
From the project team's perspective, on-chain vesting is a credible commitment — it significantly increases investor and community confidence.