Aster Exchange said it has reimbursed users after a sudden price glitch sent the XPL perpetual contract soaring and wiped out leveraged positions.
One analysis put the total reimbursements at about $16.6 million, though figures vary across sources. Reports say many affected traders received 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.
Based on reports, the underlying problem was a configuration error tied to the contract’s index and price cap. The index had been hard-coded at $1 during the token’s pre-launch setup, and a mark price cap near $1.22 was in place to limit swings.
> Index price was hardcoded to $1 > Mark price was capped at $1.22 > When they removed the price cap, it spiked to $4 while prices remained stable on other exchanges
That cap was lifted before the index was corrected, allowing the Aster mark price to run away from external market prices. As a result, positions were liquidated on the platform even though the broader market showed no similar spike.
The event left a sting for some traders. Large liquidation losses and fees hit accounts that were long or short with leverage. Some users reported lingering questions about margin points and trade history even after reimbursements landed.
At least one report indicated that Aster reported all client funds as SAFU and that full internal procedure review was promised.
According to social media reports, the response was divided. Some traders complimented the immediate refunds, describing the action as restoring short-term confidence.
Some called for stricter screening and more explicit communication. Industry watchers pointed to the incident as a reminder that both decentralized and centralized platforms can fail when index feeds, caps, or other safety switches are misconfigured.
On-chain traces and transaction receipts for refunds were suggested as ways to confirm that reimbursements were completed.
Aster’s handling avoided a prolonged user revolt, but the incident highlights a simple point: small code or setting mistakes can cause big money moves.
Exchanges will likely face fresh questions about testing, pre-launch checks, and how quickly safeguards can be re-enabled.
Featured image from Unsplash, chart from TradingView
