Aster Exchange announced that it has reimbursed users following a sudden price anomaly that caused the XPL perpetual contract to surge unexpectedly, resulting in liquidated leveraged positions.
Related Reading
Reports indicate that the contract’s mark price momentarily deviated from market values on September 25, 2025, escalating from around $1.30 to approximately $4 on Aster, while the price of XPL elsewhere remained close to $1.30. This discrepancy triggered widespread liquidations on the platform.
Aster Issues Refunds
In response to the situation, Aster’s public communications and subsequent reports revealed that the exchange acted quickly to cover losses. Users impacted by the fluctuations received refunds in USDT. A second round of payments also addressed trading and liquidation fees.
One analysis estimated total reimbursements at around $16.6 million, although estimates vary. Reports suggest that many affected traders received their compensation within hours of the incident being acknowledged.
Compensation for the XPL perp incident has now been fully distributed. All affected users have received reimbursement directly in USDT to their accounts.
We appreciate your patience and understanding throughout this process. For any further questions, please submit a ticket via… https://t.co/Wp0en9vm44
— Aster (@Aster_DEX) September 26, 2025
Faulty Index And Cap Settings
Reports suggest that the underlying issue stemmed from a configuration error associated with the contract’s index and price cap. The index had been hardcoded at $1 during the token’s pre-launch setup, alongside a mark price cap set at approximately $1.22 to mitigate volatility.
TLDR on Aster $XPL Situation:
> Index price was hardcoded to $1
> Mark price was capped at $1.22
> When they lifted the price cap, it surged to $4 while other exchanges maintained stable pricesThis was a case of gross negligence by the exchange operators. No exploits, etc. https://t.co/e8xR01FLY9 pic.twitter.com/hCdj2bvua1
— Guthix 🫵 (@GuthixHL) September 25, 2025
This price cap was removed before the index was corrected, leading the Aster mark price to diverge from external market values. Consequently, positions were liquidated on the platform despite no similar surges in the broader market.
The incident resulted in significant losses for some traders, impacting both long and short leveraged accounts. Users reported continuing uncertainty regarding margin points and trade history even after receiving reimbursements.
At least one report indicated that Aster classified all client funds as SAFU and committed to a thorough internal procedural review.
Community Response And Further Steps
Social media reactions were mixed. Some traders praised the prompt refunds, viewing it as a measure to restore short-term confidence.
Related Reading
Others called for more stringent vetting and clearer communication. Industry experts highlighted the event as a reminder that both decentralized and centralized platforms can falter when index feeds, caps, or other safety mechanisms are misconfigured.
Suggestions for on-chain traces and transaction receipts for the refunds were made as a means to verify that reimbursements were executed.
Aster’s swift action prevented an extended user backlash, but the incident underscores a critical point: minor coding or configuration errors can lead to significant financial repercussions.
Exchanges are expected to face renewed scrutiny regarding their testing processes, pre-launch checks, and the speed at which safeguards can be reinstated.
Featured image from Unsplash, chart from TradingView
