Liquidity Mining Reward Vesting Schedules Explained
A vesting schedule controls when earned liquidity mining rewards become claimable. It changes the timing and risk of the reward, not the pool fees or the calculation of how much a position earns.
Vesting starts after rewards are earned
A liquidity mining program first measures eligible liquidity over time and calculates a reward entitlement; a vesting rule then delays some or all of that entitlement. These are separate mechanisms: a position can stop earning when it leaves a qualifying pool or range, while rewards already accrued continue vesting under their own schedule.
On Avalanche C-Chain, someone comparing pools before providing liquidity can use how to use Blackhole swap as context for the swap-and-liquidity side of the decision. A mining campaign is an additional incentive layer, with its own eligibility rules and reward contract; the presence of a pool on a DEX does not itself mean it has a vesting program.
Common schedules release rewards immediately, linearly over time, or through a cliff followed by linear release. A cliff is the first date any amount can be claimed; a 30-day cliff with a 90-day total duration might release nothing for 30 days, then vest the balance over the following 60. Campaigns vary widely: a few weeks to several months is a useful range to encounter, not a protocol standard.
The contract’s clock and claim rules determine the real lock
For a simple linear schedule, let R be a user’s accrued reward, t₀ the vesting start, T the duration, and t the current time. After any cliff, the vested amount is generally R × min((t − t₀) / T, 1); claimable tokens equal vested amount minus tokens already claimed. Actual contracts may round down to token units or release at fixed epochs rather than continuously.
Check what event starts the clock. It may be each reward accrual, the end of the campaign, or the user’s claim; those produce different outcomes when rewards accrue daily. In a per-epoch design, each tranche can have its own start and end, so claiming late may leave several overlapping schedules. The contract may also require a separate claim call, and “vested” does not always mean automatically transferred.
Think of each reward tranche as a paycheck placed in escrow: the amount can be earned today, but the release date is set by the contract. The edge case to check is an early exit: some programs preserve already earned rewards and keep vesting them, while others require the LP position to remain deposited until a checkpoint or campaign end. A transferable position can add another wrinkle: verify whether its reward entitlement follows the position or stays with the original wallet.
Compare unlocked value, not headline APR
To compare campaigns, estimate both the reward allocation and when it becomes liquid. If a position earns 1,200 illustrative tokens over 30 days and they vest evenly for 90 days from campaign end, only 400 are unlocked 30 days later, 800 by day 60, and all 1,200 by day 90. A quoted APR based on all 1,200 at today’s token price overstates usable proceeds if the token price falls before release.
Then compare the vesting cost with the position’s risks: price exposure, impermanent loss, time out of range, and the opportunity cost of locked rewards. Confirm the schedule’s start event, cliff, duration, claim cadence, exit treatment, and whether the stated allocation is guaranteed or depends on eligible liquidity share. For rewards on AVAX pairs, include the possibility that the reward asset and the pool assets move differently during the lock.
Before acting, ask yourself: would this position still make sense if the locked rewards were worth less—or unavailable—until the final vesting date?