An allocation tells you how much. Vesting tells you when.

MUTERRA can use vesting where an allocation is intended to support long-term participation rather than create one immediate distribution.

Vesting can make supply releases more predictable. It does not remove market risk or guarantee price stability.

These four numbers can be different at the same time. A holder interface should show the source programme, next unlock and remaining locked amount.

Founder distributions, creator grants and other rewards can use different release patterns. A small event reward can be immediate; a larger strategic grant can unlock gradually.

The schedule attached to the specific allocation is the source of truth and must be published before or when the allocation becomes binding.

Ticket Weight and vesting solve different problems. Weight can calculate the size of a proportional allocation; vesting controls when that allocation becomes available.

If a Ticket class affects vesting, the programme must state that explicitly.

A snapshot can determine which Ticket or wallet was eligible at one moment. The resulting allocation can vest later.

A programme must state whether an unvested amount stays with the snapshot wallet, follows the Ticket or uses another recorded claim right. Users should not have to guess.

Some allocations may be delivered automatically. Others can require a claim transaction, a window, identity checks or a network fee.

Any deadline, grace process and handling of unclaimed tokens belongs in the specific programme rules.

Vesting does not guarantee a market price, liquidity, a fixed return, identical terms for every participant or a buyer after unlock.

The allocation source says how much. Vesting says when. The claim mechanism says how it arrives. The market decides what it is worth.