How DEVLOCK works
A launchpad on Raydium LaunchLab where the creator's own allocation is held by a program until the market, not the creator, opens it.
A launch is a single instruction, initialize_vested_launch, signed once by the creator. Inside it the program creates the SPL mint with its metadata, opens a Raydium LaunchLab bonding curve, performs the dev buy on that curve and transfers the chosen share of the bought tokens into an escrow token account owned by a program address. The remaining share goes to the creator's wallet.
Because all of this is one atomic transaction, there is no block in which the dev allocation is liquid, and nobody can buy ahead of the dev buy. The token is a plain SPL token: 1,000,000,000 supply, 6 decimals, no mint authority, no freeze authority, no transfer tax, no hooks.
The creator chooses three things, all immutable after launch: the locked share of the dev buy, the cliff rule and the unlock duration.
Nothing can be claimed until the cliff condition is met. There are two types.
- Volume target. The escrow opens when the bonding curve has traded a cumulative volume in SOL chosen by the creator. Volume is measured from the curve's own reserves, so trades made through any interface count: this site, Raydium, Axiom or a bot. The dev buy itself is excluded. If the curve migrates before the target is reached, migration opens the cliff instead.
- Migration. The escrow opens only when the curve is filled and its liquidity moves to a Raydium CPMM pool.
An optional delay (for example 24 hours) can be added between the cliff and the first unlocked token.
After the cliff and the delay, tokens unlock in proportion to elapsed slots over the chosen duration. At any slot the claimable amount is locked * elapsed / duration - already claimed, computed on-chain with 128-bit checked arithmetic.
Only the creator wallet recorded at launch can call claim_creator_vested, and the tokens can only go to that wallet. Each claim emits an event; the token page lists every claim with a link to its transaction.
The swap widget calls routed_swap. The program reads the pool status and sends the order to the LaunchLab curve before migration and to the Raydium CPMM pool after it, with the slippage limit enforced on-chain.
- Curve trades pay 4.00% in total, the same from this site and from any other interface: 0.25% Raydium protocol, 3.50% platform, 0.25% token creator. The fee is charged by the LaunchLab pool itself.
- No extra router fee is added on top for trades made through this site.
- After migration the Raydium CPMM pool fee applies: 0.25% trading fee plus 0.05% to the token creator.
Tokens launched here are standard LaunchLab pools, so they can also be traded directly on Raydium and on terminals that index LaunchLab.
When the curve has raised its target, Raydium migrates the liquidity to a CPMM pool. The platform configuration burns 100% of the LP tokens: the liquidity cannot be withdrawn by the creator or by the platform.
Everything shown on a token page is read from these accounts and can be checked independently.
PoolVestingState- PDA["pool_vesting", mint]: creator, locked amount, claimed amount, cliff rule, volume counter.CreatorVestingVault- PDA["vesting_vault", mint]: the token account that holds the locked tokens. Its authority is the vesting state PDA, not a wallet.
- The lock covers the dev buy made in the launch transaction. It does not stop anyone, including the creator, from buying on the curve later with another wallet.
- A volume target measures traded volume, not unique buyers. Volume can be generated at the cost of trading fees; a migration cliff is the stricter rule.
- The program is upgradeable by its authority. Check the program page for the current authority before relying on a lock.
- A locked dev allocation is a signal about the creator's incentives. It is not a guarantee about the price of a token.