Setting Pool and Fee Config for Memecoin Pool v1
Current Default Fee System for Memecoin Pool v1
Dynamic Fee Scheduler: For Dynamic AMM Memecoin Pools v1, there is a fee scheduler where the % fee charged per swap changes over time. This fee is configurable and can be changed based on market conditions.
Protocol Fee: Protocol Fee represents the amount of fees charged per swap that goes to the protocol or integrations that drive volume to the pool. Protocol Fee is a % of the Dynamic Fee.
The default global Fee Config for Memecoin Pools on Meteora is currently (may change over time):
15% - when pool trading starts
7% - 10 min after pool trading starts (10 min after 15% starts)
5% - 130 min after pool trading starts (120 min after 7% starts)
2% - 250 min after pool trading starts (120 min after 5% starts)
1% - 370 min after pool trading starts (120 min after 2% starts)
0.5% - 490 min after pool trading starts (120 min after 1% starts)
0.25% - 24 hours after pool trading starts (950 min after 0.5% starts)
Important Notes
Only the Meteora team is able to change the default Dynamic Fee and Protocol Fee; projects have no backend access.
New config keys can only be created by Meteora. Highest fee % is 15% at the moment.
Integrators such as launchpads or other partners may need to use their own unique custom pool config key, if they want custom
pool_creator_authorityto prevent front-running of the token launch pool. New dedicated config keys can only be created by Meteora - Please reach out to the team if this is required.The
pool_creator_authoritydoesn't work with program address. It's not a program whitelist, it needs to be a PDA (program derived address) or normal account.All newly created config will not have a dynamic fee schedule applied to it, unless Meteora manually specifies it.
How to choose a suitable Pool & Fee Config from the list?
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.
Public Pool Config List
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_keywith 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.
Default Pool Config used by Meteora Frontend
By default, Meteora's frontend is currently using this pool config key for Memecoin Pool creation:
FiENCCbPi3rFh5pW2AJ59HC53yM32eLaCjMKxRqanKFJFor the
FiENCCbPi3rFh5pW2AJ59HC53yM32eLaCjMKxRqanKFJpool config, it doesn't allow creation of any Alpha Vault, therefore it's fieldvault_config_keyis1111111...
New Custom Pool Config and Fee Curve for Integrators / Launchpads
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_authoritydoesn'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.
Custom Fee Curve for a Specific Pool
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.
API to track associated Fee Curve for each Config
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 then choose a config with a fee curve that suits their integration.
Steps:
Press "Execute" and find and select the config you want to view
Example: Moonshot Integration - Custom Config Key and Fee Curve
After 14400 seconds since pool start trading, the fee rate will be 2.5%
After 86400 seconds since pool start trading, the fee rate will be 1%
How do you view the starting fee for the config?
Example: Moonshot Integration - Fee Curve starting fee
Pool Dynamic Fee starts at 500 bps (5%), and protocol fee is 20%
Combining the above two example parameters, the Moonshot Fee Curve is:
Pool Dynamic Fee starts at 5%
After 14400 seconds from start of pool trading, the fee rate will be 2.5%
After 86400 seconds from start of pool trading, the fee rate will be 1%
What does each field in the Fee Config mean?
config_address = the pool config key
trade_fee_bps = pool trading fee
protocol_fee_bps = protocol fee charged from pool trading fee
activation_duration = used to determine when exactly the pool will start trading.
start trade time = current_time + activation_duration Or current_slot + activation_duration, depends on the activation_type
vault_config_key = alpha vault config key. If it is
11111111111111111111111111111111, means no alpha vault. If not, the pool can create an alpha vault. Note: This is NOT the same as the vault address.pool_creator_authority = address which can use the pool config key to create a pool. If it is
11111111111111111111111111111111, it's public and available for everyone to useactivation_type = pool activation type. 0 = slot, 1 = time
Pool Config Example
Sample fields:
{ "config_address": "FiENCCbPi3rFh5pW2AJ59HC53yM32eLaCjMKxRqanKFJ", "trade_fee_bps": 1500, "protocol_fee_bps": 2000, "activation_duration": 0, "vault_config_key": "11111111111111111111111111111111", "pool_creator_authority": "11111111111111111111111111111111", "activation_type": 0 },
User Flow Example
A pool config may or may not have an associated vault config. There's no vault config associated when the vault_config_key is 11111111111111111111111111111111
When the pool config has a vault config, user can create the pool + Alpha Vault that is binded (auto-whitelisted) by the pool. The Alpha Vault created will inherit the parameters (Pro Rata / FCFS + buying_cap, vesting duration, etc.) from the vault config.
Let's say a user wants to create the pool ABC/SOL with an Alpha Vault, the user will need to:
Check for pool config that have
vault_config_keynot =1111..., andpool_creator_authorityis the user or1111...(accessible by the public)Based on the vault requirement the user wants, the user will need to:
a) Check all the pool configs from step 1, which are each mapped to a
vault_config_key, as well asb) Check for vault config and look for one that fits the requirement
If the user finds a requirement that suits their needs, they can use that
pool_config_keyto create the pool, then use the pool config-mappedvault_config_keyto create the vault. As long asvault_config_keyis used, the vault is automatically whitelisted upon pool creation.
All the settings are already predefined by pool_config + its mapped vault_config_key
The permutations for pool config + Alpha vault are created by the Meteora team.
Pool Config Example
Alpha Vault Config Example
In this example above, only the pool_creator_authority
(5unTfT2kssBuNvHPY6LbJfJpLqEcdMxGYLWHwShaeTLi) can use the pool config 8aPHoLN8ke6PhWeYA7ELi19fppptVYUCQvqKWR5yP1sn to create a pool with the below settings:
1.5% fee
20% protocol fee
pool start trade after 1512000 slot upon creation
slot based activation
and can create a binded Alpha Vault with FCFS config as shown below:
max deposit cap = 10 token
vested over 24106 slot after pool activate
deposit opens at 24107 slot before vault crank
every escrow maximum can only deposit 1 token
Full Pool and Alpha Vault Config List
If your preferred configs are not available in the pre-defined config lists above, please contact the Meteora team. You will need your own unique config key specific to your integration.
Reminder: Fees from Permanently Locked Liquidity
Projects can permanently lock the liquidity in the Memecoin Pool, but still claim fees on the locked liquidity. 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 was permanently locked).
The project will only be able to claim swap fees from locked liquidity starting from t2.
Last updated
