TLDR
It was Binance. A faulty internal price feed treated USDe at $0.65 as real, triggering forced liquidations and later refunds on the exchange per a market recap that cited the incident on Binances systems (report).
- USDe briefly showed $0.65 on Binance, which the internal oracle accepted, cascading liquidations (report).
- Binance began refunding users who were wrongly liquidated after the issue was exposed (coverage).
- The event occurred during the Oct 10 crash and amplified broader deleveraging across venues (analysis).
Deep Dive
1. What Happened
Reports point to a Binance pricing glitch where USDe printed around $0.65 on the venue and the internal oracle treated that price as valid, firing liquidations on positions using USDe as collateral. Screenshots and postmortems cited that Binance accepted the erroneous price, leading to forced unwinds during a wider market drop (report).
Binance later began refunding users who were liquidated due to the faulty feed, acknowledging incorrect triggers and adjusting systems to prevent a repeat (coverage).
If a single venues oracle ingests a bad price, cross?collateral positions can liquidate quickly, so diversify collateral and avoid relying on a single exchange reference during stress.
2. Why It Mattered
The glitch hit at the same time as a sharp market drawdown, turning a venue?specific error into a broader deleveraging cascade. Commentary described nearly two million accounts affected and framed it as a code and liquidity failure that amplified a selloff already underway (analysis).
This sequence shows structural fragility. When market makers pull back during outages or bad data, liquidity thins and prices gap, accelerating liquidations and volatility across both centralized and decentralized venues (coverage).
Venue?level risks are part of market risk. Monitoring oracle sources, collateral composition, and liquidity depth can reduce the chance that a local glitch wipes out a cross?venue position.
3. What To Watch Next
Look for formal incident notes and policy updates on price feeds and oracles. The reporting indicates Binance adjusted systems and refunded impacted users, which is a positive sign for future resilience, but independent verification and clear disclosure help rebuild trust (report).
Second order effects include cautious market making and thinner depth after the shock, keeping conditions jumpy in the near term as liquidity gradually returns (analysis).
In the short run, spreads and slippage can remain elevated. Consider the quality of oracle inputs and exchange incident responses when sizing risk.
Conclusion
Binances internal pricing glitch around USDe acceptance triggered a wave of forced liquidations, then refunds, during a broader market drawdown. The key driver was bad data feeding risk systems, which cascaded into cross?venue deleveraging. The lasting takeaway is that exchange and oracle design can magnify shocks, so venue risk management and diversified collateral matter when volatility spikes.
CoinsKid.Com