# USDe Never De-Pegged—Binance Had the Bug

**Published by:** [Christopher](https://paragraph.com/@-christopher/)
**Published on:** 2025-10-14
**Categories:** usde
**URL:** https://paragraph.com/@-christopher/usde-never-de-pegged%E2%80%94binance-had-the-bug

## Content

The Headline That Wasn’t Twitter spent the weekend screaming that Ethena’s dollar-stable coin USDe had “de-pegged” to $0.68 on Binance. It didn’t. What collapsed was Binance’s price feed, not the stable-coin itself.Where the Liquidity Actually Lives USDe’s deepest liquidity is on Curve, not on any CEX. Curve pools hold nine-figure depth; Binance’s order-book is a thin tens of millions. While Binance printed a 32 % discount, Curve never budged more than 30 bps. One of these prices is the real market—the other is a tech outage.Why Binance Went RogueAPI meltdown: deposits & withdrawals froze, so arbitrageurs were stuck.No primary-dealer lane: Binance can’t mint/redeem USDe directly; Bybit and others can, so they snapped back to par in minutes.Faulty oracle: Binance referenced its own illiquid book instead of external markets, liquidating users at ~$0.80 and feeding a cascade. The exchange is now refunding the wrongly liquidated—an implicit admission that the print was bogus.Compare a Real De-Peg: USDC in March 2023 When Silicon Valley Bank went under, USDC traded at $0.87 everywhere—Curve, Coinbase, Kraken, OTC desks—because redemptions were literally halted. That is a de-pegging. This weekend, USDe could still be swapped 1:1 for its backing assets; only one venue failed to reflect it.Take-Away for the Industry The episode is a stress-test score-card for market infrastructure, not for USDe’s design. Collateral coverage actually rose as volatility increased. The lesson is exchange-specific: if you’re not the primary liquidity venue, look outside your walls before you trigger liquidations. USDe never broke its buck; Binance broke its data.

## Publication Information

- [Christopher](https://paragraph.com/@-christopher/): Publication homepage
- [All Posts](https://paragraph.com/@-christopher/): More posts from this publication
- [RSS Feed](https://api.paragraph.com/blogs/rss/@-christopher): Subscribe to updates