Skip to main content
Same contracts on Base and Robinhood Chain.

Dev-buy vesting

The dev buy can go into a vesting vault instead of the creator’s wallet. The schedule is public on-chain from the launch transaction, so every buyer can read what is locked and until when.
A vested dev buy is uncapped by design. The 10% cap protected buyers from an undisclosed large position; the vault replaces it with a disclosed one. The launcher refuses vesting without a dev buy (VestRequiresDevBuy).

The vault’s rules

Dividends while locked

Locked tokens still earn holder rewards. Two one-way doors end that stream: Everything is public state on the vault: each schedule’s total, released, start, cliff and duration; what a release would send now; whether the stream is gone. The factory’s vaultOf(token) is address(0) when the dev buy was not vested.

Who controls the page

LaunchControl is the registry of who controls each token’s page - artwork, description, links. The creator holds the seat by default.

Handing over

The controller can transfer the seat directly on-chain, or sign a handover that anyone submits for them - it names token, recipient and expiry, fits one transfer, and cannot be replayed.

Community takeover

When a founder is gone, the platform can propose a new controller. It cannot execute one.
1

Propose

The platform names the new controller. A 7-day clock starts, on-chain.
2

Veto window

At any point in the 7 days the current controller can cancel. A founder who is present cannot be removed; this only completes against silence.
3

Execute

After 7 days, anyone can complete it. The seat moves, and the founder’s vault stops earning dividends in the same transaction.
The delay plus the veto is the design. A takeover the platform could execute instantly would make the platform the real controller of every token.