Setting Pool and Fee Config for DAMM v2
Last updated
Last updated
Each pool is a PDA of token mints + config. There are 2 types of config; public or private.
In a public config, anyone can use one of the public config keys to create a pool. Currently, we have 72 config keys created for devnet and mainnet. Integrators can consider using a public config if tokens cannot be bought (leaked) before the token launch time. But launchpads typically use a private config.
To fetch all the public config keys, visit and call the following function.
Or you can use this json file:
In a private config, only a specified address (configured in the config key) can create a pool with that config. If you are a launchpad, this helps you prevent front-running of the token launch pool.
Integrators such as launchpads or other partners may need to use their own unique pool config key (with a custom fee schedule), if they want custom pool_creator_authority to prevent front-running of the token launch pool. New dedicated config keys can only be created by Meteora, so please reach out to the team if this is required.
If you're an integrator that's keen to create your own unique custom pool config key with a custom fee schedule and pool_fees, please reach out to the team.
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.
For Public Config Key: Integrators cannot change the fee schedule for that particular public config key.
For Private Config Key: If Meteora has already created a private config key for an integrator, how does the integrator change the fee schedule after that? Integrators can reach out to Meteora to request to change their fee schedule; the Admin as the ability to change the fee schedule for the private config key.
