Setting Pool and Fee Config for Memecoin Pool v2

Memecoin Pool v2 is a DAMM v2 Pool with a Fee Scheduler.

A pool initialized with the program endpoint InitializeCustomizablePool will be tagged as meme

A DAMM v2 Memecoin Pool has the Fee Scheduler feature enabled, while a DAMM v2 Volatile Pool does not.

Current Default Fee Schedule for Memecoin Pool v2

• Fee Scheduler: For DAMM v2 Memecoin Pools, there is a fee scheduler where the % fee charged per swap changes over time, and ending at a % fee set by the pool creator. This fee schedule is configurable and can be linear or exponential, 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 total LP Fee collected.

Currently, the default Fee Schedule used for Memecoin Pool v2 on Meteora frontend is based on an exponential curve; 50% when pool trading starts, and dropping every minute for 120 min, ending at 0.25%.

Just as an example, here's a look at the % fee at different time intervals:

• 50% - when pool trading starts

• 32.15% - 10 min after pool trading starts (10 min after 50% starts)

• 20.67% - 20 min after pool trading starts (10 min after 32.15% starts)

• 13.29% - 30 min after pool trading starts (10 min after 20.67% starts)

• 8.55% - 40 min after pool trading starts (10 min after 13.29% starts)

• 5.50% - 50 min after pool trading starts (10 min after 8.55% starts)

• 3.53% - 60 min after pool trading starts (10 min after 5.50% starts)

• 2.27% - 70 min after pool trading starts (10 min after 3.53% starts)

• 1.46% - 80 min after pool trading starts (10 min after 2.27% starts)

• 0.94% - 90 min after pool trading starts (10 min after 1.46% starts)

• 0.60% - 100 min after pool trading starts (10 min after 0.94% starts)

• 0.39% - 110 min after pool trading starts (10 min after 0.60% starts)

• 0.25% - 120 min after pool trading starts (10 min after 0.39% starts)

Pool and Fee Config for Integrators

Each pool is a PDA of token mints + config. There are 2 types of config; public or private.

Public config

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 https://github.com/MeteoraAg/cp-amm-sdk/blob/main/src/CpAmm.ts and call the following function.

Or you can use this json file:

25KB

damm v2 public Keys.json

Private config

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.

This section is under construction. More details will be added soon.