Aster Exchange said it has reimbursed users after a sudden price Glitch has sent the XPL -Legous Contract and had wiped on lifting tree positions.
Related lecture
According to reports, the marking price of the contract briefly disconnected from the markets on September 25, 2025 and jumped from around $ 1.30 to almost $ 4 on aster while XPL Elsewhere almost $ 1.30. The mismatch forced massive liquidations on the platform.
Aster -issues Refugees
According to Aster’s public messages and follow -up reports, the exchange has quickly moved to cover to lose. Restitutions were paid in USDT to bills affected by the abnormal movements. A second payment round also covered trade and liquidation costs.
One analysis placed the total reimbursements at around $ 16.6 million, although figures vary between sources. Reports say that many affected traders have received compensation within a few hours after recognizing the incident.
The compensation for the XPL -PERPP -incident is now fully divided. All affected users have reimbursed their accounts directly in USDT.
We appreciate your patience and understanding during this process. For further questions, send a ticket via … https://t.co/WP0en9VM44
– Aster (@ASTER_DEX) September 26, 2025
Defective index and cap settings
Based on reports, the underlying problem was a configuration error linked to the index and the price cap of the contract. The index was hard coded at $ 1 during the pre-launch setup of the token, and there was a mark for $ 1.22 a mark for $ 1.22 to limit swings.
TLDR on Aster $ XPL Situation:
> Index price was hard coding up to $ 1
> Marking price was covered at $ 1.22
> When they removed the price limit, it stood to $ 4, while the prices remained stable at other fairsThis was a consequence of gross negligence among the exchange operators. No exploits/etc. https://t.co/e8xr01fly9 pic.twitter.com/HCDJ2BVUA1
– Guthix 🫵 (@Guthixhl) September 25, 2025
That limit was lifted before the index was corrected, allowing the Aster Mark price to run away from external market prices. As a result, positions on the platform were liquidated, although the wider market did not show a similar peak.
The event left a sting for some traders. Large liquidation losses and reimbursements affect accounts that were long or short with leverage. Some users reported persistent questions about marquits and trade history, even after reimbursements had landed.
At least one report indicated that Aster reported all client funds as SAFU and that full internal procedure was promised.
Community response and further steps
According to reports on social media, the answer was divided. Some traders complimented the immediate repayments and describe the action as the recovery of short -term confidence.
Related lecture
Some called for stricter screening and more explicit communication. On the incident, industrial districts and a reminder that both decentralized and centralized platforms can fail when indexfeeds, caps or other safety switches are incorrectly configured.
Traces and transaction vouchers for reimbursements were presented as ways to confirm that reimbursements were completed.
The treatment of Aster avoided a long -term user uprising, but the incident emphasizes a simple point: setting small code or errors can cause large money movements.
Exchanges are likely to be confronted with new questions about testing, pre-launch checks and how quickly guarantees can be engaged.
Featured image of Unsplash, graph of TradingView