Deep Dive
1. Combined GM Pool Yield/PnL Read (19 August 2026)
Overview: This update gives developers a unified view of a liquidity pool's performance. Instead of checking multiple sources, they can now see both the fees earned and the profits or losses from traders in one call.
The new fetchGmPoolYieldPnl function returns the fee-based annual percentage yield (APY) alongside the traders' net profit and loss (PnL) for each GM market token. This helps integrators build clearer dashboards and analytics tools for liquidity providers.
What this means: This is bullish for GMX because it makes life easier for developers building on the platform. Better tools can lead to more sophisticated apps and analytics, which can attract more advanced users and liquidity to the protocol. (Source)
2. JIT-Aware Trading Capacity & SDK Alignment (13 August 2026)
Overview: This release improves trading data accuracy by incorporating "Just-In-Time" (JIT) liquidity. It ensures the SDK shows the real amount available to trade at any moment, not just the static pool balance.
Developers now get capacityLong and capacityShort fields in market data, which tell them how much can be traded before hitting limits. The update also syncs all fee and PnL calculations in the SDK with the live GMX API to prevent discrepancies.
What this means: This is bullish for GMX as it enhances the reliability of third-party trading interfaces. Traders get more accurate information on trade sizes, leading to better execution and fewer failed transactions, which improves the overall user experience. (Source)
3. Preparation for v2.2c API & Botanix Removal (31 July 2026)
Overview: This is a maintenance update that future-proofs the SDK and cleans up outdated support. It adds compatibility for new data fields coming from GMX's backend and removes code for the Botanix chain, which is no longer active.
The change is "breaking," meaning developers using old Botanix features must remove that code when they upgrade. The focus is on ensuring the SDK works smoothly with the latest GMX infrastructure.
What this means: This is neutral for GMX. It's a necessary technical housekeeping task that keeps the developer tools modern and efficient, but it doesn't directly add new user-facing features. It shows the team is actively maintaining its core software. (Source)
Conclusion
GMX's development remains active, with recent SDK updates focused on providing richer data for developers and ensuring technical alignment with the live platform. This steady stream of backend improvements supports a more robust and developer-friendly ecosystem. How will these enhanced tools influence the next wave of applications built on GMX?