Unlock Schedule

An unlock schedule is a timeline that defines when locked or restricted tokens become transferable, claimable, or otherwise available to recipients. It commonly applies to founders, employees, investors, advisers, treasuries, and incentive programs. The schedule controls access to existing allocations, while vesting may separately determine when a recipient earns them.

A common structure uses a cliff followed by gradual release. A four-year employee grant might unlock nothing during the first year, then release 25 percent at the cliff and the remainder monthly. Investor tokens may unlock in fixed quarterly amounts. Network rewards can follow block or epoch schedules. Exact timing, rounding, and start conditions affect the quantity released.

Unlocks matter because they change potential market supply and holder control. A large release relative to normal trading depth can create selling pressure, although recipients may choose not to sell. Markets often anticipate public schedules. Price impact depends on valuation, liquidity, recipient cost basis, hedges, demand, staking opportunities, and whether earlier holders already transferred economic exposure through derivatives or private agreements.

Technical enforcement varies. A vesting contract may release tokens automatically or allow claims after timestamps. A multisignature treasury may distribute them manually. Some restrictions exist only in legal agreements even though recipients already control the wallet. Administrators may have acceleration, revocation, pause, or upgrade powers. A published chart does not prove that on-chain behavior matches it.

Common mistakes include confusing vesting with unlocking, adding all allocations to one date, ignoring time zones and block variability, or assuming every unlocked token immediately circulates. Token migrations and governance changes can revise schedules. Staked or delegated locked tokens may still earn rewards or vote, creating economic influence before transferability.

To evaluate a schedule, map each allocation, beneficiary type, start event, cliff, frequency, amount, contract, and administrator. Compare upcoming releases with circulating supply and real volume, then monitor actual wallets. Projects should publish machine-readable schedules and reconcile planned versus completed unlocks. Complete archived historical versions should remain publicly and permanently available so changes cannot quietly replace earlier commitments. Transparent timing helps users model dilution, but holder behavior, delegation, staking, and enforcement determine the real market effect.