Buybacks & vesting

Buybacks allocate part of the creator-side fee remainder toward buying the launch token. They are optional and do not create an additional trader fee. Fee allocation shows the current split.

Funding and execution

Fees earmarked for buybacks accumulate as quote in the vault. pendingQuote(token) is available funding; it is not a record of a completed purchase.

executeBuyback(token, quoteAmount, minTokensOut) is owner-only. The minimum output must be non-zero. The current internal price-impact cap is 300 basis points (3%). Execution can be capped, partially filled, or revert if it cannot satisfy the checks. Unspent quote remains pending where the execution path returns it; a failed transaction does not prove a buyback happened.

There is no promise of a buyback on every trade or at a fixed interval. The contract permissions and the operator’s execution schedule are separate matters.

Purchased tokens vest; they are not burned

Bought-back tokens are held in the vault and released over five years (5 × 365 days). On a later purchase, already vested value is preserved and the remaining unvested balance is combined with the new purchase on a fresh vesting line. A new buyback cannot inherit all the elapsed time of an old one.

releasable(token) returns the currently vested, unreleased amount. A release splits tokens using the launch’s snapshotted protocol share: at the current split, 30% protocol and 70% current fee recipient.

Who can release?

The current fee recipient, treasury, or vault owner may call release(token). It pays both sides. Releases are paused during an executable takeover window to prevent the outgoing recipient from draining a matured allocation ahead of a takeover.

Who controls the preference?

The current fee recipient may enable or disable buybacks. The launchpad owner may disable them but cannot force-enable them using that owner privilege. A toggle does not undo prior trades or erase vested positions.