Create: Memecoin Pool v1
Last updated
Last updated
v1 are a subset of Dynamic AMM Pools. A Memecoin Pool v1 is a Dynamic AMM Pool that has a fee scheduler, with liquidity permanently locked at pool creation.
Memecoin Pools v1 can be integrated with platforms such as memecoin launchpads to support liquidity and trading for the token after it has graduated from the launchpad.
To create a new Memecoin Pool v1 or for integration purposes, you can use the Dynamic AMM TypeScript SDK with the code example highlighted below.
Dynamic AMM SDK:
NPM:
Dynamic AMM Program ID: Eo7WjKq67rjJQSZxS6z3YkapzY3eMj6Xy8X5EQVn5UaB
Dynamic AMM API endpoints:
Devnet:
If you want to create an Alpha Vault along with your new pool, you also need to find a pool_config_key
that is mapped to a vault_config_key
that meets your requirements.
If none of the pool_config_key
in the list meet your requirements, please reach out to Meteora for a custom pool config key.
Using this endpoint, integrators can input the config pubkey, and it will return an array of fee update timings for the config, if there's any.
Integrators may choose a pool_config_key
with a fee curve that suits your integration.
If there is no existing config in the list that fits your project's requirement, a new config needs to be created.
Only the Meteora team can create a new config to add it to the preset pool config list.
By default, Meteora's frontend is currently using this pool config key for Memecoin Pool creation: FiENCCbPi3rFh5pW2AJ59HC53yM32eLaCjMKxRqanKFJ
For the FiENCCbPi3rFh5pW2AJ59HC53yM32eLaCjMKxRqanKFJ
pool config, it doesn't allow creation of any Alpha Vault, therefore it's field vault_config_key
is 1111111...
Custom Pool Config Key: Integrators such as launchpads or other partners may need to use their own unique custom pool config key, if they want custom pool_creator_authority
to prevent front-running of the token launch pool.
NOTE:
New dedicated config keys can only be created by Meteora. Please reach out to us if this is required.
The pool_creator_authority
doesn't work with program address. It's not a program whitelist, it needs to be a PDA (program derived address) or normal account.
Custom Fee Curve: If you are an integrator, Meteora can also apply a custom fee curve/schedule for your pools, but we will need to create a dedicated config key for your team, where pool_creator_authority
is linked to your signer wallet for pool creation. You would need to send us your signer wallet that would be used to deploy the pools.
NOTE:
Even with a dedicated config key for your team, Meteora would need to customize the fee curve/schedule for you. You can't do it on your own.
Custom Pool Config and Fee Curve is used by integrators such as Moonshot by DEX Screener.
If required, Meteora can set a custom fee curve for a single, specific pool. This would override the fee curve used by the pool's config key, doesn't matter which config key is used.
Using the example, update it with your pool config key selected and other parameters in order to create a Memecoin Pool - which is a Dynamic AMM Pool with a fee scheduler and with liquidity (LP tokens) locked to the user's own lock escrow account.
Please refer to the section under let allocations = [
In the config file, you can specify different wallet addresses to receive fees from the locked liquidity, and the % to allocate to each wallet. Multiple wallets are possible, but their allocations must add up to 100%.
If the project wants to permanently lock liquidity in the Memecoin pool, they should ideally lock the liquidity BEFORE the pool starts trading, so that swap fees from locked liquidity are captured the second trading starts.
In a scenario where:
The pool started trading - t0
Liquidity gets deposited to the pool by the project, but not locked - t1
Subsequently, that liquidity is permanently locked by the project - t2
The project will not be able to claim swap fees earned from t1 to t2, since fees from t1 to t2 are assigned to the LP token before the LP token gets permanently locked. When the LP token gets locked, the earlier fees are locked along with it.
The project will only be able to claim swap fees from locked liquidity starting from t2.
What fee parameters to choose depends on your project's needs. You will need to look at the and choose a suitable pool_config_key
with your preferred fee parameters.
Pool config list:
Devnet API: You can also get the list of config keys from devnet API
API endpoint to return the associated fee curve for each existing config:
Note: For more information about setting Pool and Fee Config for Memecoin Pools, please read .
After you have selected your preferred pool_config_key
, reference this example: