Token Vesting
Pronunciation: TOH-kun VEH-sting
Definition
Token vesting is a schedule or condition that gradually grants recipients transferable ownership or claimability over tokens allocated to them.
Overview
How it works and why it matters
Vesting is a schedule that makes token rights economically or technically available over time. A contract can enforce release times, but an employment or investment agreement may govern rights even when tokens are held elsewhere. Evaluate cliff, start date, linear release rate, revocation powers and whether already vested tokens are immediately transferable.
Important technical and operational details
Vesting can use cliffs, linear release, milestones, performance, employment, governance, or smart-contract time locks and can apply to teams, investors, advisors, or communities. The process can change balances, supply, permissions, transferability, metadata, or future rights. The initiating authority, required approvals, timing, and reversibility determine whether the action is ordinary user behavior or a privileged administrative event.
Vested allocation, unlocked tokens, claimed tokens, and tokens actually sold are different states that should not be combined. Token Vesting should be tied to an exact asset, network, contract or mint, and implementation version. similar names can describe different mechanics, such as reducing total supply versus sending tokens to an inaccessible address.
Risks include hidden side agreements, revocable grants, contract bugs, accelerated release, governance changes, custody loss, insider concentration, and market unlock shocks. Risks include compromised authority, hidden or unlimited permissions, incorrect decimals, reentrancy or callback behavior, duplicated cross-chain supply, failed migrations, misleading event interpretation, and governance actions that alter prior assumptions.
Systems should record beneficiary, total grant, cliff, schedule, claimed amount, revocation, acceleration, contract, voting rights, transfer, and remaining locked balance. payment and custody systems should simulate or test unusual token behavior before support, including transfer fees, pauses, allowlists, rebases, callbacks, and upgradeable implementations. Exceptions need explicit reconciliation and refund rules.
Related concepts
Token Distribution; Token Claim
Further reading
Example
A contributor receives an allocation of 12,000 tokens with a 12-month cliff and monthly vesting thereafter. The interface may show the whole allocation on day one, yet only a fraction becomes claimable at each release. A merchant should not count unvested allocation as instantly liquid treasury funds.
Comparison
Vesting differs from a token lock: a lock restricts transfers, while vesting often determines when entitlement accrues. Check who controls the contract and what happens on termination or migration.
Key Takeaway
Displayed token allocations are not necessarily vested, claimable, or liquid.
Sources
- Ethereum ERC Standards — Ethereum Foundation (2026-08-01)
- Ethereum Documentation: Smart Contracts — Ethereum Foundation (2026-08-01)