#launchpad

DBC [release 0.1.10] containing DAMM v2 Compounding Fee Support and DAMM v2 Migration Inner Positions is NOW LIVE.

You can bump your SDK to the latest version @meteora-ag/dynamic-bonding-curve-sdk@1.5.6 to start using the latest features.

#all

gmet everyone

⚠️ Grouped API endpoints sunsetting May 30th, 2026

The Grouped endpoints on both DLMM and DAMM v2 Data APIs will be permanently decommissioned on May 30, 2026. After this date, requests to these endpoints will return 404.

Affected endpoints

DLMM
• GET /pools/groups
• GET /pools/groups/{lexical_order_mints}

DAMM v2
• GET /pools/groups
• GET /pools/groups/{lexical_order_mints}

Action required
If your integration depends on these endpoints, you'll need to migrate before May 30. We won't be providing a drop-in replacement, so you will need to reconstruct the grouped endpoints behavior or find alternative solutions.

#all

⏰ DLMM Program Update (0.12.0) containing Limit Order and Quote Token Fee is COMING SOON

📆 ETA: Week of 12th May 2026, Tuesday, 11am GMT+8

⚠️ This update contains BREAKING CHANGES affecting:
1. Trading Terminals that index swap and swap2 instructions for DLMM pools
2. Trading Terminal that handles Swap Quote computation for DLMM pools
3. Trading Terminals that index Swap to pivot to index Swap2Evt

Breaking Changes:

- Enum FunctionType no longer defaulted to FunctionType::LiquidityMining. All existing onchain LbPair account will defaulted to FunctionType::Undetermined. With FunctionType::Undetermined, if there's liquidity reward initialized, it will be FunctionType::LiquidityMining, else will be FunctionType::LimitOrder

- Swap quote mechanism due to introducing of collect fee mode on in/out side, and limit order mechanism. Affected endpoints are swap, swap_exact_out, swap_with_price_impact, swap2, swap_exact_out2 and swap_with_price_impact2.

- Due to new limit order logic (consuming more CU), max bins to swap in 1 instruction changes from 280 bins to 260 bins

- Endpoint swap and swap2 bitmap extension account will be mutable due to limit order logic require flipping of liquidity tracking bits.

- Event FeeParameterUpdate added new field base_fee_power_factor

- AccountsType enum variants introduces TransferHookReferral. Clients building swap2, swap_exact_out2 and swap_with_price_impact2 instructions must update their RemainingAccountsInfo slices to include AccountsType::TransferHookReferral when the swap has host_fee_in account. Additionally, any required transfer hook accounts for the referral mint must also be provided in the instruction.

Added:

- New endpoint add_liquidity_by_weight2, that is same as add_liquidity_by_weight but supports token2022

- New endpoint set_permissionless_operation_bits to allow position owner to enable permissionless authorization on some operations such as claim_fee

- New endpoint place_limit_order to allow user to place limit orders for either bid or ask side.

- New endpoint cancel_limit_order to cancel limit order.

- New endpoint close_limit_order_if_empty to close a limit order if it's empty.

- Account PresetParameter added new collect_fee_mode field. All the existing PresetParameter account will have default CollectFeeMode::OnlyInput.

- Account LbPair::StaticParameters added new collect_fee_mode field. All existing LbPair account will have default CollectFeeMode::OnlyInput.

Changed:

- Allow permissionless claim_fee if position owner enabled it

- All the existing LbPair accounts without any liquidity mining rewards will be defaulted to limit order supported pool and doesn't support LM anymore. This is not revert-able.

- Endpoint go_to_a_bin will revert if the pool is disabled / before activation. The restriction can be bypassed by operator by passing operator associated accounts through remaining accounts.

NOTE: Do check out the Notion document for the full changes and minor notes

———

Full Changelog / Summary:
https://meteoraag.notion.site/Changelog-Limit-Order-and-Quote-Token-Fee-345cd1ff2111800cb99bce237364e71c?pvs=73

#all

gmet!

❗️We are pushing back the DLMM Program Update by 1 day to give Trading Terminals more time to adopt the changes

⏰ DLMM Program Update (0.12.0) containing Limit Order and Quote Token Fee is COMING SOON

⚠️ Note that this update contains BREAKING CHANGES affecting:
- Trading Terminals that index swap and swap2 instructions for DLMM pools
- Trading Terminal that handles Swap Quote computation for DLMM pools
- Trading Terminals that index Swap to pivot to index Swap2Evt

📆ETA: Wednesday, 13th May 2026, 11am UTC+8

Full Summary: https://meteoraag.notion.site/Changelog-Limit-Order-and-Quote-Token-Fee-345cd1ff2111800cb99bce237364e71c?pvs=73

any questions can ping @dannweeeee

#all

🎉 DLMM Program Update (0.12.0) containing Limit Order and Quote Token Fee is LIVE

You can bump your SDK to the latest version @meteora-ag/dlmm@1.9.8 to start using the latest features.

🗒️ For Trading Terminals do ensure the following BREAKING CHANGES are covered:
1. Trading Terminals that uses swap and swap2 instructions for DLMM pools
2. Trading Terminal that processes swapQuote computation for DLMM pools
3. Trading Terminals that index Swap to pivot to index Swap2Evt

#launchpad

⏰ DBC Program Update (0.2.0) containing Transfer Hook and Restricted Mint Authority is COMING SOON

📆 ETA: 3rd June 2026, Wednesday, 11am GMT+8

⚠️ This update contains BREAKING CHANGES affecting:

1. Launchpad Partners that uses CreatorUpdateAndMintAuthority or PartnerUpdateAndMintAuthority.

📝 This update also contains OPTIONAL affecting:

1. Trading Terminals can choose to index WithTransferHook event variants such as EvtInitializePoolWithTransferHook, EvtSwap2WithTransferHook, EvtCurveCompleteWithTransferHook, EvtCreateConfigV2WithTransferHook.

2. Swap Routers can choose to use swap2_with_transfer_hook for transfer-hook pools.

Breaking Changes:

- create_config endpoint now rejects the configs with the following token_update_authority: CreatorUpdateAndMintAuthority and PartnerUpdateAndMintAuthority

- initialize_virtual_pool_with_spl_token and initialize_virtual_pool_with_token2022 endpoints now reject configs whose token_update_authority is CreatorUpdateAndMintAuthority or PartnerUpdateAndMintAuthority. Existing configs on-chain that used these variants can no longer initialize new pools.

- For non-transfer-hook pools, base_mint mint authority can no longer be assigned to the creator or partner. It is always revoked at pool initialization. Transfer-hook pools may still assign mint authority to creator/partner.

Added:

- Added endpoint create_config_with_transfer_hook that creates a ConfigWithTransferHook account storing the transfer hook program alongside the pool config.

- Added endpoint initialize_virtual_pool_with_token2022_transfer_hook for creating virtual pools with token-2022 base mints that have transfer hooks.

- Added endpoints with transfer hook support: swap2_with_transfer_hook, claim_trading_fee2 and claim_creator_trading_fee2. These accept a transfer_hook_accounts_info: TransferHookAccountsInfo parameter for passing transfer hook extra accounts via remaining accounts.

- Added WithTransferHook event variants for events consumed by external indexers to differentiate between transfer-hook and non-transfer-hook pool operations: EvtInitializePoolWithTransferHook, EvtSwap2WithTransferHook, EvtCurveCompleteWithTransferHook, EvtCreateConfigV2WithTransferHook.

- Re-enabled TokenAuthorityOption::CreatorUpdateAndMintAuthority and TokenAuthorityOption::PartnerUpdateAndMintAuthority for transfer-hook configs only. The mint authority is assigned to the creator or partner at pool initialization.

Deprecated:

- Deprecated TokenAuthorityOption::CreatorUpdateAndMintAuthority and TokenAuthorityOption::PartnerUpdateAndMintAuthority for non-transfer-hook configs.

Full Changelog: https://docs.meteora.ag/developer-guides/dbc/changelog#dynamic-bonding-curve-0-2-0

#all

gmet!

⏰ DBC Program Update (0.2.0) containing Transfer Hook and Restricted Mint Authority is COMING SOON

📆 ETA: 3rd June 2026, Wednesday, 11am GMT+8

⚠️ This update contains BREAKING CHANGES affecting:

1. Launchpad Partners that uses CreatorUpdateAndMintAuthority or PartnerUpdateAndMintAuthority.

📝 This update also contains OPTIONAL affecting:

1. Trading Terminals can choose to index WithTransferHook event variants such as EvtInitializePoolWithTransferHook, EvtSwap2WithTransferHook, EvtCurveCompleteWithTransferHook, EvtCreateConfigV2WithTransferHook.

2. Swap Routers can choose to use swap2_with_transfer_hook for transfer-hook pools.

Full Changelog: https://docs.meteora.ag/developer-guides/dbc/changelog#dynamic-bonding-curve-0-2-0

any questions can ping @dannweeeee

#all

🎉 DBC Program Update (0.2.0) containing Transfer Hook and Restricted Mint Authority is LIVE

You can bump your SDK to the latest version @meteora-ag/dynamic-bonding-curve-sdk@1.5.9 to start using the latest features.

⚠️ This update contains BREAKING CHANGES affecting:
1. Launchpad Partners that uses CreatorUpdateAndMintAuthority or PartnerUpdateAndMintAuthority.

📝 This update also contains OPTIONAL affecting:
1. Trading Terminals can choose to index WithTransferHook event variants.
2. Swap Routers can choose to use swap2_with_transfer_hook for transfer-hook pools.

#launchpad

⏰ DAMM v2 Program Update (0.2.2) containing Position Delegate is COMING SOON

📆 ETA: 26th June 2026, Friday, 11am GMT+8

Breaking Changes:

- The following endpoints previously rejected unauthorized signers with Anchor's ConstraintTokenOwner (2015) and now reject with PoolError::InvalidAuthority (6053), PoolError::InvalidPermission (6054), or PoolError::DelegatedAmountNonZero (6070): claim_position_fee, claim_reward, add_liquidity, remove_liquidity, remove_all_liquidity, lock_position, lock_inner_position, permanent_lock_position.

Added:

- Added support for NFT delegates to manage positions. The following endpoints can now be signed by a delegate if the owner has granted them permission: claim_position_fee, claim_reward, add_liquidity, remove_liquidity, remove_all_liquidity, lock_position, lock_inner_position, permanent_lock_position. Note: the close_position, split_position, and split_position2 endpoints remain callable by the owner only.

- Added new endpoint update_delegate_permission to set the permission bitmask on Position.delegate_permission. Pass permission = 0 to clear all permissions. Callers are responsible for managing the SPL token delegate via SPL Approve / Revoke separately. The bitmask supports 8 permissions: AddLiquidity, RemoveLiquidity, RemoveLiquidityToOwner, ClaimPositionFee, ClaimPositionFeeToOwner, ClaimReward, ClaimRewardToOwner, LockPosition.

- Added new endpoint withdraw_dead_liquidity_reward allowing the funder to recover the unowned DEAD_LIQUIDITY reward share of a CollectFeeMode::Compounding pool at any time, without waiting for the reward campaign to end. This share is tracked by the new dead_liquidity_reward_checkpoint field in the Pool RewardInfo.

Changed:

- Renamed the signer account from owner to signer, now that the signer may be a delegate, in the following endpoints: claim_position_fee, claim_reward, add_liquidity, remove_liquidity, remove_all_liquidity, lock_position, lock_inner_position, permanent_lock_position.

Full Changelog: https://docs.meteora.ag/developer-guides/damm-v2/changelog#cp-amm-0-2-2

#all

gmet

⚠️ Grouped API endpoints sunsetting 29th June, Monday, 11am SGT

After this date, requests to these endpoints will return 4XX.

Affected endpoints:
DLMM
• GET /pools/groups
• GET /pools/groups/{lexical_order_mints}
DAMM v2
• GET /pools/groups
• GET /pools/groups/{lexical_order_mints}

Action required:
If your integration depends on these endpoints, you'll need to migrate before June 29th. We won't be providing a drop-in replacement, so you will need to reconstruct the grouped endpoints behavior or find alternative solutions.

NOTE: This is the final notice and extension of deprecation deadline.

#launchpad

🎉 DAMM v2 Program Update (0.2.2) containing Position Delegate is LIVE

You can bump your SDK to the latest version @meteora-ag/dlmm@1.4.4 to start using the latest features.

#all

gmet

⚠️ Grouped API endpoints are now deprecated as of 30 June 11am SGT

All requests to these endpoints will return 4XX.

Affected endpoints:
DLMM
• GET /pools/groups
• GET /pools/groups/{lexical_order_mints}
DAMM v2
• GET /pools/groups
• GET /pools/groups/{lexical_order_mints}

gmet

🎉 DFS Program Update (0.1.2) containing DBC Claim Trading Fee 2 endpoints is LIVE

📝 This update contains the following changes:
Whitelist DBC claim_trading_fee2 and claim_creator_trading_fee2 in fund_by_claiming_fee
The fund_by_claiming_fee endpoint now rejects when skip_reward is non-zero for DAMM v2 claim_reward instruction to prevent clearing pending rewards without funding the FeeVault

You can bump your SDK to the latest version @meteora-ag/dynamic-fee-sharing-sdk@1.1.0 to start using the latest features.

#launchpad

⏰ DAMM v2 Program Update (0.2.3) deprecating Rate Limiter is COMING SOON

📆 ETA: 20th August 2026, Thursday, 11am GMT+8

As part of our periodic assessment of and improvements to our Anti Sniper Suite for token launches, Rate Limiter Fee Mode will be deprecated on DAMM v2 to make way for newer and better anti sniper mechanisms. Note that Rate Limiter Fee Mode will no longer be available for new launches, however, existing coins and pools are unaffected.

Deprecated

- Deprecated BaseFeeMode::RateLimiter. New configs and new pools can no longer be created with BaseFeeMode::RateLimiter. Existing configs with BaseFeeMode::RateLimiter can no longer be used to create new pools.
- Existing pools with BaseFeeMode::RateLimiter are unaffected. Operators can still call fix_pool_fee_params, fix_config_fee_params and update_pool_fees on existing pools and configs with BaseFeeMode::RateLimiter.

Full Changelog: https://docs.meteora.ag/developer-guides/damm-v2/changelog#cp-amm-0-2-3

#launchpad

gmet @everyone

🎉 DAMM v2 Program Update (0.2.3) deprecating Rate Limiter is LIVE

You can bump your SDK to the latest version @meteora-ag/dlmm@1.4.6 to start using the latest features.