Team ETH Vesting

Team compensation never becomes claimable on arrival. Every deposit into a launch's TeamDistribution contract enters a rolling linear vesting schedule and vests over a fixed six months. The parameter is immutable and identical for every launch.

Vesting exists for one reason: without it, a large early liquidation — precisely when speculative demand peaks — could hand the team its maximum compensation immediately, after which nothing economic binds them to the project. The schedule converts team compensation from an event into a stream, so being paid and staying engaged are the same thing.

The rolling schedule

Deposits arrive continuously — the team share of each liquidation, and on $PURE's instance the team half of processed ecosystem contributions (the launch's Treasury and, for $PURE, the EcosystemReceiver are the only two addresses that can ever deposit). Each deposit is recorded as a tranche stamped with its arrival epoch, and each tranche vests independently:

vested(tranche) = amount × min(1, elapsed / vestingPeriodSec)

with vestingPeriodSec = 15,768,000 (six months). The team's claimable total at any moment is the sum of the vested portions across all tranches. Deposits landing within the same hour consolidate into one tranche, and fully-vested tranches merge into a settled balance, so the schedule stays compact however long the launch runs.

The result is a continuously rolling position: at any given time some compensation is claimable, more is vesting, and new liquidations keep adding tranches at the back of the queue.

Claiming

The team claims by pulling: claim(amount), callable only by the launch's designated team address, any amount up to the vested total, whenever it likes. Claims deduct from the oldest value first (FIFO), and the payout unwraps to native ETH at the transfer. No one else can trigger, redirect, or intercept a team claim — and nothing is ever pushed to the team's address automatically.

At shutdown

The vesting schedule resolves in one of two ways, depending on the shutdown mode the arbitrator determines:

No-Traction — the project failed to find traction, but the team remained engaged. Vesting accelerates: the contract's full balance (including the team's share of the shutdown pot, deposited moments earlier) becomes immediately claimable. The rationale is simple — vesting exists to bind compensation to a live project, and there is no longer a live project to bind to. The team still pulls its balance via claim; nothing is transferred automatically, and whatever goes unclaimed after the one-year window is handled by the sweep rules in Shutdown & Capital Resolution.

Abandonment — the team walked away. The contract's entire remaining balance is clawed back to the Treasury and every tranche is zeroed. There is no partial vesting, no grace period, and no distinction between vested-but-unclaimed and unvested — the team forfeits everything it had not already claimed. The clawed-back value joins the shutdown pot, where supporters receive their share and token holders absorb what would have been the team's.

What vesting does not touch

Vesting governs when team compensation becomes claimable — nothing more. The team's share of each liquidation is unchanged by it, the market-making engine is entirely unaware of it, and supporter and holder flows live in different contracts it cannot reach.