Zap Changelog

​

Release summary

​

What We Shipped

• Whitelisted Jupiter route_v2 and shared_account_route_v2 for zap_out
• zap_out now derives the amount_in offset from the AMM program and its instruction discriminator
• Updated Anchor to 1.0.2
• Deprecated Jupiter route and shared_account_route in favor of the v2 routes. Both stay whitelisted for zap_out
• offset_amount_in in ZapOutParameters is ignored. The field stays in the instruction layout

​

Program: zap 0.2.3

​

Changed

• Update anchor to 1.0.2
• Endpoint zap_out now derives the offset of amount_in in the swap payload from the amm program and its instruction discriminator, instead of reading it from ZapOutParameters.

​

Added

• Add Jupiter’s route_v2 and shared_account_route_v2 as whitelisted instructions for zap_out

​

Deprecated

• Jupiter’s route and shared_account_route are deprecated in favor of route_v2 and shared_account_route_v2. They remain whitelisted for zap_out for backward compatibility.
• offset_amount_in in ZapOutParameters is ignored. It remains in the instruction layout for backward compatibility.

​

Release summary

​

What We Shipped

• Support Zap-In to damm-V2 Compounding Pool Fee Mode
• Support Zap-In to single-sided damm-v2 pool

​

What To Do

​

Program: zap 0.2.2

​

Added

• Add support for damm-v2 pool with Compounding fee mode

​

Fixed

• Fix zap in to single-sided damm-v2 pool. A single-sided pool is a pool fully contains only one token in the pool pair, either fully token a (sqrt_price at sqrt_min_price) or fully token b (sqrt_price at sqrt_max_price)

​

TypeScript SDK: @meteora-ag/zap-sdk 1.3.0

​

Added

• Support Zap-In to damm-V2 Compounding Pool Fee Mode.
• Support Zap-In to single-sided damm-v2 pool. A single-sided pool is a pool that fully contains only one token of the pool pair, either fully token A (sqrt_price at sqrt_min_price) or fully token B (sqrt_price at sqrt_max_price).

​

Fixed

• Rebalance DLMM position with 1 bin. Reference: https://github.com/MeteoraAg/dlmm-sdk/pull/286