DLMM Launch Pool is a special pool type designed for new token launches. It is based on DLMM and comes fundamentally equipped with a feature set that makes it optimal for bootstrapping liquidity for new tokens and making the tokens accessible on Jupiter and other trading integrations. DLMM Launch Pools can also be created with an Alpha Vault as part of the token launch process. This is optional. Alpha Vault is a new anti-bot tool to guard against sniper bots and allow genuine supporters to be the first to buy tokens at launch. Below we provide the steps to use Bun to configure and run sample scripts to conveniently set up a DLMM Launch Pool with Alpha Vault on your own.

​
Getting Started

​
Dependencies

Install Bun: You’ll also need bun to run the scripts. Install it via bun installation. Then install the dependencies by running the command bun install

​
Scripts

The following code examples can be used to initialize and seed a DLMM liquidity pool on Meteora using a customizable permissionless liquidity bin pair (LB pair). It allows you to configure parameters for the pool, including fees, pricing, curvature, and activation conditions, before executing initialization and seeding commands. We also have code examples for interacting with the Alpha Vault program. Use these examples to create and manage vaults, handle deposits and withdrawals, manage permissioned and permissionless vault configurations, and interact with escrow accounts.

​
Create DLMM Launch Pool

Clone repo: https://github.com/MeteoraAg/meteora-pool-setup Select an example config to reference and change the parameters inside according to your needs: https://github.com/MeteoraAg/meteora-pool-setup/tree/main/config Run the script with the config file which is updated with your preferred parameters. For example, run: 
bun run src/create_pool.ts --config ./config/create_dlmm_pool.json
Replace ./config/create_dlmm_pool.json with the path to your config file, after you have set your config parameters. Important Notes:
  • The max bin step you can set for a DLMM pool is 400 bin step.
  • When creating a DLMM pool, there are 3 roles in position that you can config:
    • Position Owner: Wallet that owns the liquidity
    • Operator: Wallet that can deposit and withdraw tokens on behalf of the Position Owner
    • Fee Owner: Wallet that gets the fees from that position
  • During the initialization of the DLMM pool, pool creator needs to have at least 1 lamport worth of the base token in the wallet to prove ownership.
  • If you plan to use a multisig on the Meteora website, please make sure it is the SquadsX multisig, as that is the only type supported on Meteora website. Otherwise, you can’t manage liquidity through the website.

​
Seed liquidity

There are two different strategy options when it comes to seeding liquidity in a DLMM Launch Pool.

​
Seed liquidity using ilm curve distribution strategy

This is the standard type of token launch liquidity distribution used by past LFG projects such as JUP, WEN, CLOUD etc. You can first use this ilm curve tool to determine the suitable parameters for your launch. Reference this config file https://github.com/MeteoraAg/meteora-pool-setup/blob/main/config/seed_liquidity_lfg.json and set your preferred parameters. Run the script with the config file which is set with your preferred parameters. For example, run: 
bun run src/seed_liquidity_lfg.ts --config ./config/seed_liquidity_lfg.json
Replace ./config/seed_liquidity_lfg.json with the path to your config file, after you have set your config parameters.

​
Seed liquidity using single bin strategy

This is a unique token launch strategy where all liquidity is allocated into a single bin. Reference this config file https://github.com/MeteoraAg/meteora-pool-setup/blob/main/config/seed_liquidity_single_bin.json and set your preferred parameters. Run the script with the config file which is set with your preferred parameters. For example, run: 
bun run src/seed_liquidity_single_bin.ts --config ./config/seed_liquidity_single_bin.json
Replace ./config/seed_liquidity_single_bin.json with the path to your config file, after you have set your config parameters. Important Notes:
  • When seeding liquidity using the endpoint, both Operator and Position Owner need to have base tokens to prove ownership. If the Position Owner doesn’t have any base tokens, then the Operator will need to send 1 lamport worth of the base token to Position Owner. But the script will check if Position Owner has tokens and if not, it will bundle a transfer instruction to send 1 lamport worth of the base token from the Operator to the Position Owner.
  • In the code example, lock_release_point refers to the time the liquidity position can be withdrawn. If it is set to zero, it means the position can be withdrawn immediately after trading starts.
  • If you plan to use a multisig on the Meteora website, please make sure it is the SquadsX multisig, as that is the only type supported on Meteora website. Otherwise, you can’t manage liquidity through the website.

​
Set DLMM Launch Pool status

You are able to disable the pool prior to pool activation time (before trading starts) and enable it later before or after pool activation time. After pool activation time, once enabled the pool cannot be disabled by you again. Reference this config file https://github.com/MeteoraAg/meteora-pool-setup/blob/main/config/set_dlmm_pool_status.json and set your preferred parameters. Run the script with the config file which is set with your preferred parameters. For example, run: 
bun run src/set_dlmm_pool_status.ts --config ./config/set_dlmm_pool_status.json
Replace ./config/set_dlmm_pool_status.json with the path to your config file, after you have set your config parameters.

​
Create Alpha Vault

​
DLMM Launch Pool with Alpha Vault Pro Rata mode

Reference this example config: https://github.com/MeteoraAg/meteora-pool-setup/blob/main/config/create_dlmm_pool_with_prorata_alpha_vault.json Change the parameters in the config according to your needs. Run the config after it has been updated with your parameters: 
bun run src/create_alpha_vault.ts --config ./config/create_dlmm_pool_with_prorata_alpha_vault.json

​
DLMM Launch Pool with Alpha Vault FCFS (First Come First Served) mode

Reference this example config: https://github.com/MeteoraAg/meteora-pool-setup/blob/main/config/create_dlmm_pool_with_fcfs_alpha_vault.json Change the parameters in the config according to your needs. Run the config after it has been updated with your parameters: 
bun run src/create_alpha_vault.ts --config ./config/create_dlmm_pool_with_fcfs_alpha_vault.json

​
DLMM Launch Pool with Alpha Vault Pro Rata mode (with Whitelist)

Reference this example config: https://github.com/MeteoraAg/meteora-pool-setup/blob/main/config/create_dlmm_pool_with_prorata_alpha_vault.json Change the parameters in the config according to your needs. Use: 
"whitelistMode": "permissioned_with_authority"
"whitelistFilepath": "./config/whitelist_wallet.csv"
Replace ./config/whitelist_wallet.csv with your csv file containing your list of whitelisted addresses. Run the config after it has been updated with your parameters: 
bun run src/create_alpha_vault.ts --config ./config/create_dlmm_pool_with_prorata_alpha_vault.json

​
Alpha Vault with Whitelist

For some launches, the project may want to restrict which wallet addresses are allowed to deposit funds into the Alpha Vault, so in the config file used in the script to create the Alpha Vault, the whitelistMode needs to be specified.
  • permissionless: No whitelist, anyone can deposit into the Alpha Vault
  • permission_with_authority: In this mode, only the Alpha Vault creator can create escrow account with max_cap. This allows the creator to use a permissioned (with whitelist) setup without having to use the merkle tree. Creator needs to pay SOL rent for each escrow account for the whitelisted wallets, so this Alpha Vault whitelist mode is suitable for scenarios where there are very few whitelisted addresses (e.g. =<100). If they need to support a lot more whitelisted addresses, they should still use the merkle tree (PermissionWithMerkleProof whitelist mode).
  • permission_with_merkle_proof: In this mode, only wallets that are whitelisted can deposit into the Alpha Vault. Csv file containing the list of whitelisted wallets needs to be provided by the project to Meteora, for the Merkle proof to be hosted by Meteora and shown on the UI. Alpha Vault deposits should not open until the Merkle proof is hosted by Meteora.
Important Notes:
  • If you do not want to use Alpha Vault, skip this step.
  • Currently, only SOL or USDC is accepted as the quote token when initializing a Dynamic AMM or DLMM Pool with Alpha Vault in a permissionless setup. Since the Alpha Vault can’t tell what the quote token would be, the quote token is limited to SOL or USDC. However, any quote token can be used if you use a config key that doesn’t have Alpha Vault.
  • There must be a ~1 hour 5 minutes period between the deposit close time and the pool activation time.
  • Crank start point (time when vault buys tokens from the pool):
    • Timestamp-based Crank start point = activationPoint - 3600
    • Slot-based Crank start point = activationPoint - 9000
  • Vault deposit close point (time when vault deposits close):
    • Timestamp-based Vault, Deposit close point = Crank start point - 5 min
    • Slot-based Vault, Deposit close point = Crank start point - 750

​
After deployment

To view pool on the UI, access the link below For DLMM pool: https://app.meteora.ag/dlmm/[POOL_ADDRESS]

​
When can you withdraw tokens from the pool to the position owner?

CustomizablePermissionless DLMM: After pool activation point (trading starts)

​
Other Configuration Details

There are various config files that can be found in the config directory. It contains all the configurations required to run the scripts. We also need to provide the keypair for the payer wallet in keypair.json file.
DLMM Pool can also lock liquidity, so the lock_release_point can be set to some indefinite time then it ‘unlocks’

​
General configuration

  • rpcUrl: Solana RPC URL to get data and send transactions.
  • keypairFilePath: Keypair file path to send transactions.
  • dryRun: Set to true to send transactions.
  • computeUnitPriceMicroLamports: CU price in micro lamports unit. For example: 100000.
  • createBaseToken: Configuration to create base token.
  • baseMint: Base token address if the createBaseToken field is not set.
  • quoteSymbol: Quote token symbol, only SOL or USDC is supported.
  • quoteMint: Quote token mint, in case the user wants to create a DLMM launch pool with a token other than SOL or USDC.
  • dlmm: DLMM pool configuration.
Some configuration constraints:
  • createBaseToken and baseMint cannot be used together.
  • dynamicAmm and dlmm cannot be used together.
Create Base Token configuration:
  • mintBaseTokenAmount: Base token amount to be minted.

​
DLMM configuration

  • binStep: DLMM pool bin step.
  • feeBps: Fee bps for DLMM pool.
  • initialPrice: Initial pool price.
  • activationType: To activate pool trading based on slot or timestamp.
  • activationPoint: To activate pool trading at a point, either slot valut or timestamp value based on activationType.
  • priceRounding: Should be up or down.
  • hasAlphaVault: Whether alpha vault is enabled or not for this pool.
  • creatorPoolOnOffControl: Allow creator to turn on/off pool control.
When using the endpoint instruction initializeCustomizablePermissionlessLbPair the purpose is for creating a launch pool for the token for the first time, so only one DLMM pool is meant to be created for that token pair. If you are using that instruction to create a new DLMM pool with the same base and quote tokens, but with different parameters, the transaction will fail. Pool creator must have at least 1 lamport worth of the base token in the wallet to prove ownership.

​
Alpha Vault configuration

  • poolType: dynamic or dlmm pool type.
  • alphaVaultType: Alpha Vault type, could be fcfs or prorata
  • depositingPoint: Absolute value that, the slot or timestamp that allows deposit depend on the pool activation type.
  • startVestingPoint: Absolute value, the slot or timestamp that start vesting depend on the pool activation type. If no vesting is required, you should put this as 1 sec after the pool’s activationPoint
  • endVestingPoint: Absolute value, the slot or timestamp that end vesting depend on the pool activation type. If no vesting is required, this should be the same as startVestingPoint
  • maxDepositCap: Maximum deposit cap.
  • individualDepositingCap: Individual deposit cap.
  • escrowFee: Fee to create stake escrow account. If this fee is added, it will be a one-time fee charged when users create a stake escrow account. This acts as a tax and makes it prohibitively expensive for users to attempt to use multiple wallets to bypass the individual deposit cap. It’s charged in native SOL (non-wrapped version) and will be sent to the Meteora treasury.
  • whitelistMode: permissionless or permission_with_merkle_proof or permission_with_authority.

​
Alpha Vault Pro rata configuration

  • depositingPoint: Absolute value that, the slot or timestamp that allows deposit depend on the pool activation type.
  • startVestingPoint: Absolute value, the slot or timestamp that start vesting depend on the pool activation type. If no vesting is required, you should put this as 1 sec after the pool’s activationPoint
  • endVestingPoint: Absolute value, the slot or timestamp that end vesting depend on the pool activation type. If no vesting is required, this should be the same as startVestingPoint
  • maxBuyingCap: Maximum buying cap.
  • escrowFee: Fee to create stake escrow account. If this fee is added, it will be a one-time fee charged when users create a stake escrow account. This acts as a tax and makes it prohibitively expensive for users to attempt to use multiple wallets to bypass the individual deposit cap. It’s charged in native SOL (non-wrapped version) and will be sent to the Meteora treasury.
  • whitelistMode: permissionless or permission_with_merkle_proof or permission_with_authority.

​
Alpha Vault Key Components

Vault Types: Supports both permissionless (without whitelist) and permissioned (with whitelist) Alpha Vaults. Whitelist Modes: Without whitelist:
  • Permissionless
With whitelist:
  • PermissionWithMerkleProof
  • PermissionWithAuthority
alphaVaultType (Vault Mode):
  • Pro-rata
  • FCFS (First-Come, First-Served)
Individual Deposit Cap:
  • Global individual deposit cap without whitelist only possible on FCFS vault mode, not possible on Pro rata vault mode.

​
Alpha Vault TypeScript SDK

After creating the Alpha Vault for your pool, check out the Alpha Vault SDK for different ways to interact with it. For example, depositing funds into the Alpha Vault, cranking the Alpha Vault to buy tokens from the pool, or claiming purchased tokens from the Alpha Vault.

​
For Testing Bun Scripts

First, run the localnet 
bun run start-test-validator
Then run the test: 
bun test

​
Other Alpha Vault Considerations

​
What is the general process if you want to use a Launch Pool with Alpha Vault, then later use the USDC or SOL funds raised from the Launch Pool to redeploy the liquidity to another new pool?

When setting up the Launch Pool with Alpha Vault, the token deployer should set token claim unlock from Alpha Vault to be sometime after pool activation time (after pool starts trading). The token deployer must set enough buffer time after pool activation to withdraw liquidity from the Launch Pool first to redeploy to another pool, BEFORE users can claim tokens from the Alpha Vault. Optional: Once the Launch Pool and Alpha Vault are set up, Meteora can help the team disable the Launch Pool from trading. This is a special requirement if you want the Launch Pool to be used only by the Alpha Vault to buy tokens for depositors, but not for public trading by everyone else.
It is important to note that you should NOT allow users to claim tokens from the Alpha Vault before the token starts trading anywhere. For the Alpha Vault, the startVestingPoint needs to be at least 1 sec after PoolActivationPoint. This would mean tokens unlock for claiming right after or some time after the pool starts trading. If you allow users to claim tokens (via Alpha Vault or any airdrops) before the official token trading time, users can use the tokens to create a secondary market immediately and skew your initial token price, negatively impacting your launch.
After the Launch Pool activation time, liquidity can be withdrawn from the Launch Pool and redeployed to another pool (e.g. DAMM v2 or another DLMM) that starts trading immediately or with another activation time. If the second pool has another activation time, it should be set earlier than the token claim unlock time from the Alpha Vault. Once the second pool activates for trading, the token is tradable for everyone, and users can start claiming from the Alpha Vault, depending on when you configured vesting to start.

​
For Testing Bun Scripts

First, run the localnet: 
bun run start-test-validator
Then run the test: 
bun test