Ctrlk
Open Ticket
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Vesting

Long-form ALB vesting via the VestingFactory contract

Some ALB allocations — to the team, contributors, advisors, and certain DAO-budgeted recipients — are released over multi-year schedules through the on-chain VestingFactory instead of via direct distribution.

Last updated: July 6, 2026.

What it is

VestingFactory is a contract deployed by the team in June 2025 that creates per-recipient vesting contracts. Each per-recipient vesting contract holds an ALB allocation and releases it linearly over a configurable schedule.

This is distinct from the esALB locking system:

  • esALB is short-term, holder-controlled, instantly mintable from ALB, and unlocks in 30 days or 1%/24h.

  • Vesting is long-term, multi-year, and release schedules are fixed by the proposal that authorized them. The recipient cannot accelerate redemption.

The combination of the two ensures that long-tail contributor allocations reach circulating supply slowly while short-term holder behavior remains liquid via the esALB unlock paths.

Origin

The team-facing 5 M ALB from the original timelock (see ALB Token — Initial supply & distribution) was always intended to vest. At launch, the vesting infrastructure had not yet been built. VestingFactory is that deployed infrastructure.

AIP-3 (Oct 2024) and AIP-4 (Jun 2025) both authorized additional vested allocations:

  • AIP-3 transferred 66% of the previous dev-team emissions rights into vested positions for DAO contributors, devs, and potential external investors.

  • AIP-4 authorized esALB-style multi-year additional locks vesting over close to 5 years total since launch.

Which addresses receive vesting

Vesting recipients include (non-exhaustive):

  • Founding team members (the original 5 M ALB allocation).

  • Long-term core developers and operators.

  • Recipients of the AIP-3 / AIP-4 vested allocations.

The full list of recipient addresses is on-chain — every per-recipient vesting contract is created by VestingFactory (0x77ec0394…ed84, second deployment 0xf61cc1ae…453d) and is therefore visible on Basescan via the factory's contract-creation history.

How it interacts with circulating supply

ALB held in vesting contracts is non-circulating until released. The "circulating supply" figure on CoinGecko / DefiLlama / DexScreener excludes:

  • Tokens still in vesting contracts (not yet released to the recipient).

  • Tokens locked as esALB (locked, but technically held by the user — counted as circulating in some methodologies).

Per the latest analytics, ~234 M ALB is reported as circulating against ~465 M minted. The gap is split between vesting contracts, the DAO multisig & treasury addresses, the team operations Safe, and unvested farm-emission accumulator state.

See also

PreviousesLPNextReal Yield (WETH)

Last updated