Deep Dive
1. One-Click Trading Subaccount Improvements (10 June 2026)
Overview: This update makes the "One-Click Trading" feature more robust, especially for users who let the SDK manage their trading subaccounts. It ensures the software's view of an account's status stays perfectly in sync with the blockchain.
The release adds new functions to check a subaccount's on-chain state and refresh it, and introduces safeguards to prevent orders from being placed if an account's action limits are nearly exhausted. It also fixes how transaction approvals are handled after a failed submission, making retries smoother.
What this means: This is bullish for GMX because it makes automated, high-frequency trading on the platform more reliable and secure. Users can trade with greater confidence, knowing the underlying software better prevents errors related to account state, which could support higher trading volumes.
(Source)
2. SPCX Market and Leverage Cap Support (9 June 2026)
Overview: This update formally adds support for trading the SPCX/USD perpetual contract on Arbitrum. It includes all the necessary market data and, importantly, applies a maximum leverage cap of 10x for this asset.
The integration provides the config files and token metadata needed for any application or interface to list and correctly handle the SPCX market, including its specific risk parameters.
What this means: This is neutral for GMX, as it represents routine ecosystem expansion. Adding new markets like SPCX gives traders more choice, potentially attracting new users. The built-in leverage cap is a prudent risk management feature that protects traders from extreme volatility.
(Source)
3. Referral Code Integration for API Orders (9 June 2026)
Overview: This change allows developers to easily add referral codes to trades processed through GMX's API. It supports both human-readable codes and pre-encoded values for increase, decrease, and swap orders.
The update ensures that when a third-party app prepares an order via the SDK, the referral code is correctly included in the data sent to the GMX backend for signing and execution.
What this means: This is bullish for GMX because it lowers the barrier for other projects to integrate and promote GMX's native referral program. Easier integration can lead to wider distribution and user acquisition, directly benefiting protocol growth and fee generation.
(Source)
Conclusion
The recent SDK updates show GMX is simultaneously strengthening core trading infrastructure and removing friction for user growth. How will these backend improvements translate into on-chain activity and protocol revenue in the coming months?