Launch lock
Hold a launch's liquidity in its pools until a block you pick, or for good, while a beneficiary collects every fee it earns.
On this page
You hand the launch to the lock and name a beneficiary, and the lock takes every pool of the launch at once, every pool of a Multi-pool launch included.
What you set
| Setting | What it takes |
|---|---|
| Beneficiary | Any account that can make calls, such as a wallet or a Safe. Never the lock, the launcher or the PoolManager. |
| Unlock block | Any future parent block, about 12 seconds each, or forever. |
| Fees | None. The lock takes nothing, and the pools keep the Hook Blocks set at launch. |
Only the liquidity owner can lock it. The owner first hands the launch to the lock, then locks it in one more call.
While it is locked
- Nobody can withdraw the liquidity or add more, and nobody can move the launch.
- Only the beneficiary acts. It collects every fee the locked liquidity earns, and on a pool with arbitrage recapture it moves the LP share as well (
claimRecapture). - The beneficiary cannot be changed.
- The token's supply is not locked: the lock holds liquidity, not tokens in wallets.
When it unlocks
From the unlock block the beneficiary can hand the launch to a new owner (release). The fees earned until then go to the beneficiary in the same call, and the new owner accepts the launch in a second step. A lock set forever never releases.
Next to the dev buy lock
The dev buy lock is set inside the launch and ends on its own block. The launch lock is a separate step after launch, by the liquidity owner, and can last for good. A launch can have both: the dev buy lock holds the liquidity until its end whatever the launch lock says.
In the app
Once a launch lands, the app's next step is to lock it for good. For good is picked, and your wallet is the beneficiary unless you name another account. Locking takes two signatures: the first hands the launch to the lock, and the second locks it. Until a date locks it for the days you enter instead, and Keep it unlocked skips the step. The pool's Liquidity tab can lock it later.
Pool pages, token pages and Discover tag a launch only when its liquidity is locked: locked for good, or locked until a date. A launch that is not locked, whose lock has ended, or whose lock could not be read carries no tag. Each reads the lock from the chain.
For integrations
Anyone can check a lock on chain: lockOf(familyId) returns the beneficiary and the unlock block, and the lock logs FamilyLocked when it locks and FamilyReleased when it releases. Explorers, screeners and wallets can show the liquidity as locked from the chain itself. A contract can be the beneficiary if it can call collect, and fees can also come out as PoolManager claims.