#launchpad

⏰ DBC Program Update containing Vested Locked Liquidity and Pool Creation Fee is COMING SOON

📆 ETA: Friday, 16th January 2026, 11am UTC+8 (in ~1 week)**

❗️NOTE: This upcoming update contains BREAKING CHANGES for Launchpad Partners who have 100% unlocked LP liquidity in their graduated DAMM v2 pool. All affected Launchpad Partners are to craft and test their updated DBC config key on DEVNET using the Typescript SDK beta version @meteora-ag/dynamic-bonding-curve-sdk@1.4.10-rc.0 before the program update next week

require!(
    config.get_total_liquidity_locked_bps_at_n_seconds(SECONDS_PER_DAY)?
        >= MIN_LOCKED_LIQUIDITY_BPS,
    PoolError::InvalidMigrationLockedLiquidity
);

// SECONDS_PER_DAY  =  86400 = 1 day
// MIN_LOCKED_LIQUIDITY_BPS = 10% = 1000 bps

Breaking Changes:
- Endpoints: create_config, initialize_virtual_pool_with_spl_token and initialize_virtual_pool_with_token2022 will only allow config that has minimum 10% of locked liquidity in at least 1 day

- migration_damm_v2 endpoint require vesting accounts for first_position and second_position if LP vesting was configured.

Added:
- Add new endpoint claim_partner_pool_creation_fee to allow partners to withdraw the pool creation fee.

- PoolConfig account now stores creator_lp_vesting_info and partner_lp_vesting_info fields. Only applicable to DAMM v2 migration option. It store vesting parameters required for lock_position cpi during DAMM v2 migration.

Changed:
- Allow partners to configure the pool_creation_fee when creating a config. The value is in SOL lamport, so when token creator create pool (throught endpoint initialize_virtual_pool_with_spl_token and initialize_virtual_pool_with_token2022`), they would need to pay `pool_creation_fee in SOL lamport. Later partner would be able to claim that fee (Meteora would take 10% from that fee)

- Allow partners to config partner_lp_vesting_info and creator_lp_vesting_info when creating config key that includes liquidity vesting information if pool is migrated to damm v2 later

Full Summary: https://meteoraag.notion.site/Changelog-Vested-Lock-Liquidity-and-Pool-Creation-Fee-2e3cd1ff21118010af56f3daff676306?pvs=74

#launchpad

📣 REMINDER: DBC Program Update containing Vested Locked Liquidity and Pool Creation Fee is COMING THIS WEEK

📆 ETA: Friday, 16th January 2026, 11am UTC+8

❗️NOTE: This upcoming update contains BREAKING CHANGES for Launchpad Partners who have 100% unlocked LP liquidity in their graduated DAMM v2 pool. All affected Launchpad Partners are to craft and test their updated DBC config key on DEVNET using the Typescript SDK beta version @meteora-ag/dynamic-bonding-curve-sdk@1.4.10-rc.0 before the program update this Friday.

In this update, DBC Config Keys will require at least 10% of total liquidity locked+vested at day 1 (86400 seconds) after migration.

require!(
    config.get_total_liquidity_locked_bps_at_n_seconds(SECONDS_PER_DAY)?
        >= MIN_LOCKED_LIQUIDITY_BPS,
    PoolError::InvalidMigrationLockedLiquidity
);

// SECONDS_PER_DAY  =  86400 = 1 day
// MIN_LOCKED_LIQUIDITY_BPS = 10% = 1000 bps

Full Announcement: https://t.me/meteora_dev/46

Full Summary: https://meteoraag.notion.site/Changelog-Vested-Lock-Liquidity-and-Pool-Creation-Fee-2e3cd1ff21118010af56f3daff676306?pvs=74

#launchpad

gmet!

the DBC [release 0.1.8] program updates scheduled earlier today is now live 🙏🏻

full announcement here: https://t.me/meteora_dev/46

#launchpad

⏰ DBC Program Update containing Market Cap Fee Scheduler and First Swap with Min Fee is COMING SOON

📆 ETA: Wednesday, 4th February 2026, 11am UTC+8

❗️NOTE: This upcoming update contains BREAKING CHANGES for Launchpad Partners who are parsing/indexing the EvtPartnerClaimPoolCreationFee event. All affected Launchpad Partners are to update their event deserialization to include the new fee_receiver field and test using the Typescript SDK version @meteora-ag/dynamic-bonding-curve-sdk@1.5.2 before the program update.

Breaking Changes:
EvtPartnerClaimPoolCreationFee event now includes a fee_receiver field. Partners parsing/indexing this event must update their deserialization.

Added:
- New migrated_pool_base_fee_mode and MigratedPoolMarketCapFeeSchedulerParams fields in create_config to allow partners to configure a market cap-based fee scheduler for graduated DAMM v2 pools. Instead of a fixed fee after migration, the pool fee dynamically adjusts based on the token's price movement (market cap growth). Two modes available: Linear (mode 3) and Exponential (mode 4).

- New enable_first_swap_with_min_fee field in create_config to allow pool creators to initialize a pool and perform their first buy in a single transaction at the minimum base fee, bypassing anti-sniper fees on that first swap only.

Changed:
- When enable_first_swap_with_min_fee is enabled in the config, swap and swap2 endpoints require SYSVAR_INSTRUCTIONS_PUBKEY in remaining accounts. The program uses this to verify that the transaction contains a pool initialization instruction before the swap. Only the very first swap on a newly created pool within the same transaction will receive the minimum base fee. All subsequent swaps are charged normal fees. The SDK handles passing this account automatically.

- A protocol migration fee of 0.2% (20 bps) is now charged upon migration. It takes a cut from the liquidity being migrated to the graduated pool.

SDK (v1.5.1-rc.0):
- New getStartingBaseFeeBpsFromBaseFeeParams helper to automatically derive the starting base fee from the pool's baseFeeParams.

Full Summary:
https://meteoraag.notion.site/Changelog-Market-Cap-Fee-Scheduler-and-First-Swap-with-Min-Fee-2f8cd1ff21118091a75ff67c04f598dd?pvs=74

#launchpad

We've launched Bedrock, a new framework to build tokenized equity on Solana.

https://x.com/0xSoju/status/2018371205083132068

Bedrock is our attempt to give tokens more rights, as we move towards a fully ICM future.

We're happy to work with you to see how Bedrock best fits into your business, reach out to Soju or the rest of the Meteora team for more info

#launchpad

DBC [release 0.1.9] Program Update containing Market Cap Fee Scheduler and First Swap with Min Fee update is NOW LIVE.

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

⏰ DAMM v2 Program Update (0.1.8) containing Lock Inner Position, and Inner Vesting Split is COMING SOON

📆 ETA: Monday, 9th February 2026, 11am UTC+8

Added:
- New endpoint lock_inner_position, allowing liquidity to be vested without an external Vesting account for better composability.

Changed:
- Endpoints split_position and split_position2 will now split InnerVesting of the Position account. Integrators who use position splitting should account for the new inner vesting split behavior.

Full Changelog:
https://github.com/MeteoraAg/damm-v2/blob/release_0.1.8/CHANGELOG.md

Full Summary:
https://meteoraag.notion.site/Changelog-Fix-Pool-Params-Lock-Inner-Position-Inner-Vesting-Split-2fccd1ff211180ef8921f3da0b35f13a

📣 DAMM v2 [release 0.1.8] Program Update containing Lock Inner Position and Inner Vesting Split is NOW LIVE.

Full changelog:
https://github.com/MeteoraAg/damm-v2/blob/release_0.1.8/CHANGELOG.md

Full summary:
https://meteoraag.notion.site/Changelog-Fix-Pool-Params-Lock-Inner-Position-Inner-Vesting-Split-2fccd1ff211180ef8921f3da0b35f13a

📣 API Reference Update: DLMM & DAMM v2

We've updated our API reference documentation for DLMM and DAMM v2 with new base endpoints.

What's changing:

New Base URLs
DLMM: https://dlmm.datapi.meteora.ag/
DAMM v2: https://damm-v2.datapi.meteora.ag/

Legacy API Deprecation
The legacy API endpoints (dlmm-api.meteora.ag and dammv2-api.meteora.ag) will be decommissioned on March 15, 2026. Please migrate to the new base URLs before this date.


Important:
Request and response schemas have changed significantly as part of a full API rewrite.

Action required:
Update your integrations to use the new base URLs. The legacy endpoints will continue to function until March 15 but will no longer be available after that date.

Full API reference docs:
https://docs.meteora.ag/api-reference

#trading

⏰ DAMM v2 Program Update (0.2.0) containing Compounding Fee Mode, Pool Layout Versioning, and Partner Fee Removal is COMING SOON

📆 ETA: Friday, 13th March 2026, 11am UTC+8

❗️NOTE: This upcoming update contains BREAKING CHANGES affecting:
1. Trading Terminals parsing/indexing the EvtSwap2 event
2. Trading Terminals computing swap quotes for DAMM v2 pools
3. Trading Terminals tracking pool balances for DAMM v2 pools

All affected partners must update before the program goes live.

Breaking Changes:

1. Swap Quote Math (Concentrated Liquidity Pools)
The partner fee is no longer included in quote calculations.
→ Update your fee math: remove partner_fee from swap quote calculations.

2. Swap Event (EvtSwap2)
swap_result.partner_fee is removed and replaced by swap_result.claiming_fee + swap_result.compounding_fee. Total trading fee = claiming_fee + compounding_fee.
→ Update your event deserialization to use the new fields.

3. Pool Balance Tracking
- Concentrated liquidity pools: continue using the existing formula.
- Compounding pools (new): read token_a_amount and token_b_amount directly from pool state.
→ Handle both pool types when tracking balances. Concentrated pools will migrate to pool state in a future update.

Added:
- New collect_fee_mode (Compounding): fees collected in quote token, with a configurable percentage compounded back into reserves. These pools follow the constant-product formula (token_a * token_b = constant) instead of a concentrated price range.
- Endpoints create_config, initialize_customizable_pool, and initialize_pool_with_dynamic_config now support collect_fee_mode == Compounding and configurable compounding_fee_bps.

Changed:
- partner field removed from Pool struct.
- claim_partner_fee endpoint removed.

Full Summary:
https://meteoraag.notion.site/Changelog-Compounding-Liquidity-31ccd1ff2111801d9977df1b3d24fce7

⚠️ REMINDER: Legacy API Decommission

This is a follow-up reminder that the legacy DLMM and DAMM v2 API endpoints will be permanently decommissioned on March 15, 2026.

If you haven’t migrated yet, please do so now. After March 15, any calls to the legacy endpoints will fail.

Endpoints going offline on March 15:
∙ dlmm-api.meteora.ag
∙ dammv2-api.meteora.ag

New endpoints to migrate to:
∙ DLMM: https://dlmm.datapi.meteora.ag
∙ DAMM v2: https://damm-v2.datapi.meteora.ag/

Important reminder:
The new API is a full rewrite request and response schemas have changed. Please review the updated API reference before migrating.

📖 Full API reference docs: https://docs.meteora.ag/api-reference

#trading

⏰ DAMM v2 Program Update (0.2.0) containing Compounding Fee Mode, Pool Layout Versioning, and Partner Fee Removal is COMING TOMORROW

📆 ETA: Friday, 13th March 2026, 11am UTC+8

⚠️ Breaking Changes for Trading Terminals:

1. Swap Quote Math
• Concentrated pools: partnerFee removed from quote results. Remove it from fee calculations.
• Compounding pools (new): Use constant-product formula (x * y = k). Compute quotes using token_a_amount, token_b_amount, and liquidity from pool state.

2. Swap Event (EvtSwap2)
swap_result.partner_fee is removed. Total trading fee is now split into:
• claiming_fee — claimable portion
• compounding_fee — compounded back into liquidity
Update event deserialization accordingly.

3. Pool Balance Tracking
• Compounding pools: Read token_a_amount and token_b_amount directly from pool state (not derived from liquidity math).

Full Summary:
https://meteoraag.notion.site/Changelog-Compounding-Liquidity-31ccd1ff2111801d9977df1b3d24fce7

#trading

DAMM v2 [release 0.2.0] containing Compounding Fee Mode, Pool Layout Versioning, and Partner Fee Removal is NOW LIVE.

You can bump your SDK to the latest version @meteora-ag/cp-amm-sdk@1.3.7 to start using the latest features.

#launchpad

⏰ DBC Program Update (0.1.10) containing DAMM v2 Migration Inner Positions and DAMM v2 Compounding Fee Support is COMING SOON

📆 ETA: Monday, 16th March 2026, 11am UTC+8

Added:

• New MigratedCollectFeeMode.Compounding (2) option in migratedPoolFee.collectFeeMode when creating a config for DAMM v2 migration. Requires compoundingFeeBps (1–10,000) when enabled.

Changed:

• DAMM v2 migration now uses the position itself for LP vesting instead of external vesting accounts, reducing the number of accounts required in the migrateDammV2 instruction.

Full Summary:
https://meteoraag.notion.site/Changelog-Migrate-to-DAMM-v2-Inner-Positions-DAMM-v2-Compounding-Fee-321cd1ff211180f3bb21e40a647c2297